[OpenWrt-Devel] [PATCH 1/1] flashrom: use msr path compatible w/ hotplug2
The issue wasn't that flashrom-0.9.3 was broken, but that the incompatible
device path put the box into a funky state that couldn't be reverted.
This fix causes it to use the hotplug2 path.
With this, we don't need to revert to 0.9.1, superseding my early patch to
revert...
Signed-off-by: Philip Prindeville
---
Index: feeds/packages/utils/flashrom/patches/001-msr_dev_path.patch
===
--- feeds/packages/utils/flashrom/patches/001-msr_dev_path.patch
(revision 0)
+++ feeds/packages/utils/flashrom/patches/001-msr_dev_path.patch
(revision 0)
@@ -0,0 +1,21 @@
+--- flashrom-0.9.3/physmap.c.orig 2010-10-05 20:56:44.0 -0600
flashrom-0.9.3/physmap.c 2011-03-29 20:26:22.0 -0600
+@@ -352,7 +352,7 @@ int setup_cpu_msr(int cpu)
+ {
+ char msrfilename[64];
+ memset(msrfilename, 0, sizeof(msrfilename));
+- snprintf(msrfilename, sizeof(msrfilename), "/dev/cpu/%d/msr", cpu);
++ snprintf(msrfilename, sizeof(msrfilename), "/dev/msr%d", cpu);
+
+ if (fd_msr != -1) {
+ msg_pinfo("MSR was already initialized\n");
+@@ -362,7 +362,8 @@ int setup_cpu_msr(int cpu)
+ fd_msr = open(msrfilename, O_RDWR);
+
+ if (fd_msr < 0) {
+- perror("Error while opening /dev/cpu/0/msr");
++ fprintf(stderr, "Error while opening %s: %s\n", msrfilename,
++ strerror(errno));
+ msg_pinfo("Did you run 'modprobe msr'?\n");
+ return -1;
+ }
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] 802.1Q VLAN support for Infineon ADM6996 switch chip for UBNT RouterStation
Dear all, Any one has tried the patch from Peter Lebbing on VLAN tag on UBNT RouterStation platform and get it work properly. Regards, Chun Yeow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Kernel opps after erasing jffs partition (ramips rt305x)
https://dev.openwrt.org/ticket/9143 [1] Links: -- [1] https://dev.openwrt.org/ticket/9143 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] block-extroot and firmware updating/flashing
> Picky, picky. ;-) No, no, just "picky". > Well other than binaries that depend on the kernel like iptables you > should be right about the uClibc binaries. But the normal case (i.e. > not custom) is to load the modules after extroot, so that's what we > build extroot for. If you really care and want to submit patches that > are suitably generic, we'll of course take a look at them. That's fine. I just wanted to check whether there was some deep reason I wasn't aware of. I don't think it's a big issue since upgrading the firmware already requires several steps anyway, so a few more is not a big deal. I.e. it's a very low-priority annoyance. Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Segfault with Asterisk 1.8 WNDR3700 on (r26315)
Hello, On Tue, Mar 29, 2011 at 11:22:51PM +0200, Etienne Champetier wrote: > [...] > It may sound strange but did you launch freeradius with ssh or with luci > When starting pmacctd or uacctd with luci i've got problem with SIGCHLD (not > send by the child or not received by the parent ???) > > Hoping that help... I don't have freeradius installed but thanks for replying to me! ;-) -- Mathieu Chouquet-Stringer math...@csetco.com The sun itself sees not till heaven clears. -- William Shakespeare -- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Segfault with Asterisk 1.8 WNDR3700 on (r26315)
Hello
It may sound strange but did you launch freeradius with ssh or with luci
When starting pmacctd or uacctd with luci i've got problem with SIGCHLD (not
send by the child or not received by the parent ???)
Hoping that help...
Le 29/03/2011 23:15, Mathieu Chouquet-Stringer a écrit :
> [resending as I hadn't realized I needed to subscribe to the mailing
> list]
>
> Hello Hans, hello all,
>
> I just recompiled and upgraded my WNDR3700 home router and everything
> went really well. Much congrats to people involved with the build
> system, packages and all...
>
> I was previously running asterisk 1.4 and I'm in the process of moving
> my setup to 1.8.
>
> That said, I'm having issues: as soon as I install asterisk18-app-stack
> from trunk (1.8.2.3-1), no matter what my setup is (in terms of
> configuration files), asterisk segfaults when I start it (either in
> daemon mode or console mode).
>
> At the moment, I have only these 2 packages installed, I haven't yet
> touched the config and it still segfaults:
> asterisk18 - 1.8.2.3-1
> asterisk18-app-stack - 1.8.2.3-1
>
> There's nothing in system logs:
> [Mar 29 20:40:18] WARNING[5239] ccss.c: Could not find valid ccss.conf file.
> Using cc_max_requests default
> [Mar 29 20:40:18] NOTICE[5239] loader.c: 21 modules will be loaded.
> [Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module
> 'res_musiconhold.so': File not found
> [Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module
> 'res_musiconhold.so': File not found
> [Mar 29 20:40:18] WARNING[5239] loader.c: Module 'res_musiconhold.so' could
> not be loaded.
> [Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module 'res_crypto':
> File not found
> [Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module 'chan_local':
> File not found
> [Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module 'res_agi':
> File not found
>
> If I strace it, it always dies at the same point: it resolves hostname
> using DNS and then clone a new process...
>
> [pid 5878] stat("/etc/resolv.conf", {st_dev=makedev(0, 12), st_ino=34483,
> st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
> st_blocks=8, st_size=44, st_atime=2011/03/29-22:51:50,
> st_mtime=2011/03/29-22:51:50, st_ctime=2011/03/29-22:51:50}) = 0
> [pid 5878] socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 6
> [pid 5878] connect(6, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("127.0.0.1")}, 28) = 0
> [pid 5878] send(6, "\0\5\1\0\0\1\0\0\0\0\0\0\7OpenWrt\4\6YY"..., 41,
> 0) = 41
> [pid 5878] poll([{fd=6, events=POLLIN}], 1, 5000) = 1 ([{fd=6,
> revents=POLLIN}])
> [pid 5878] recv(6, "\0\5\205\200\0\1\0\1\0\0\0\0\7OpenWrt\4\6YY"...,
> 512, MSG_DONTWAIT) = 57
> [pid 5878] close(6)= 0
> [pid 5878] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
> [pid 5878] setsockopt(6, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
> [pid 5878] setsockopt(6, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
> [pid 5878] bind(6, {sa_family=AF_INET, sin_port=htons(5060),
> sin_addr=inet_addr("0.0.0.0")}, 16) = 0
> [pid 5878] getsockname(6, {sa_family=AF_INET, sin_port=htons(5060),
> sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
> [pid 5878] setsockopt(6, SOL_IP, IP_TOS, [0], 4) = 0
> [pid 5878] setsockopt(6, SOL_SOCKET, SO_PRIORITY, [4], 4) = 0
> [pid 5878] gettimeofday({1301432042, 8553}, NULL) = 0
> [pid 5878] stat64(0x7ffec5d0, 0x7ffec438) = 0
> [pid 5878] open("/etc/asterisk/sip_notify.conf", O_RDONLY|O_LARGEFILE) = 7
> [pid 5878] ioctl(7, TIOCNXCL, 0x7ffec3e8) = -1 ENOTTY (Inappropriate ioctl
> for device)
> [pid 5878] gettimeofday({1301432042, 9229}, NULL) = 0
> [pid 5878] read(7, "; rfc3842\n; put empty \"Content=>"..., 4096) = 725
> [pid 5878] read(7, "", 4096) = 0
> [pid 5878] close(7)= 0
> [pid 5878] gettimeofday({1301432042, 10072}, NULL) = 0
> [pid 5878] time(NULL) = 1301432042
> [pid 5878] gettimeofday({1301432042, 10291}, NULL) = 0
> [pid 5878] old_mmap(NULL, 49152, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b5a8000 [pid 5878]
> mprotect(0x2b5a8000, 4096, PROT_NONE) = 0
> [pid 5878] clone(Process 5888 attached
> child_stack=0x2b5b3380,
> flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
> parent_tidptr=0x2b5b36e8, tls=0x2b5ba970, child_tidptr=0x2b5b36e8) = 5888
> [pid 5878] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> [pid 5887] +++ killed by SIGSEGV +++
> [pid 5886] +++ killed by SIGSEGV +++
> [pid 5885] +++ killed by SIGSEGV +++
> [pid 5884] +++ killed by SIGSEGV +++
> [pid 5883] +++ killed by SIGSEGV +++
> [pid 5882] +++ killed by SIGSEGV +++
> [pid 5881] +++ killed by SIGSEGV +++
> [pid 5880] +++ killed by SIGSEGV +++
> [pid 5879] +++ killed by SIGSEGV +++
> [pid 5888] +++ killed by SIGSEGV +++
>
> Not sure where to go from here... I've tried enabling debugging but
> it doesn't see
[OpenWrt-Devel] Segfault with Asterisk 1.8 WNDR3700 on (r26315)
[resending as I hadn't realized I needed to subscribe to the mailing
list]
Hello Hans, hello all,
I just recompiled and upgraded my WNDR3700 home router and everything
went really well. Much congrats to people involved with the build
system, packages and all...
I was previously running asterisk 1.4 and I'm in the process of moving
my setup to 1.8.
That said, I'm having issues: as soon as I install asterisk18-app-stack
from trunk (1.8.2.3-1), no matter what my setup is (in terms of
configuration files), asterisk segfaults when I start it (either in
daemon mode or console mode).
At the moment, I have only these 2 packages installed, I haven't yet
touched the config and it still segfaults:
asterisk18 - 1.8.2.3-1
asterisk18-app-stack - 1.8.2.3-1
There's nothing in system logs:
[Mar 29 20:40:18] WARNING[5239] ccss.c: Could not find valid ccss.conf file.
Using cc_max_requests default
[Mar 29 20:40:18] NOTICE[5239] loader.c: 21 modules will be loaded.
[Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module
'res_musiconhold.so': File not found
[Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module
'res_musiconhold.so': File not found
[Mar 29 20:40:18] WARNING[5239] loader.c: Module 'res_musiconhold.so' could not
be loaded.
[Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module 'res_crypto':
File not found
[Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module 'chan_local':
File not found
[Mar 29 20:40:18] WARNING[5239] loader.c: Error loading module 'res_agi': File
not found
If I strace it, it always dies at the same point: it resolves hostname
using DNS and then clone a new process...
[pid 5878] stat("/etc/resolv.conf", {st_dev=makedev(0, 12), st_ino=34483,
st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=8, st_size=44, st_atime=2011/03/29-22:51:50,
st_mtime=2011/03/29-22:51:50, st_ctime=2011/03/29-22:51:50}) = 0
[pid 5878] socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 6
[pid 5878] connect(6, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 28) = 0
[pid 5878] send(6, "\0\5\1\0\0\1\0\0\0\0\0\0\7OpenWrt\4\6YY"..., 41,
0) = 41
[pid 5878] poll([{fd=6, events=POLLIN}], 1, 5000) = 1 ([{fd=6,
revents=POLLIN}])
[pid 5878] recv(6, "\0\5\205\200\0\1\0\1\0\0\0\0\7OpenWrt\4\6YY"...,
512, MSG_DONTWAIT) = 57
[pid 5878] close(6)= 0
[pid 5878] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
[pid 5878] setsockopt(6, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid 5878] setsockopt(6, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
[pid 5878] bind(6, {sa_family=AF_INET, sin_port=htons(5060),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
[pid 5878] getsockname(6, {sa_family=AF_INET, sin_port=htons(5060),
sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
[pid 5878] setsockopt(6, SOL_IP, IP_TOS, [0], 4) = 0
[pid 5878] setsockopt(6, SOL_SOCKET, SO_PRIORITY, [4], 4) = 0
[pid 5878] gettimeofday({1301432042, 8553}, NULL) = 0
[pid 5878] stat64(0x7ffec5d0, 0x7ffec438) = 0
[pid 5878] open("/etc/asterisk/sip_notify.conf", O_RDONLY|O_LARGEFILE) = 7
[pid 5878] ioctl(7, TIOCNXCL, 0x7ffec3e8) = -1 ENOTTY (Inappropriate ioctl for
device)
[pid 5878] gettimeofday({1301432042, 9229}, NULL) = 0
[pid 5878] read(7, "; rfc3842\n; put empty \"Content=>"..., 4096) = 725
[pid 5878] read(7, "", 4096) = 0
[pid 5878] close(7)= 0
[pid 5878] gettimeofday({1301432042, 10072}, NULL) = 0
[pid 5878] time(NULL) = 1301432042
[pid 5878] gettimeofday({1301432042, 10291}, NULL) = 0
[pid 5878] old_mmap(NULL, 49152, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b5a8000 [pid 5878] mprotect(0x2b5a8000,
4096, PROT_NONE) = 0
[pid 5878] clone(Process 5888 attached
child_stack=0x2b5b3380,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0x2b5b36e8, tls=0x2b5ba970, child_tidptr=0x2b5b36e8) = 5888
[pid 5878] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 5887] +++ killed by SIGSEGV +++
[pid 5886] +++ killed by SIGSEGV +++
[pid 5885] +++ killed by SIGSEGV +++
[pid 5884] +++ killed by SIGSEGV +++
[pid 5883] +++ killed by SIGSEGV +++
[pid 5882] +++ killed by SIGSEGV +++
[pid 5881] +++ killed by SIGSEGV +++
[pid 5880] +++ killed by SIGSEGV +++
[pid 5879] +++ killed by SIGSEGV +++
[pid 5888] +++ killed by SIGSEGV +++
Not sure where to go from here... I've tried enabling debugging but
it doesn't seem to show more than this.
I've looked at known bugs, googled, and found nothing so I'm willing to:
- recompile my kernel with core dumping enabled (not having it certainly
doesn't help)
- compile asterisk with debug mode on to see where it dies
unless you have better ideas of what to try...
Thanks in advance for any kind of assistance you could provide...
Cheers,
--
Mathieu Chouquet-Stringer math...@csetco.com
The sun itself se
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/11 21:21, En/na Felix Fietkau ha escrit:
> On 2011-03-29 6:38 PM, Luca Olivetti wrote:
>> Al 29/03/11 18:30, En/na John Crispin ha escrit:
>>> On 29/03/11 18:06, Luca Olivetti wrote:
Al 29/03/11 10:32, En/na John Crispin ha escrit:
>> AFAIS, the current in-kernel driver relies on regulatory domain for
>> frequency restrictions.
>> It could solve your current problem.
>
> yes, the proposed patch rewrites the eep on the fly upon a read and
> fakes a ES reg. this is the patch we can accept as is into owrt
Can or can't?
Bye
>>>
>>> cannot
>>
>> Would 0x67 be acceptable?
> What regdomain is programmed into the EEPROM by default?
It is set at 0. The original firmware (which isn't Linux but it seems it's
using a version of ath9k) overrides ir too.
See this extract from the bootlog:
EEPROM : EEP_MAP_DEFAULT !
Powertable magic: a55a
ar5416CheckEepromDef: Read Magic = 0xA55A
need_swap = True.
EEPROM Endianness is not native.. Changing
regDmn[0] 0
regDmn[1] 1f
change it to 1f1f
[HWLAN] Set HWLAN MAC as LAN MAC ..
ath_getchannels> nchan=22
ath_getchannels> nchan=22
ath_getchannels> nchan=22 match:9
Chan Freq RegPwr HT CTL CTL_U CTL_L DFS
1 2412n 20 HT20 101 N
2 2417n 20 HT20 101 N
3 2422n 20 HT40 101 N
4 2427n 20 HT40 101 N
5 2432n 20 HT40 111 N
6 2437n 20 HT40 111 N
7 2442n 20 HT40 111 N
8 2447n 20 HT40 111 N
9 2452n 20 HT40 111 N
10 2457n 20 HT40 110 N
11 2462n 20 HT40 110 N
12 2467n 20 HT20 110 N
13 2472n 20 HT20 110 N
ath_countrycode : 724
> And what does the driver do with it if you leave out the override?
It will set a default world regdomain (the most restrictive):
static const struct ieee80211_regdomain *ath_default_world_regdomain(void)
{
/* this is the most restrictive */
return &ath_world_regdom_64;
}
static const struct
ieee80211_regdomain *ath_world_regdomain(struct ath_regulatory *reg)
{
switch (reg->regpair->regDmnEnum) {
case 0x60:
case 0x61:
case 0x62:
return &ath_world_regdom_60_61_62;
case 0x63:
case 0x65:
return &ath_world_regdom_63_65;
case 0x64:
return &ath_world_regdom_64;
case 0x66:
case 0x69:
return &ath_world_regdom_66_69;
case 0x67:
case 0x68:
case 0x6A:
return &ath_world_regdom_67_68_6A;
default:
WARN_ON(1);
return ath_default_world_regdomain();
}
}
But I was asking if it's not acceptable to set the regdomain to Spain or
if it's not acceptable to change it at all.
Bye
--
Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
On 2011-03-29 6:38 PM, Luca Olivetti wrote: Al 29/03/11 18:30, En/na John Crispin ha escrit: On 29/03/11 18:06, Luca Olivetti wrote: Al 29/03/11 10:32, En/na John Crispin ha escrit: AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. yes, the proposed patch rewrites the eep on the fly upon a read and fakes a ES reg. this is the patch we can accept as is into owrt Can or can't? Bye cannot Would 0x67 be acceptable? What regdomain is programmed into the EEPROM by default? And what does the driver do with it if you leave out the override? - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/1] flashrom: revert to 0.9.1, and patch for proper MSR dev path
Flashrom looks for the MSR as /dev/cpu/%d/msr on an SMP box, but most embedded
applications are UP. Patch
the path accordingly.
Also, 0.9.3 introduced a regression in how certain devices are erased. Revert
to 0.9.1.
Signed-off-by: Philip Prindeville
---
Index: packages/utils/flashrom/patches/001-msr_path.patch
===
--- packages/utils/flashrom/patches/001-msr_path.patch (revision 0)
+++ packages/utils/flashrom/patches/001-msr_path.patch (revision 0)
@@ -0,0 +1,21 @@
+--- flashrom-0.9.1/physmap.c.orig 2009-08-19 04:46:23.0 -0600
flashrom-0.9.1/physmap.c 2011-03-29 01:41:01.0 -0600
+@@ -184,7 +184,7 @@ int setup_cpu_msr(int cpu)
+ {
+ char msrfilename[64];
+ memset(msrfilename, 0, 64);
+- sprintf(msrfilename, "/dev/cpu/%d/msr", cpu);
++ sprintf(msrfilename, "/dev/msr%d", cpu);
+
+ if (fd_msr != -1) {
+ printf("MSR was already initialized\n");
+@@ -194,7 +194,8 @@ int setup_cpu_msr(int cpu)
+ fd_msr = open(msrfilename, O_RDWR);
+
+ if (fd_msr < 0) {
+- perror("Error while opening /dev/cpu/0/msr");
++ fprintf(stderr, "Error while opening %s: %s\n", msrfilename,
++ strerror(errno));
+ printf("Did you run 'modprobe msr'?\n");
+ return -1;
+ }
Index: packages/utils/flashrom/Makefile
===
--- packages/utils/flashrom/Makefile(revision 26355)
+++ packages/utils/flashrom/Makefile(working copy)
@@ -1,5 +1,5 @@
#
-# Copyright (C) 2010 OpenWrt.org
+# Copyright (C) 2011 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=flashrom
-PKG_VERSION:=0.9.3
+PKG_VERSION:=0.9.1
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=http://qa.coreboot.org/releases/
-PKG_MD5SUM:=eccdec2764223f5d2839bf577380eaa9
+PKG_MD5SUM:=2b7cc0e45a0ac4c6d43c0f7cd05b041a
include $(INCLUDE_DIR)/package.mk
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] iptables tee and u32
Hello, I sent before iptables_tee.patch but did not received any feedback and patch is not applied. Sending now as attaches iptables_tee.patch iptables_u32.patch. I can maintain iptables package. -- Best regards, Maxim Uvarov --- ./include/netfilter.mk.orig 2011-03-22 22:22:49.837576205 -0700 +++ ./include/netfilter.mk 2011-03-23 09:32:04.219794159 -0700 @@ -283,6 +283,10 @@ $(eval $(call nf_add,IPT_ULOG,CONFIG_IP_ $(eval $(call nf_add,IPT_TPROXY,CONFIG_NETFILTER_XT_MATCH_SOCKET, $(P_XT)xt_socket)) $(eval $(call nf_add,IPT_TPROXY,CONFIG_NETFILTER_XT_TARGET_TPROXY, $(P_XT)xt_TPROXY)) +# tee + +$(eval $(call nf_add,IPT_TEE,CONFIG_NETFILTER_XT_TARGET_TEE, $(P_XT)xt_TEE)) + # # ebtables # --- ./package/iptables/Makefile.orig 2011-03-22 16:35:21.985572908 -0700 +++ ./package/iptables/Makefile 2011-03-23 09:32:05.066073042 -0700 @@ -229,6 +229,16 @@ Includes: - libxt_TPROXY endef +define Package/iptables-mod-tee +$(call Package/iptables/Module, +kmod-ipt-tee) + TITLE:=TEE iptables extensions +endef + +define Package/iptables-mod-tee/description +TEE iptables extensions. +Includes: +- libxt_TEE +endef define Package/iptables-utils $(call Package/iptables/Module, ) @@ -399,6 +409,7 @@ $(eval $(call BuildPlugin,iptables-mod-i $(eval $(call BuildPlugin,iptables-mod-ulog,$(IPT_ULOG-m))) $(eval $(call BuildPlugin,iptables-mod-hashlimit,$(IPT_HASHLIMIT-m))) $(eval $(call BuildPlugin,iptables-mod-tproxy,$(IPT_TPROXY-m))) +$(eval $(call BuildPlugin,iptables-mod-tee,$(IPT_TEE-m))) $(eval $(call BuildPackage,ip6tables)) $(eval $(call BuildPackage,ip6tables-utils)) $(eval $(call BuildPackage,libiptc)) --- ./package/kernel/modules/netfilter.mk_orig 2011-03-23 09:43:38.0 -0700 +++ ./package/kernel/modules/netfilter.mk 2011-03-23 01:04:42.0 -0700 @@ -279,8 +279,26 @@ define KernelPackage/ipt-tproxy/descript Kernel modules for Transparent Proxying endef + $(eval $(call KernelPackage,ipt-tproxy)) +define KernelPackage/ipt-tee + TITLE:=TEE support + KCONFIG:= \ + CONFIG_NETFILTER_XT_TARGET_TEE + FILES:= \ + $(LINUX_DIR)/net/netfilter/xt_TEE.ko \ + $(foreach mod,$(IPT_TEE-m),$(LINUX_DIR)/net/$(mod).ko) + AUTOLOAD:=$(call AutoLoad,45,$(notdir nf_tee $(IPT_TEE-m))) + $(call AddDepends/ipt) +endef + +define KernelPackage/ipt-tee/description + Kernel modules for TEE +endef + +$(eval $(call KernelPackage,ipt-tee)) + define KernelPackage/ipt-iprange TITLE:=Module for matching ip ranges --- ./include/netfilter.mk.orig 2011-03-29 09:36:51.526659744 -0700 +++ include/netfilter.mk 2011-03-29 09:43:18.510644953 -0700 @@ -287,6 +287,10 @@ $(eval $(call nf_add,IPT_TPROXY,CONFIG_N $(eval $(call nf_add,IPT_TEE,CONFIG_NETFILTER_XT_TARGET_TEE, $(P_XT)xt_TEE)) +# u32 + +$(eval $(call nf_add,IPT_U32,CONFIG_NETFILTER_XT_MATCH_U32, $(P_XT)xt_u32)) + # # ebtables # --- package/iptables/Makefile.orig 2011-03-28 10:51:55.017571052 -0700 +++ package/iptables/Makefile 2011-03-28 12:56:37.849995355 -0700 @@ -240,6 +240,17 @@ Includes: - libxt_TEE endef +define Package/iptables-mod-u32 +$(call Package/iptables/Module, +kmod-ipt-u32) + TITLE:=U32 iptables extensions +endef + +define Package/iptables-mod-u32/description +U32 iptables extensions. +Includes: +- libxt_u32 +endef + define Package/iptables-utils $(call Package/iptables/Module, ) TITLE:=iptables save and restore utilities @@ -410,6 +421,7 @@ $(eval $(call BuildPlugin,iptables-mod-u $(eval $(call BuildPlugin,iptables-mod-hashlimit,$(IPT_HASHLIMIT-m))) $(eval $(call BuildPlugin,iptables-mod-tproxy,$(IPT_TPROXY-m))) $(eval $(call BuildPlugin,iptables-mod-tee,$(IPT_TEE-m))) +$(eval $(call BuildPlugin,iptables-mod-u32,$(IPT_U32-m))) $(eval $(call BuildPackage,ip6tables)) $(eval $(call BuildPackage,ip6tables-utils)) $(eval $(call BuildPackage,libiptc)) --- package/kernel/modules/netfilter.mk_orig 2011-03-28 10:54:01.30705 -0700 +++ package/kernel/modules/netfilter.mk 2011-03-28 12:11:06.869573081 -0700 @@ -299,6 +299,23 @@ endef $(eval $(call KernelPackage,ipt-tee)) +define KernelPackage/ipt-u32 + TITLE:=U32 support + KCONFIG:= \ + CONFIG_NETFILTER_XT_MATCH_U32 + FILES:= \ + $(LINUX_DIR)/net/netfilter/xt_u32.ko \ + $(foreach mod,$(IPT_U32-m),$(LINUX_DIR)/net/$(mod).ko) + AUTOLOAD:=$(call AutoLoad,45,$(notdir nf_tee $(IPT_U32-m))) + $(call AddDepends/ipt) +endef + +define KernelPackage/ipt-u32/description + Kernel modules for U32 +endef + +$(eval $(call KernelPackage,ipt-u32)) + define KernelPackage/ipt-iprange TITLE:=Module for matching ip ranges ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
On Tue, 29 Mar 2011 19:08:22 +0200, Gabor Juhos wrote: 2011.03.29. 18:44 keltezéssel, Layne Edwards írta: On Tue, 29 Mar 2011 17:30:21 +0200, Jochen Friedrich wrote: IMHO, it doesn't matter how patches are submitted - whether it be via mailing list or trac - as long as the same method is used for all patches so they are all in the same place (and therefore don't slip through the cracks). As for patchwork, I see that some patches submitted via the mailing list are not listed... so if that is the only source the devs use to accept patches, some might be missed. Only unprocessed patches are listed by default. You have to clear the filter to see all patches and their status. Clearing all filters, I still don't see all patches in patchwork. For example, the following are not listed: 3/21 - Add WLAN LED support for Ralink RT305x SoC Devices 3/15 - sysupgrade and status LED support for ramips HW550-3G Correct, your patches are not there. Probably because each line of the message body contains a leading whitespace, and they were not identified as valid patches. Hmmm... that's odd. I didn't add any leading whitespace, just submitted the patch inline as plain text. The whitespace must have been added by my email client (roundcube). It looks like all of my emails have leading whitespace when I look at the source. I'll have to investigate. Thanks for pointing this out. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] iptables / missing libip4tc.so.0
2011/3/29 Felix Fietkau : > On 2011-03-29 3:03 PM, Bastian Bittorf wrote: >> >> I build from trunk for ar71xx. >> I already tried make clean/distclean. >> >> After flashing the router i get: >> >> root@openwrt:~ iptables -h >> iptables: can't load library 'libip4tc.so.0' >> >> the file belongs to iptables and is defined here: >> >> package/iptables/Makefile >> >> but it is not build?: >> build@box:$ grep "iptables" .config | grep -v ^# >> CONFIG_DEFAULT_iptables=y >> CONFIG_PACKAGE_iptables=y >> CONFIG_PACKAGE_iptables-mod-conntrack=y >> CONFIG_PACKAGE_iptables-mod-conntrack-extra=y >> CONFIG_PACKAGE_iptables-mod-extra=y >> CONFIG_PACKAGE_iptables-mod-filter=y >> CONFIG_PACKAGE_iptables-mod-ipopt=y >> CONFIG_PACKAGE_iptables-mod-nat=y >> CONFIG_PACKAGE_iptables-mod-nat-extra=y >> CONFIG_PACKAGE_iptables-mod-ulog=y >> >> maybe this is related: >> https://forum.openwrt.org/viewtopic.php?pid=123430 >> >> any ideas? > > Did you forget to run make oldconfig after updating? > > - Felix > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > Does this error happen only with -h? If so, I don't think that help is required on the router. -- Best regards, Maxim Uvarov ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
2011.03.29. 18:44 keltezéssel, Layne Edwards írta: > On Tue, 29 Mar 2011 17:30:21 +0200, Jochen Friedrich wrote: >>> IMHO, it doesn't matter how patches are submitted - whether it be via >>> mailing >>> list or trac - as long as the same method is used for all patches so they >>> are >>> all in the same place (and therefore don't slip through the cracks). As for >>> patchwork, I see that some patches submitted via the mailing list are not >>> listed... so if that is the only source the devs use to accept patches, some >>> might be missed. >> >> Only unprocessed patches are listed by default. You have to clear the >> filter to see all patches and their status. >> > > Clearing all filters, I still don't see all patches in patchwork. For > example, > the following are not listed: > > 3/21 - Add WLAN LED support for Ralink RT305x SoC Devices > 3/15 - sysupgrade and status LED support for ramips HW550-3G Correct, your patches are not there. Probably because each line of the message body contains a leading whitespace, and they were not identified as valid patches. -Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
On Tue, 29 Mar 2011 17:30:21 +0200, Jochen Friedrich wrote: IMHO, it doesn't matter how patches are submitted - whether it be via mailing list or trac - as long as the same method is used for all patches so they are all in the same place (and therefore don't slip through the cracks). As for patchwork, I see that some patches submitted via the mailing list are not listed... so if that is the only source the devs use to accept patches, some might be missed. Only unprocessed patches are listed by default. You have to clear the filter to see all patches and their status. Clearing all filters, I still don't see all patches in patchwork. For example, the following are not listed: 3/21 - Add WLAN LED support for Ralink RT305x SoC Devices 3/15 - sysupgrade and status LED support for ramips HW550-3G ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/11 18:30, En/na John Crispin ha escrit: > On 29/03/11 18:06, Luca Olivetti wrote: >> Al 29/03/11 10:32, En/na John Crispin ha escrit: >> AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. >>> >>> yes, the proposed patch rewrites the eep on the fly upon a read and >>> fakes a ES reg. this is the patch we can accept as is into owrt >> >> Can or can't? >> >> Bye > > cannot Would 0x67 be acceptable? Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
On 29/03/11 18:06, Luca Olivetti wrote: > Al 29/03/11 10:32, En/na John Crispin ha escrit: > >>> AFAIS, the current in-kernel driver relies on regulatory domain for >>> frequency restrictions. >>> It could solve your current problem. >> >> yes, the proposed patch rewrites the eep on the fly upon a read and >> fakes a ES reg. this is the patch we can accept as is into owrt > > Can or can't? > > Bye cannot ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/11 10:32, En/na John Crispin ha escrit: >> AFAIS, the current in-kernel driver relies on regulatory domain for >> frequency restrictions. >> It could solve your current problem. > > yes, the proposed patch rewrites the eep on the fly upon a read and > fakes a ES reg. this is the patch we can accept as is into owrt Can or can't? Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] add uacctd
Hello
This patch add uacctd, an ulog based accounting deamon from pmacct project
(http://www.pmacct.net/)
It also put all pmacct packages in a submenu called (13 packages)
Thanks in advance.
Signed-off-by: Etienne CHAMPETIER
Index: admin/pmacct/files/uacctd.init
===
--- admin/pmacct/files/uacctd.init (révision 0)
+++ admin/pmacct/files/uacctd.init (révision 0)
@@ -0,0 +1,18 @@
+#!/bin/sh /etc/rc.common
+# Copyright (C) 2006 OpenWrt.org
+START=50
+
+BIN=uacctd
+DEFAULT=/etc/default/$BIN
+RUN_D=/var/run
+PID_F=$RUN_D/$BIN.pid
+
+start() {
+ [ -f $DEFAULT ] && . $DEFAULT
+ mkdir -p $RUN_D
+ $BIN $OPTIONS
+}
+
+stop() {
+ [ -f $PID_F ] && kill -INT $(cat $PID_F)
+}
Index: admin/pmacct/files/uacctd.default
===
--- admin/pmacct/files/uacctd.default (révision 0)
+++ admin/pmacct/files/uacctd.default (révision 0)
@@ -0,0 +1 @@
+OPTIONS="-f /etc/uacctd.conf"
Index: admin/pmacct/files/uacctd.conf
===
--- admin/pmacct/files/uacctd.conf (révision 0)
+++ admin/pmacct/files/uacctd.conf (révision 0)
@@ -0,0 +1,28 @@
+!
+! uacctd configuration example
+!
+! debug: true
+
+uacctd_group : 1
+
+daemonize: true
+pidfile: /var/run/uacctd.pid
+aggregate: src_host,dst_host
+! aggregate: src_net,dst_net
+plugins: memory
+imt_buckets: 65537
+imt_mem_pools_size: 65536
+! imt_mem_pools_number: 0
+! plugins: mysql
+! plugins: pgsql
+! plugins: sqlite3
+! sql_db: uacct
+! sql_table: acct
+! sql_table_version: 2
+! sql_passwd: arealsmartpwd
+! sql_user: uacct
+! sql_refresh_time: 90
+! sql_optimize_clauses: true
+! sql_history: 10m
+! sql_history_roundoff: mh
+! networks_file: ./networks.example
Index: admin/pmacct/Makefile
===
--- admin/pmacct/Makefile (révision 26352)
+++ admin/pmacct/Makefile (copie de travail)
@@ -22,6 +22,7 @@
define Package/pmacct/Default
SECTION:=admin
CATEGORY:=Administration
+ SUBMENU:=Pmacct suite
URL:=http://www.pmacct.net/
endef
@@ -80,6 +81,34 @@
DEPENDS+= +libsqlite3
endef
+define Package/uacctd/Default
+ $(call Package/pmacct/Default)
+ DEPENDS+= +iptables-mod-ulog
+ TITLE:=ulog accounting daemon
+endef
+
+define Package/uacctd
+ $(call Package/pmacctd/Default)
+endef
+
+define Package/uacctd-mysql
+ $(call Package/pmacctd/Default)
+ TITLE+= with MySQL support
+ DEPENDS+= +libmysqlclient
+endef
+
+define Package/uacctd-pgsql
+ $(call Package/pmacctd/Default)
+ TITLE+= with PostreSQL support
+ DEPENDS+= +libpq
+endef
+
+define Package/uacctd-sqlite
+ $(call Package/pmacctd/Default)
+ TITLE+= with SQLite support
+ DEPENDS+= +libsqlite3
+endef
+
define Package/pmacct-client
$(call Package/pmacct/Default)
TITLE:=Command-line client to gather data from the IMT plugin
@@ -87,11 +116,12 @@
define Compile/Template
-$(PKG_BUILD_DIR)/nfacctd$(1) $(PKG_BUILD_DIR)/pmacctd$(1): $(STAMP_CONFIGURED)
+$(PKG_BUILD_DIR)/nfacctd$(1) $(PKG_BUILD_DIR)/pmacctd$(1)
$(PKG_BUILD_DIR)/uacctd$(1): $(STAMP_CONFIGURED)
-$(MAKE) -C $(PKG_BUILD_DIR) distclean
$(call Build/Configure/Default, \
--with-pcap-includes="$(STAGING_DIR)/usr/include" \
--with-pcap-libs="$(STAGING_DIR)/usr/lib" \
+ --enable-ulog \
$(2) \
,\
LIBS="-lz" \
@@ -101,8 +131,9 @@
all
mv -f $(PKG_BUILD_DIR)/src/nfacctd $(PKG_BUILD_DIR)/nfacctd$(1)
mv -f $(PKG_BUILD_DIR)/src/pmacctd $(PKG_BUILD_DIR)/pmacctd$(1)
+ mv -f $(PKG_BUILD_DIR)/src/uacctd $(PKG_BUILD_DIR)/uacctd$(1)
-$(PKG_BUILD_DIR)/.built: $(PKG_BUILD_DIR)/nfacctd$(1)
$(PKG_BUILD_DIR)/pmacctd$(1)
+$(PKG_BUILD_DIR)/.built: $(PKG_BUILD_DIR)/nfacctd$(1)
$(PKG_BUILD_DIR)/pmacctd$(1) $(PKG_BUILD_DIR)/uacctd$(1)
endef
@@ -127,7 +158,7 @@
endef
-ifneq ($(SDK)$(CONFIG_PACKAGE_nfacctd)$(CONFIG_PACKAGE_pmacctd),)
+ifneq
($(SDK)$(CONFIG_PACKAGE_nfacctd)$(CONFIG_PACKAGE_pmacctd)$(CONFIG_PACKAGE_uacctd),)
define Compile/pmacct/basic
$(call Compile/Template,, \
--disable-mysql \
@@ -136,11 +167,12 @@
)
$(call Install/Template,nfacctd,)
$(call Install/Template,pmacctd,)
+ $(call Install/Template,uacctd,)
endef
endif
$(eval $(Compile/pmacct/basic))
-ifneq ($(SDK)$(CONFIG_PACKAGE_nfacctd-mysql)$(CONFIG_PACKAGE_pmacctd-mysql),)
+ifneq
($(SDK)$(CONFIG_PACKAGE_nfacctd-mysql)$(CONFIG_PACKAGE_pmacctd-mysql)$(CONFIG_PACKAGE_uacctd-mysql),)
define Compile/pmacct/mysql
$(call Compile/Template,-mysql, \
--enable-mysql \
@@ -149,11 +181,12 @@
)
$(call Install/Template,nfacctd,-mysql)
$(call Install/Template,pmacctd,-mysql)
+ $(call Install/Template,uacctd,-mysql)
endef
e
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
Hi Layne, http://patchwork.cyranjo.org/ That's bud's quote, not mine :) Oops, apologies! IMHO, it doesn't matter how patches are submitted - whether it be via mailing list or trac - as long as the same method is used for all patches so they are all in the same place (and therefore don't slip through the cracks). As for patchwork, I see that some patches submitted via the mailing list are not listed... so if that is the only source the devs use to accept patches, some might be missed. Only unprocessed patches are listed by default. You have to clear the filter to see all patches and their status. Thanks, Jochen ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
On Tue, 29 Mar 2011 10:21:44 +0200, Jochen Friedrich wrote: Hi Layne, i'd change my patch delivery then by posting them to the more public wiki and posting a note here only. this way people hit by the same bug can find the patch online with their favorite search engine no matter if an openwrt dev had the time to check and push it to trunk or not. I don't know if you've read the mail posted almost a year ago here ;-), but there is a public patch repository available at: http://patchwork.cyranjo.org/ Cheers, Jochen That's bud's quote, not mine :) IMHO, it doesn't matter how patches are submitted - whether it be via mailing list or trac - as long as the same method is used for all patches so they are all in the same place (and therefore don't slip through the cracks). As for patchwork, I see that some patches submitted via the mailing list are not listed... so if that is the only source the devs use to accept patches, some might be missed. Gregers - I will be there Sunday :) Regards, Layne ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
Regarding the current debate - I'll try to pull the various strings and suggestions together and post an agenda for sundays meeting. Sincerely On 28/03/11 22:52, Larry Vaden wrote: > On Mon, Mar 28, 2011 at 3:15 PM, Layne Edwards > wrote: >> >> Respectfully, >> Layne > > Equally respectfully, Fedora IMHO has an excellent model of mentorship > prior to gaining rights. > > kind regards/ldv -- Gregers Petersen Relationship manager, layer 8 and anthropology glp on irc ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M KAMIKAZE (bleeding edge) --- * 10 oz Vodka Shake well with ice and strain * 10 oz Triple sec mixture into 10 shot glasses. * 10 oz lime juice Salute! --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] linker errors like ignoring invalid character `#' in expression
On Tue, Mar 29, 2011 at 7:38 PM, Jonathan Bennett wrote: > On Tue, Mar 29, 2011 at 9:06 AM, Madhavi Manchala > wrote: >> On Tue, Mar 29, 2011 at 7:16 PM, Madhavi Manchala >> wrote: >>> Dear All, >>> >>> I am seeing the following linker error messages when I try to build >>> the OpenWRT image for my board. >>> >>> arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: >>> ignoring invalid character `#' in expression >>> arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: syntax >>> error >>> >>> I googled, but there is no much luck for me. I did not understand why >>> am I getting this error. >>> >>> Any suggestions / hints would be appreciated. >>> >>> Thanks for your help, too. >>> >>> Thanks and Regards, >>> Madhavi M. >> >> Dear All, >> >> It was resolved. Thanks. > > That's great! However, a few words of explanation might be helpful in > case anyone else runs across this issue. (And I'm curious.) Dear Jonathan Bennett, It was due to a comment line which is placed in the arch/arm/kernel/vmlinux.lds file. The comment was added as //comment. However, when I looked whole vmlinux.lds file, all the comments are included in /* */. So, I changed it to /* */ instead //. Then it compiled. I do not know the exact reason for that. May be .lds files do not accept the comments in //. Thanks. Regards, Madhavi M. >> >> Regards, >> Madhavi M. > > ~Jonathan Bennett > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] linker errors like ignoring invalid character `#' in expression
On Tue, Mar 29, 2011 at 9:06 AM, Madhavi Manchala wrote: > On Tue, Mar 29, 2011 at 7:16 PM, Madhavi Manchala > wrote: >> Dear All, >> >> I am seeing the following linker error messages when I try to build >> the OpenWRT image for my board. >> >> arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: >> ignoring invalid character `#' in expression >> arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: syntax >> error >> >> I googled, but there is no much luck for me. I did not understand why >> am I getting this error. >> >> Any suggestions / hints would be appreciated. >> >> Thanks for your help, too. >> >> Thanks and Regards, >> Madhavi M. > > Dear All, > > It was resolved. Thanks. That's great! However, a few words of explanation might be helpful in case anyone else runs across this issue. (And I'm curious.) > > Regards, > Madhavi M. ~Jonathan Bennett ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] linker errors like ignoring invalid character `#' in expression
On Tue, Mar 29, 2011 at 7:16 PM, Madhavi Manchala wrote: > Dear All, > > I am seeing the following linker error messages when I try to build > the OpenWRT image for my board. > > arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: > ignoring invalid character `#' in expression > arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: syntax > error > > I googled, but there is no much luck for me. I did not understand why > am I getting this error. > > Any suggestions / hints would be appreciated. > > Thanks for your help, too. > > Thanks and Regards, > Madhavi M. Dear All, It was resolved. Thanks. Regards, Madhavi M. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] linker errors like ignoring invalid character `#' in expression
Dear All, I am seeing the following linker error messages when I try to build the OpenWRT image for my board. arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: ignoring invalid character `#' in expression arm-openwrt-linux-uclibcgnueabi-ld:arch/arm/kernel/vmlinux.lds:284: syntax error I googled, but there is no much luck for me. I did not understand why am I getting this error. Any suggestions / hints would be appreciated. Thanks for your help, too. Thanks and Regards, Madhavi M. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] iptables / missing libip4tc.so.0
On 2011-03-29 3:03 PM, Bastian Bittorf wrote: I build from trunk for ar71xx. I already tried make clean/distclean. After flashing the router i get: root@openwrt:~ iptables -h iptables: can't load library 'libip4tc.so.0' the file belongs to iptables and is defined here: package/iptables/Makefile but it is not build?: build@box:$ grep "iptables" .config | grep -v ^# CONFIG_DEFAULT_iptables=y CONFIG_PACKAGE_iptables=y CONFIG_PACKAGE_iptables-mod-conntrack=y CONFIG_PACKAGE_iptables-mod-conntrack-extra=y CONFIG_PACKAGE_iptables-mod-extra=y CONFIG_PACKAGE_iptables-mod-filter=y CONFIG_PACKAGE_iptables-mod-ipopt=y CONFIG_PACKAGE_iptables-mod-nat=y CONFIG_PACKAGE_iptables-mod-nat-extra=y CONFIG_PACKAGE_iptables-mod-ulog=y maybe this is related: https://forum.openwrt.org/viewtopic.php?pid=123430 any ideas? Did you forget to run make oldconfig after updating? - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] iptables / missing libip4tc.so.0
I build from trunk for ar71xx. I already tried make clean/distclean. After flashing the router i get: root@openwrt:~ iptables -h iptables: can't load library 'libip4tc.so.0' the file belongs to iptables and is defined here: package/iptables/Makefile but it is not build?: build@box:$ grep "iptables" .config | grep -v ^# CONFIG_DEFAULT_iptables=y CONFIG_PACKAGE_iptables=y CONFIG_PACKAGE_iptables-mod-conntrack=y CONFIG_PACKAGE_iptables-mod-conntrack-extra=y CONFIG_PACKAGE_iptables-mod-extra=y CONFIG_PACKAGE_iptables-mod-filter=y CONFIG_PACKAGE_iptables-mod-ipopt=y CONFIG_PACKAGE_iptables-mod-nat=y CONFIG_PACKAGE_iptables-mod-nat-extra=y CONFIG_PACKAGE_iptables-mod-ulog=y maybe this is related: https://forum.openwrt.org/viewtopic.php?pid=123430 any ideas? bye, Bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/2011 10:32, En/na John Crispin ha escrit: Hey Luis, Sorry for intruding here, but are you guys using the in-kernel ath9k, or the 'crap' vendor driver? no intrusion ... happy about the comments. we are talking about latest compat wireless ath9k. AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. yes, the proposed patch rewrites the eep on the fly upon a read and fakes a ES reg. this is the patch we can accept as is into owrt BTW, that's the same that the stock firmware does (according to it's bootlog), anyway it seems it has nothing to do with the performance problem. Maybe it's a problem with the layout of the caldata and/or the endiannes problem I saw, though ath9k gladly accepts the data. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/2011 9:59, En/na John Crispin ha escrit: ok, so when the work is on your desk, its ok that it takes time, but when it is on other peoples desks it is not ?! :) interested in making wifi work (I'm not going to use it), besides, performance is atrociously bad. i guess you did something wrong then To both points: I asked questions about it (ath9k) last November on this list, then asked again on ath9k-devel last December. I got no replies[*], so, yes, I probably did something wrong, and, yes, it's ok that it takes me time, since I cannot manage to get any help. Besides, I'm now trying to work on the voip stuff, that supposedly was working a year or so ago. [*]Save for Joerg Albert telling me that he had a similar problem. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Upgrade wing package to latest version
Upgrades the wing package to the latest version. The most important
changes are:
* revised implementation of the minstrel rate control algorithm
* the openwrt makefile now point to the new repository, the old one
in not available anymore
Signed-off-by: Roberto Riggio
--
Index: net/wing/files/lib/network/wing.sh
===
--- net/wing/files/lib/network/wing.sh(revision 26355)
+++ net/wing/files/lib/network/wing.sh(working copy)
@@ -36,32 +36,32 @@
exit 1
fi
-local profile rc ls prefix debug
+local profile rc ls metric prefix period tau debug
config_get profile $config profile "bulk"
-config_get rc $config rc "static"
+config_get rc $config rc "minstrel"
config_get ls $config ls "fcfs"
config_get metric $config metric "wcett"
config_get prefix $config prefix "6"
config_get period $config period "1"
config_get tau $config tau "10"
-config_get_bool debug $config debug "False"
+config_get_bool debug $config debug "false"
local hwaddr=$(echo $hwaddrs | sed 's/ .*//');
local ipaddr=$(printf "$prefix.%d.%d.%d" $(echo $hwaddr | awk -F:
'{printf "0x%s 0x%s 0x%s",$4,$5,$6}'))
local netmask=255.0.0.0
-if ! wing_template_available "profile" "$profile" "bulk"; then
+if ! wing_template_available "profile" "$profile"; then
logger -t "$config" "Unable to configure router. Exiting."
exit 1
fi
-if ! wing_template_available "rc" "$rc" "static"; then
+if ! wing_template_available "rc" "$rc"; then
logger -t "$config" "Unable to configure rate control. Exiting."
exit 1
fi
-if ! wing_template_available "ls" "$ls" "radiotap"; then
+if ! wing_template_available "ls" "$ls"; then
logger -t "$config" "Unable to configure link scheduler. Exiting."
exit 1
fi
@@ -115,10 +115,7 @@
wing_template_available() { # prefix, template, default
local template="/etc/wing/$1.$2.click"
[ ! -f $template ] && {
-template="/etc/wing/$1.$3.click"
-[ ! -f $template ] && {
-return 1
-}
+return 1
}
return 0
}
@@ -131,8 +128,12 @@
config_get ifname $1 ifname
config_get device $1 device
config_get hwmode $device hwmode "11bg"
-freq=$(iwlist $ifname freq | grep "Current Frequency" | sed -n
"s/^.*Current Frequency:\([0-9.]*\) GHz (Channel \([0-9]*\))/\1/p" | awk
'{print $1*1000}')
-freq=${freq:-"0"}
+config_get channel $device channel "0"
+[ "$channel" = "0" -o "$channel" = "auto" ] && {
+logger -t "$device" "Channel not specified. Ignoring."
+return 0
+}
+freq=$(iwlist $ifname freq | sed -n "s/^.*Channel 0*$channel :
\([0-9.]*\).*/\1/p" | awk '{print $1*1000}')
hwaddr=$(/sbin/ifconfig $ifname 2>&1 | sed -n 's/^.*HWaddr
\([0-9A-Za-z\-]*\).*/\1/p' | sed -e 's/\-/:/g' | cut -c1-17)
freqs=${freqs:+"$freqs "}$freq
hwmodes=${hwmodes:+"$hwmodes "}$hwmode
Index: net/wing/files/etc/uci-defaults/wing
===
--- net/wing/files/etc/uci-defaults/wing(revision 26355)
+++ net/wing/files/etc/uci-defaults/wing(working copy)
@@ -1,13 +1,13 @@
uci set network.mesh=interface
uci set network.mesh.proto=wing
uci set network.mesh.profile=bulk
-uci set network.mesh.rc=static
+uci set network.mesh.rc=minstrel
uci set network.mesh.ls=fcfs
uci set network.mesh.metric=wcett
uci set network.mesh.prefix=6
-uci set network.mesh.period=36000
-uci set network.mesh.tau=36
-uci set network.mesh.debug=true
+uci set network.mesh.period=1
+uci set network.mesh.tau=10
+uci set network.mesh.debug=false
cfg=$(uci add firewall zone)
uci set firewall.$cfg.name="mesh"
Index: net/wing/Makefile
===
--- net/wing/Makefile(revision 26355)
+++ net/wing/Makefile(working copy)
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=wing
-PKG_VERSION:=20101023
+PKG_VERSION:=20110329
PKG_RELEASE:=1
-PKG_REV:=daffb8d7642c4a343951d67159504ff4f4da49ed
+PKG_REV:=5c93a28b13921608750b2b5050a7e58fe3b69901
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
-PKG_SOURCE_URL:=http://github.com/create-net/click-wing.git
+PKG_SOURCE_URL:=git://github.com/rriggio/click.git
PKG_SOURC
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/2011 9:58, En/na John Crispin ha escrit: So what's the part that I should clean up? register_ath9k function, the fixups etc. the whole patch is a complete mess, whoich is not understandable, let alone the fact that it does not follow kernel code style I copied that almost verbatim from the ar71xx architecture (which has also other features that lantiq should borrow, like, e.g., the same /etc/config/network is not suitable for every profile). But then, I'm not an openwrt developer, so what should I know? Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Hey Luis, > > Sorry for intruding here, but are you guys using the in-kernel ath9k, > or the 'crap' vendor driver? no intrusion ... happy about the comments. we are talking about latest compat wireless ath9k. > > AFAIS, the current in-kernel driver relies on regulatory domain for > frequency restrictions. > It could solve your current problem. yes, the proposed patch rewrites the eep on the fly upon a read and fakes a ES reg. this is the patch we can accept as is into owrt > > But, as always, there may be hundreds of reasons why this approach may > not be possible. > i am not sure, in theroy mac80211 should handle this already. thx, John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Hi On Tue, Mar 29, 2011 at 08:59, John Crispin wrote: > On 29/03/11 09:53, Luca Olivetti wrote: >> Al 29/03/2011 9:48, En/na Luca Olivetti ha escrit: >> >>> >>> I'll see what I can do for both issues (regdomain and generic), however >>> remember that I can only test with my router and wouldn't want to >>> mislead somebody else that it should also work with his. >> > > your current patch is misleading, a generic version wont be. > >> BTW, if you can merge everything else, please do, so I can synch to svn >> and work from there. > > check the timeline first next time, happened already > >> It will take a lot of time for me to fix those issues, I'm not really > > ok, so when the work is on your desk, its ok that it takes time, but > when it is on other peoples desks it is not ?! :) > >> interested in making wifi work (I'm not going to use it), besides, >> performance is atrociously bad. Sorry for intruding here, but are you guys using the in-kernel ath9k, or the 'crap' vendor driver? AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. But, as always, there may be hundreds of reasons why this approach may not be possible. > > i guess you did something wrong then > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > Luis Correia ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team
Hi Layne, i'd change my patch delivery then by posting them to the more public wiki and posting a note here only. this way people hit by the same bug can find the patch online with their favorite search engine no matter if an openwrt dev had the time to check and push it to trunk or not. I don't know if you've read the mail posted almost a year ago here ;-), but there is a public patch repository available at: http://patchwork.cyranjo.org/ Cheers, Jochen ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
On 29/03/11 09:53, Luca Olivetti wrote: > Al 29/03/2011 9:48, En/na Luca Olivetti ha escrit: > >> >> I'll see what I can do for both issues (regdomain and generic), however >> remember that I can only test with my router and wouldn't want to >> mislead somebody else that it should also work with his. > your current patch is misleading, a generic version wont be. > BTW, if you can merge everything else, please do, so I can synch to svn > and work from there. check the timeline first next time, happened already > It will take a lot of time for me to fix those issues, I'm not really ok, so when the work is on your desk, its ok that it takes time, but when it is on other peoples desks it is not ?! :) > interested in making wifi work (I'm not going to use it), besides, > performance is atrociously bad. i guess you did something wrong then ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
> > So what's the part that I should clean up? register_ath9k function, the fixups etc. the whole patch is a complete mess, whoich is not understandable, let alone the fact that it does not follow kernel code style ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/2011 9:48, En/na Luca Olivetti ha escrit: I'll see what I can do for both issues (regdomain and generic), however remember that I can only test with my router and wouldn't want to mislead somebody else that it should also work with his. BTW, if you can merge everything else, please do, so I can synch to svn and work from there. It will take a lot of time for me to fix those issues, I'm not really interested in making wifi work (I'm not going to use it), besides, performance is atrociously bad. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/2011 9:32, En/na John Crispin ha escrit: On 29/03/11 09:26, Luca Olivetti wrote: Al 29/03/2011 8:18, En/na John Crispin ha escrit: Hi Luca, i am about to merge some of your stuff. whilste looking over the rest i noticed this -> ++arv7518_ath9k_wmac_data.eeprom_data[0x208>>1]=0x82d4; /* Spain */ ++arv7518_ath9k_wmac_data.eeprom_data[0x20a>>1]=0x1f1f; /* as in stock firmware */ we wont be able to merge generic ath9k support that locks to the reg domain of ES. That function is for the arv7518 which, AFAIK, is only available in Spain. nope available all around the world http://www.arcadyan.com/english/products/product_detail.asp?PROD_L1ID=0003&PROD_ID=0041 That doesn't resemble the router I have, mine is like this one http://www.tuadsl.com/wp-content/uploads/router-smc-7908.jpg but white. It's true that arcadyan documentation isn't widely available (they don't sell to end user and are very secretive, like lantiq, broadcom, jungo and other similar companies), so it may well be possible that they share the same board. Or not. there should be a generic arv45xx_register_ath9k function That's another matter, but since I only know the eeprom layout of the arv7518 (and then not completely) I cannot do a generic function. well, make the specific one generic I'll see what I can do for both issues (regdomain and generic), however remember that I can only test with my router and wouldn't want to mislead somebody else that it should also work with his. also, please cleanup the ath9k patches (whitespace, ...) Do you mean this one? http://patchwork.midlink.org/patch/727/ no that is a different patch So what's the part that I should clean up? Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] CAN interface module for the PEAK CAN systems HARDWARE
2011/3/29 devendra.aaru > Hello everybody, > > I compiled successfully the PEAK CAN interface module for the PCEngines > ALIX board. > I got the linux sources from the PEAK CAN developer website. > I tested them using the PEAK CAN software. > Any one interested adding this to the openwrt tree. > Please submit them as a patch. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 29/03/2011 8:18, En/na John Crispin ha escrit: Hi Luca, i am about to merge some of your stuff. whilste looking over the rest i noticed this -> ++ arv7518_ath9k_wmac_data.eeprom_data[0x208>>1]=0x82d4; /* Spain */ ++ arv7518_ath9k_wmac_data.eeprom_data[0x20a>>1]=0x1f1f; /* as in stock firmware */ we wont be able to merge generic ath9k support that locks to the reg domain of ES. That function is for the arv7518 which, AFAIK, is only available in Spain. there should be a generic arv45xx_register_ath9k function That's another matter, but since I only know the eeprom layout of the arv7518 (and then not completely) I cannot do a generic function. also, please cleanup the ath9k patches (whitespace, ...) Do you mean this one? http://patchwork.midlink.org/patch/727/ Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] CAN interface module for the PEAK CAN systems HARDWARE
Hello everybody, I compiled successfully the PEAK CAN interface module for the PCEngines ALIX board. I got the linux sources from the PEAK CAN developer website. I tested them using the PEAK CAN software. Any one interested adding this to the openwrt tree. dev. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
