Re: [OpenWrt-Devel] gpio-led bug
Am 23.12.2009 um 12:48 schrieb Nuno Gonçalves: > The follow commands cause a reboot on a WRT160NL: > > cd $1 && echo netdev > trigger && echo $2 > device_name && echo $3 > mode I've noticed similar problems on an TP-Link tl-wr941nd. Stefan -- Stefan BethkeFon +49 151 14070811 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] New Enhancement Ticket (with patch) for RT210W support
(Reminder Copy of original message)
Forwarded Message
> From: Spudz76
> Reply-to: spud...@gmail.com
> To: OpenWrt Development List
> Subject: New Enhancement Ticket (with patch) for RT210W support
> Date: Fri, 18 Dec 2009 16:02:48 -0600
>
> This is for an ancient platform, Askey RT210W, which is the same board
> used in Belkin F5D4230-4 before but not including v1444 (the old larger
> format model with MiniPCI BCM4306 wifi and dual antennae) and original
> Siemens SE505v1 (w/o CFE or RAM upgrade), and probably several others.
>
> Sets up proper button/LED mappings and returns a proper platform string
> ("Askey RT210W"), that is all that was required. Platform works OK
> without this but detection failed and LEDs were not mapped. GPIO 7 is
> connected to the reset switch but it is also hardwired somehow to SoC
> reset, so it is unlikely the software could pick up the event prior to
> the hardware forcibly resetting - mapped it anyway.
>
> Please apply this patch to the 8.09 branch, following my previous
> WRT300Nv11 patch. Let me know if I need to
> resubmit same patch for trunk version as well.
>
> https://dev.openwrt.org/ticket/6380
>
> (patch attached to ticket, not included here)
>
> Thanks!
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] New Enhancement Ticket (with patch) for WRT300Nv1.1 support
(Reminder Copy of original message) Forwarded Message > From: Spudz76 > Reply-to: spud...@gmail.com > To: OpenWrt Development List > Subject: New Enhancement Ticket (with patch) for WRT300Nv1.1 support > Date: Fri, 18 Dec 2009 15:31:39 -0600 > > The WRT300N versions so far supported did not include the v1.1 which is > a bit different than the others. The current build does not run properly > and inits the switch incorrectly. This patch adds detection to > broadcom-diag and patches the netconfig script to avoid the incorrect > switch settings. Also patches image makefile to add proper board ID for > successful TFTP flash, and repair previous v1 definition as well > (signature right, firmware version wrong). A bonus, added a profile for > this model to pull in the proper wl driver flavor (MIMO) and the proper > Ethernet driver (57xx). > > Please apply this patch to the 8.09 branch. Let me know if I need to > resubmit same patch for trunk version as well. > > https://dev.openwrt.org/ticket/6379 > > (patch attached to ticket, not included here) > > Thanks! > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] gpio-led bug
The follow commands cause a reboot on a WRT160NL: cd $1 && echo netdev > trigger && echo $2 > device_name && echo $3 > mode where $1 is in: /sys/class/leds/wrt160nl\:amber\:wps/ /sys/class/leds/wrt160nl\:blue\:power/ /sys/class/leds/wrt160nl\:blue\:wlan/ /sys/class/leds/wrt160nl\:blue\:wps/ $2 is in: eth0 eth1 br-lan $3 is in: tx rx example 1: cd /sys/class/leds/wrt160nl\:blue\:wlan/ echo netdev > trigger echo eth0 > device_name echo rx > mode [unexpected reboot] example 2: [WAN cable disconnected] cd /sys/class/leds/wrt160nl\:blue\:wlan/ echo netdev > trigger echo eth1 > device_name echo rx > mode [...] [I connect WAN cable] [unexpected reboot] Regards, -- \ Nuno Gonçalves / \ Bugs? Features! / \ nuno...@gmail.com / PORTUGAL Sent from Coimbra, 06, Portugal ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kamikaze trunk, uClibc-0.9.30.1 Xscale EABI not working
Hi; Glibc-2.7 works with EABI support while eglibc-trunk has compilation errors.. Regards, KH _ From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Teh Kok How Sent: Wednesday, December 23, 2009 6:10 PM To: openwrt-devel@lists.openwrt.org Subject: [OpenWrt-Devel] kamikaze trunk,uClibc-0.9.30.1 Xscale EABI not working Hi; [3.39] device=eth0, addr=10.0.51.200, mask=255.255.255.0, gw=255.255.255.255, [3.40] host=ixdp425, domain=, nis-domain=(none), [3.40] bootserver=10.0.51.38, rootserver=10.0.51.38, rootpath= [3.41] Looking up port of RPC 13/2 on 10.0.51.38 [3.43] Looking up port of RPC 15/1 on 10.0.51.38 [3.44] VFS: Mounted root (nfs filesystem) on device 0:14. [3.44] Freeing init memory: 124K [3.52] eth0: link up, speed 100 Mb/s, full duplex [3.59] Kernel panic - not syncing: Attempted to kill init! [3.60] [] (unwind_backtrace+0x0/0xe0) from [] (panic+0x4c/0x13c) [3.61] [] (panic+0x4c/0x13c) from [] (do_exit+0x64/0x708) [3.62] [] (do_exit+0x64/0x708) from [] (do_group_exit+0xb0/0xe4) [3.62] [] (do_group_exit+0xb0/0xe4) from [] (get_signal_to_deliver+0x390/0x3ec) [3.63] [] (get_signal_to_deliver+0x390/0x3ec) from [] (do_notify_resume+0x64/0x5d8) [3.64] [] (do_notify_resume+0x64/0x5d8) from [] (work_pending+0x1c/0x20) [3.65] Rebooting in 1 seconds.. [kh...@khteh-pc:/usr/src/root-ixp4xx 2]$ file bin/busybox bin/busybox: ELF 32-bit MSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped [kh...@khteh-pc:/usr/src/root-ixp4xx 3]$ readelf -h bin/busybox | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 4]$ readelf -a bin/busybox | grep NEEDED 0x0001 (NEEDED) Shared library: [libcrypt.so.0] 0x0001 (NEEDED) Shared library: [libm.so.0] 0x0001 (NEEDED) Shared library: [libc.so.0] [kh...@khteh-pc:/usr/src/root-ixp4xx 5]$ readelf -a bin/busybox | grep -A1 INTERP INTERP 0x000114 0x8114 0x8114 0x00014 0x00014 R 0x1 [Requesting program interpreter: /lib/ld-uClibc.so.0] [kh...@khteh-pc:/usr/src/root-ixp4xx 6]$ readelf -h lib/libuClibc-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 7]$ readelf -h lib/libm-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 8]$ readelf -h lib/ld-uClibc-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 9]$ readelf -h lib/libcrypt-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 10]$ Attached is the uClibc-0.9.30.1 config that I use. Any insight is appreciated. Regards, KH ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kamikaze trunk, uClibc-0.9.30.1 Xscale EABI not working
Hi; [3.39] device=eth0, addr=10.0.51.200, mask=255.255.255.0, gw=255.255.255.255, [3.40] host=ixdp425, domain=, nis-domain=(none), [3.40] bootserver=10.0.51.38, rootserver=10.0.51.38, rootpath= [3.41] Looking up port of RPC 13/2 on 10.0.51.38 [3.43] Looking up port of RPC 15/1 on 10.0.51.38 [3.44] VFS: Mounted root (nfs filesystem) on device 0:14. [3.44] Freeing init memory: 124K [3.52] eth0: link up, speed 100 Mb/s, full duplex [3.59] Kernel panic - not syncing: Attempted to kill init! [3.60] [] (unwind_backtrace+0x0/0xe0) from [] (panic+0x4c/0x13c) [3.61] [] (panic+0x4c/0x13c) from [] (do_exit+0x64/0x708) [3.62] [] (do_exit+0x64/0x708) from [] (do_group_exit+0xb0/0xe4) [3.62] [] (do_group_exit+0xb0/0xe4) from [] (get_signal_to_deliver+0x390/0x3ec) [3.63] [] (get_signal_to_deliver+0x390/0x3ec) from [] (do_notify_resume+0x64/0x5d8) [3.64] [] (do_notify_resume+0x64/0x5d8) from [] (work_pending+0x1c/0x20) [3.65] Rebooting in 1 seconds.. [kh...@khteh-pc:/usr/src/root-ixp4xx 2]$ file bin/busybox bin/busybox: ELF 32-bit MSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped [kh...@khteh-pc:/usr/src/root-ixp4xx 3]$ readelf -h bin/busybox | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 4]$ readelf -a bin/busybox | grep NEEDED 0x0001 (NEEDED) Shared library: [libcrypt.so.0] 0x0001 (NEEDED) Shared library: [libm.so.0] 0x0001 (NEEDED) Shared library: [libc.so.0] [kh...@khteh-pc:/usr/src/root-ixp4xx 5]$ readelf -a bin/busybox | grep -A1 INTERP INTERP 0x000114 0x8114 0x8114 0x00014 0x00014 R 0x1 [Requesting program interpreter: /lib/ld-uClibc.so.0] [kh...@khteh-pc:/usr/src/root-ixp4xx 6]$ readelf -h lib/libuClibc-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 7]$ readelf -h lib/libm-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 8]$ readelf -h lib/ld-uClibc-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 9]$ readelf -h lib/libcrypt-0.9.30.1.so | grep Flags Flags: 0x502, has entry point, Version5 EABI [kh...@khteh-pc:/usr/src/root-ixp4xx 10]$ Attached is the uClibc-0.9.30.1 config that I use. Any insight is appreciated. Regards, KH uClibc-0.9.30.1-config Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] 2.6.30+: BCM5354 USB LOCKUP (ehci-ssb) due to missed kernel changes
On Tue, Dec 22, 2009 at 11:16:35PM +0100, Michael Buesch wrote: > On Tuesday 22 December 2009 22:29:32 Andreas Mohr wrote: > > Now that this annoying issue is out of the way, how to go forward? > > By sending a patch? Not the worst way to deal with it, admittedly. > > And I would be very pleased if ehci-ssb.c could find its way into mainline > > pretty soon, > > Yeah. Care to do so? Huh what me? :) I'll get this nailed. I wouldn't want this unfortunate thing to happen again. Thanks, Andreas Mohr ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
