Re: [OpenWrt-Devel] BRCM4716 support part 2
And I forgot the actual patch again, sorry. 2010/4/15 Bernhard Loos : > Hello > This adds two patches to brcm47xx. > 950-sbb-sysfs-files.patch is not 4716 specific and adds a bunch of > sysfs attributes to ssb devices, similiar to pci devices. > 951-brcm4716-defines.patch contains defines for registers and device > ids used on th brcm4716 > > Bernhard > n16_2.diff Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] BRCM4716 support part 2
Hello This adds two patches to brcm47xx. 950-sbb-sysfs-files.patch is not 4716 specific and adds a bunch of sysfs attributes to ssb devices, similiar to pci devices. 951-brcm4716-defines.patch contains defines for registers and device ids used on th brcm4716 Bernhard ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Missing 2.6.32.11 checksum in Backfire
Please add the 2.6.32.11 kernel checksum from r20842 [1] also to the Backfire branch. Kernel 2.6.32.11 compiles without any issues for Orion. Thorough testing will be done after tickets #7111 [2] and #7113 for Orion are applied too. Thanks Maddes [1] https://dev.openwrt.org/changeset/20842 [2] https://dev.openwrt.org/ticket/7111 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] switch config
I finnaly managed to use vlan support on WRT160NL with the following config: config interface loopback option ifname lo option protostatic option ipaddr 127.0.0.1 option netmask 255.0.0.0 config interface lan option ifname eth0.0 option type bridge option protostatic option ipaddr 192.168.2.1 option netmask 255.255.255.0 config interface wan option ifname eth1 option protodhcp config interface wan2 option ifname eth0.1 option protodhcp config switch option name eth0 option reset1 option enable_vlan 1 config switch_vlan option device eth0 option vlan 0 option ports"1 2 3 4*" config switch_vlan option device eth0 option vlan 1 option ports"0 4t" For what I tested I see two issues: CPU port is 4 and not 5 as specified in http://wiki.openwrt.org/doc/switch. This is terrible for anyone trying to start. Should this be implemented on a standard way? Or should I create a table on wiki specifying the which port is which in different routers? Exchanging 4* with 4t, i.e., putting the default vlan on the wan2 port, breaks both lan and wan2 interface. Any reason? I don't see where the untagged traffic comes... Regards, -- + Nuno Gonçalves + nuno...@gmail.com + http://nunoassimassim.blogspot.com/ + PORTUGAL E-mail sent directly from Google Mail webmail using HTTPS on behalf of Nuno João Pinto Gonçalves, birth date 1986-11-16. E-mail headers provide good assurance that this message was not tampered and originates from nuno...@gmail.com. If you require additional security, I may provide on request X509 electronic signature under Portuguese government chain. Se precisar de assinatura digital do Cartão de Cidadão, de uma apitadela. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Problem with libreadline?
Hello I found that in current OpenWRT, programs that uses libreadline (i checked two, birdc an atftp) are statically linked with it. The cause for this is that staging_dir/target-XXX/usr/lib contains libreadline.a, libreadline.so.5.2 and libreadline.so.5 (symlink), but does not contain libreadline.so (symlink). Linker tries to find libreadline.so and because it is missing, it uses libreadline.a (and links statically). If i manually add the symlink, programs are linked dynamically. Is this a bug in libreadline package? -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so." signature.asc Description: Digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] sysupgrade: mount: mounting mini_fo:/overlay on /mnt failed: Function not implemented
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Does the message "mount: mounting mini_fo:/overlay on /mnt failed: > Function not implemented" represent any bug? No. It was always there iirc. ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvFhPsACgkQdputYINPTPOTWQCdEh/npsQOiviAmvSPL2YHWZ3n rIoAnAn6/Y4ale3LD1DOKFWfzp5vqs1L =mtZN -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] sysupgrade: mount: mounting mini_fo:/overlay on /mnt failed: Function not implemented
Latest trunk flash: Connecting to 192.168.1.182 (192.168.1.182:80) openwrt.bin 100% |***| 3136k --:--:-- ETA r...@openwrt:/tmp# sysupgrade -n openwrt.bin Switching to ramdisk... mount: mounting mini_fo:/overlay on /mnt failed: Function not implemented Performing system upgrade... Unlocking firmware ... Writing from to firmware ... Upgrade completed Rebooting system... Connection closed by foreign host. Does the message "mount: mounting mini_fo:/overlay on /mnt failed: Function not implemented" represent any bug? Regards, -- + Nuno Gonçalves + nuno...@gmail.com + http://nunoassimassim.blogspot.com/ + PORTUGAL E-mail sent directly from Google Mail webmail using HTTPS on behalf of Nuno João Pinto Gonçalves, birth date 1986-11-16. E-mail headers provide good assurance that this message was not tampered and originates from nuno...@gmail.com. If you require additional security, I may provide on request X509 electronic signature under Portuguese government chain. Se precisar de assinatura digital do Cartão de Cidadão, de uma apitadela. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] minstrel_ht crashing kernel on IXP4xx platform during iperf throughput test
maybe I should report to ath9k-devel list, but I think it might be the problem of OpenWrt configuration, caused by using the module minstrel_ht. the reason I try minstrel_ht is I could only get around 50Mbpsthroughput rate by using ath9k for my AR9280 card. some developer saidthe low throughput is a known problem for ath9k on IPX4xx platform, itwas kind of optimizing work. I still cannot see any light on thisproblem since last year. I sawthe crashing on several trunk since OpenWrt r20294, till r20851, yes itwas caused by iperf test while it was just nice by ping test. topology: PC1 - STA - AP - PC2 iperf/ping was form PC1 to PC2, the crash happened on both AP and STA, see attachment for the log, Thank You !! r...@openwrt:/# [ cut here ] WARNING: at /home/jun/os/openwrt/acpe/20851/build_dir/linux-ixp4xx_generic/compat-wireless-2010-04-13/net/mac80211/rc80211_minstrel_ht.c:118) Modules linked in: nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xh Backtrace: Function entered at [] from [] r7: r6:bf078894 r5:bf07f3c0 r4:0076 Function entered at [] from [] Function entered at [] from [] r7:bf07c264 r6:c3286280 r5:0020 r4:0008 Function entered at [] from [] Function entered at [] from [] Function entered at [] from [] Function entered at [] from [] Function entered at [] from [] Function entered at [] from [] Function entered at [] from [] r7:c05d6140 r6: r5:c05c56e0 r4: Function entered at [] from [] r7:0100 r6:0006 r5:0001 r4:0018 Function entered at [] from [] Function entered at [] from [] Function entered at [] from [] Exception stack(0xc05bbf58 to 0xc05bbfa0) bf40: c05bcd58 c05bcd58 bf60: c05bbf90 6013 c05ba000 c05d13c4 c05bda08 c05bda00 0001c630 690541c2 bf80: 0001c52c c05bbfbc c05bbfa0 c05bbfa0 c03bce54 c03bce54 6013 r7:c05bda00 r6:0080 r5:001f r4: Function entered at [] from [] r7:c05bda00 r6:c03b9e10 r5:c05d138c r4:c05d8994 Function entered at [] from [] Function entered at [] from [<8034>] r5:c05d1444 r4:39fd ---[ end trace 5d087f5d7e9a8582 ]--- Unable to handle kernel NULL pointer dereference at virtual address pgd = c3304000 [] *pgd=03303031, *pte=, *ppte= Internal error: Oops: 817 [#1] last sysfs file: /sys/kernel/uevent_seqnum Modules linked in: nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xh CPU: 0Tainted: GW (2.6.32.10 #10) pc : []lr : []psr: a013 sp : c32bd8a0 ip : 0001 fp : c32bd8d4 r10: c33f01cc r9 : c3c8a1e0 r8 : c32bd908 r7 : c3313dc0 r6 : c33f r5 : c3313dc0 r4 : c3c8b2c0 r3 : r2 : 0097 r1 : 0008 r0 : 00ff Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 39ff Table: 03304000 DAC: 0015 Process klogd (pid: 1247, stack limit = 0xc32bc270) Stack: (0xc32bd8a0 to 0xc32be000) d8a0: 0006 c330b000 0086 c3c8b2c0 c3313dc0 c32bd960 d8c0: c3313da0 c38b3054 c32bd954 c32bd8d8 bf068400 bf06002c c3313da0 c32bd960 d8e0: c333802e c3313da0 c333802e bf032d40 c3d514a0 d900: c32bd964 c32bd910 c38b2200 c38b3054 c3c8b650 c3313da0 ff00 00ff d920: 00ff c3338000 c3313da0 c38b2200 c3c8b2c0 0008 c32bd960 d940: c3313dc0 0002 c32bd9ac c32bd958 bf068d88 bf067b78 c32bd98c d960: c3313da0 c38b2200 c3c8b2c0 c33f bf0e7ec4 0800 0002 d980: c32bd9ac c3c8b000 c3313da0 c3c8b2c0 0008 c38b2200 c3313dc0 c3c4402e d9a0: c32bd9ec c32bd9b0 bf0690d8 bf068d20 bf0dcf48 bf0a7f60 c33f c3c8b2c0 d9c0: c32bd9ec c3c8b000 c3c44046 c3313da0 0008 0008 001a d9e0: c32bda7c c32bd9f0 bf06a7c4 bf068f0c 0070 0003 0006 c32bda18 da00: c3c8b000 c3c8b2c0 c38b2200 bf049f92 c3c44050 c3c44050 8801 00804867 da20: d7300080 4867d86f 000aeb0f fb32 c32bdae0 c333558c 0004 c38b29f8 da40: 0007 c3d51d10 c32bdb04 c32b8801 bf0dcf48 c05ddf68 c31fc0c8 c2d9dac0 da60: c3313da0 c3c8b000 c31fc0c8 c05ddf70 c32bdabc c32bda80 c050550c bf069c04 da80: bf053c38 bf079ae4 c3313da0 c3313da0 c38b2200 c31fc0c8 c2d9dac0 daa0: c3c8b000 c3313da0 c32bdae4 c32bdac0 c0516924 c05052ec dac0: 00228681 c2d9dac0 c31fc0c8 c3c8b000 c32bdb14 c32bdae8 dae0: c0505970 c05168e4 c2d9db1c c3313da0 c3313da0 c308e460 c32e22c0 db00: c05ddf70 c32bdb2c c32bdb18 c0567d08 c050571c c3313da0 db20: c32bdb54 c32bdb30 c0567d70 c0567cb0 c32bdb5c 001a c3335560 c38b29f8 db40: c3313da0 c32bdb7c c32bdb58 c0567e2c c0567d1c c32bdb84 c32bdb68 db60: 0003 c3cadf20 c3313da0 c32bdb8c c32bdb80 c0567e74 c0567d8c db80: c32bdbc4 c32bdb90 c0568a54 c0567e48 bf068cf4 bf06da10 00ff dba0:
