[OpenWrt-Devel] kernel panic with kmod-brcm-wl and dir-320
Hello, I have a DLink dir-320. I installed openwrt on it ( trunk r26841https://dev.openwrt.org/changeset/26841). Then I installed kmod-brcm-wl,wlc,wl,nas. I disabled the b43 module, but when booting I get a kernel panic: Unhandled kernel unaligned access[#1]: Cpu 0 $ 0 : 1000f800 0001 0760 $ 4 : 81afc100 81a588c0 0800 $ 8 : 80116f68 00401d00 $12 : 7fe400a0 0022 $16 : 0018 81a28200 81a588c0 $20 : 80c4 0006 00a0 $24 : 80e114e0 $28 : 80d8e000 80d8fad8 1000 80e24d2c Hi: Lo: 04a6 epc : 80e24d2c 0x80e24d2c Tainted: P ra: 80e24d2c 0x80e24d2c Status: 1000f803KERNEL EXL IE Cause : 00800014 BadVA : 0001 PrId : 00029029 (Broadcom BMIPS3300) Modules linked in: nf_conntrack_irc nf_conntrack_ftp xt_conntrack xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc wl(P) crc_ccitt arc4 aes_generic crypto_algapi usb_storage ohci_hcd ehci_hcd sd_mod ext4 jbd2 usbcore scsi_mod nls_base mbcache crc16 switch_robo switch_core diag Process wlc (pid: 781, threadinfo=80d8e000, task=81a14a28, tls=2b03c2d0) Stack : 80d8fb30 80c4070c 80c4 81a28200 0038 b8005164 0018 0018 b8005164 80c4070c 80c4 0006 b8005540 b8005000 b8005520 80e57bcc 80c4 b8005f98 80c4070c 80c7 0006 80c4070c 090b0e0a 80c4050e 0006 0001 b800552c 0006 80c4 80c4 2b07 80c4 80c4070c 80c40c5c 0002 7fe400f0 80e43af0 ... Call Trace:[80e57bcc] 0x80e57bcc [80e43af0] 0x80e43af0 [80e57db0] 0x80e57db0 [80e43f14] 0x80e43f14 [80e31e30] 0x80e31e30 [80e55fb8] 0x80e55fb8 [80e049e8] 0x80e049e8 [80e2ec84] 0x80e2ec84 [80e38f84] 0x80e38f84 [80022234] 0x80022234 [80022234] 0x80022234 [8002231c] 0x8002231c [8002231c] 0x8002231c [8002261c] 0x8002261c [8002261c] 0x8002261c [80026fb0] 0x80026fb0 [8027701b] 0x8027701b [80022234] 0x80022234 [80e03bd0] 0x80e03bd0 [8001486c] 0x8001486c [8018fcb8] 0x8018fcb8 [8017d494] 0x8017d494 [8008a524] 0x8008a524 [80099550] 0x80099550 [80178358] 0x80178358 [80178ac0] 0x80178ac0 [801783e4] 0x801783e4 [800995f0] 0x800995f0 [80178dc8] 0x80178dc8 [80087428] 0x80087428 [8000de50] 0x8000de50 Code: 8e2400b4 0c381668 02602821 ac40 8e3000b4 02602821 0c381668 02002021 8e26013c Kernel panic - not syncing: Fatal exception in interrupt Regards ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 06/05/11 15:16, John Crispin wrote: On 06/05/11 15:13, Peter Lebbing wrote: So, can someone please commit my patch, http://patchwork.midlink.org/patch/906/ ? patch looks ok, let me apply it Problems? Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://wwwhome.cs.utwente.nl/~lebbing/pubkey.txt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] packages: Update pango to 1.28.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jochen I got some errors[1] when compile pango-1.28.4. the pango-1.26.0 compile fine. when I apply this patch: http://fidelio.qi-hardware.com/~xiangfu/openwrt-xburst.patches/pango-automake.patch I got those errors: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-05072011-1900/BUILD_LOG.05072011-2107.last100 it should auto detect 'gtkdoc-rebase' right? thanks in advance. [1] Error Message: - -- Installing ./html/pango.devhelp - -- Installing ./html/pango.devhelp2 - -- Installing ./html/pango.html - -- Installing ./html/rendering.html - -- Installing ./html/right.png - -- Installing ./html/rotated-text.png - -- Installing ./html/style.css - -- Installing ./html/tools.html - -- Installing ./html/up.png /bin/bash: line 20: --relative: command not found make[6]: *** [install-data-local] Error 127 make[6]: Leaving directory `/home/xiangfu/openwrt-xburst.full_system/build_dir/target-mipsel_uClibc-0.9.30.1/pango-1.28.4/docs' make[5]: *** [install-am] Error 2 make[5]: Leaving directory `/home/xiangfu/openwrt-xburst.full_system/build_dir/target-mipsel_uClibc-0.9.30.1/pango-1.28.4/docs' make[4]: *** [install] Error 2 make[4]: Leaving directory `/home/xiangfu/openwrt-xburst.full_system/build_dir/target-mipsel_uClibc-0.9.30.1/pango-1.28.4/docs' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/home/xiangfu/openwrt-xburst.full_system/build_dir/target-mipsel_uClibc-0.9.30.1/pango-1.28.4' make[2]: *** [/home/xiangfu/openwrt-xburst.full_system/build_dir/target-mipsel_uClibc-0.9.30.1/pango-1.28.4/.built] Error 2 make[2]: Leaving directory `/home/xiangfu/openwrt-xburst.full_system/feeds/packages/Xorg/lib/pango' make[1]: *** [package/feeds/packages/pango/compile] Error 2 make[1]: Leaving directory `/home/xiangfu/openwrt-xburst.full_system' make: *** [package/pango/compile] Error 2 On 04/18/2011 12:49 AM, Jochen Friedrich wrote: Signed-off-by: Jochen Friedrich joc...@scram.de --- Xorg/lib/pango/Makefile |8 Xorg/lib/pango/patches/001-automake-compat.patch | 12 2 files changed, 4 insertions(+), 16 deletions(-) ... - -- Best Regards Xiangfu Liu http://www.openmobilefree.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3H9UkACgkQRRAEFRxkgLQOwwCfVuFmdr+GM+qUjrYDh07EtGNR bfkAnj6dcqSn7dvTbbJDNMu8aoGxsQxN =aHwz -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 16:01, Peter Lebbing wrote: On 06/05/11 15:16, John Crispin wrote: On 06/05/11 15:13, Peter Lebbing wrote: So, can someone please commit my patch, http://patchwork.midlink.org/patch/906/ ? patch looks ok, let me apply it Problems? Peter. apart from not liking this rather impolite single word style of (mis-)communication i think there are no problems. i was actually just in the process of testing your patch and getting it ready for a commit when i received your motivational email ;) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ram on dir-320
05.05.2011 17:34, Cristian Astorino wrote: Yes, it's similar,but not the same. I tried now and there is not difference between warm and hard reset. Ram detected is always 23MB. I think there are some problems with memory detection routines. Hmm, reading your message I got curious about what amount of ram is being detected by OpenWRT on my DIR-320. Here it is: root@dir320lx2home:/etc/config# cat /proc/meminfo MemTotal: 29800 kB ... It's more that you've got but still less than it should be for 32Mb. Unfortunatelly I don't remember the OpenWRT trunk revision I used to build firmware for this DIR-320 but I'm pretty sure it was pretty long time ago around spring 2010. -- Best regards, Alexey Loukianov mailto:mooro...@mail.ru System Engineer,Mob.:+7(926)218-1320 *nix Specialist signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
Al 09/05/2011 0:31, En/na Luca Olivetti ha escrit: It turns out that the ebu, in the gpio_led structure, uses gpio starting from 32, so defining fake leds using gpios 32-40 I could map all missing leds. Since they're active low, I used lq_register_gpio_ebu(0xff), so they all turn off as soon as the kernel calls lq_register_gpio_ebu (contrary to leds controlled by real gpio, they're lit at power on, the original firmware turns them off very soon). The next question is, how can I control (some of) the leds from an userspace program? Opening the /sys/class/leds/led name/trigger file and alternatively writing none or default-on? Or the same but with the brightness file? Writing a trigger module? (and how since the trigger comes from user space)? Open the gpio directly? (again, how?) Some other way? TIA -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
On 09/05/11 16:59, Luca Olivetti wrote: Al 09/05/2011 0:31, En/na Luca Olivetti ha escrit: It turns out that the ebu, in the gpio_led structure, uses gpio starting from 32, so defining fake leds using gpios 32-40 I could map all missing leds. Since they're active low, I used lq_register_gpio_ebu(0xff), so they all turn off as soon as the kernel calls lq_register_gpio_ebu (contrary to leds controlled by real gpio, they're lit at power on, the original firmware turns them off very soon). The next question is, how can I control (some of) the leds from an userspace program? Opening the /sys/class/leds/led name/trigger file and alternatively writing none or default-on? Or the same but with the brightness file? Writing a trigger module? (and how since the trigger comes from user space)? Open the gpio directly? (again, how?) Some other way? TIA Hi luca, if it is a gpio cd /sys/class/gpio echo 13 export echo out gpio13/direction echo 0/1 gpio13/brightness for a led in userland echo default-on /sys/class/leds/led name/trigger or in kernel space use the default trigger as shown in this patch https://lists.openwrt.org/pipermail/openwrt-devel/2008-January/001618.html also look at /etc/init.d/led it allows you to setup your leds based on a uci file so ideally you give your leds a default brightness / trigger in the kernel code and then setup the others in userland via uci depending on which works best / makes sense for the specific case ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
Hi, a very silly question is therer a 2/2 to go with this 1/2 patch ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 16:01, Peter Lebbing wrote: On 06/05/11 15:16, John Crispin wrote: On 06/05/11 15:13, Peter Lebbing wrote: So, can someone please commit my patch, http://patchwork.midlink.org/patch/906/ ? patch looks ok, let me apply it Problems? Peter. applied in r26865, thx ! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 16:10, John Crispin wrote: On 09/05/11 16:01, Peter Lebbing wrote: Problems? apart from not liking this rather impolite single word style of (mis-)communication i think there are no problems. Oh, I'm very sorry. It was in no way meant to be impolite. It was simply meant to have the same connotation as Are there any problems with the patch that should be looked at first, but shorter. Perhaps even occupying less of your time while reading it. i was actually just in the process of testing your patch and getting it ready for a commit when i received your motivational email ;) Seeing how quick patch submission - commit messages sometimes ping-pong on the list, I got the impression it was a matter of pressing a button, barring any error messages. So I was somewhat surprised at only having a message let me apply it, and not the actual commit message, and was trying to pose an open question whether it did not work out to satisfaction... Miscommunication is the correct word here. Sorry about that. Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://wwwhome.cs.utwente.nl/~lebbing/pubkey.txt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 18:21, Peter Lebbing wrote: On 09/05/11 16:10, John Crispin wrote: On 09/05/11 16:01, Peter Lebbing wrote: Problems? apart from not liking this rather impolite single word style of (mis-)communication i think there are no problems. Oh, I'm very sorry. It was in no way meant to be impolite. It was simply meant to have the same connotation as Are there any problems with the patch that should be looked at first, but shorter. Perhaps even occupying less of your time while reading it. i was actually just in the process of testing your patch and getting it ready for a commit when i received your motivational email ;) Seeing how quick patch submission - commit messages sometimes ping-pong on the list, I got the impression it was a matter of pressing a button, barring any error messages. So I was somewhat surprised at only having a message let me apply it, and not the actual commit message, and was trying to pose an open question whether it did not work out to satisfaction... Miscommunication is the correct word here. Sorry about that. Peter. no worries, i intended to apply it before the weekend, but then the weekend arrived, bringing lots of sun, reducing the available time considerably :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 17:22, John Crispin wrote: a very silly question is therer a 2/2 to go with this 1/2 patch ? That is a patch that I posted to have it available to people, but not for inclusion in OpenWRT yet. From my 0/2 mail: I am submitting for inclusion in OpenWRT the driver for the M chip. Since I don't have the FC chip, I cannot test if it all works as you would expect and hope for that chip. I still include a patch enabling its support, but not for inclusion in OpenWRT just now. If other people feel they have sufficiently tested that the driver works, they are free to submit it for inclusion themselves. I will try to offer support, but it's somewhat limited without hardware :). The whole 0/2 mail can be found at https://lists.openwrt.org/pipermail/openwrt-devel/2011-April/010525.html The 2/2 patch is at http://patchwork.midlink.org/patch/899/, but I feel people should test it more first before it should be included in OpenWRT. Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://wwwhome.cs.utwente.nl/~lebbing/pubkey.txt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 18:36, Peter Lebbing wrote: On 09/05/11 17:22, John Crispin wrote: a very silly question is therer a 2/2 to go with this 1/2 patch ? That is a patch that I posted to have it available to people, but not for inclusion in OpenWRT yet. From my 0/2 mail: I am submitting for inclusion in OpenWRT the driver for the M chip. Since I don't have the FC chip, I cannot test if it all works as you would expect and hope for that chip. I still include a patch enabling its support, but not for inclusion in OpenWRT just now. If other people feel they have sufficiently tested that the driver works, they are free to submit it for inclusion themselves. I will try to offer support, but it's somewhat limited without hardware :). The whole 0/2 mail can be found at https://lists.openwrt.org/pipermail/openwrt-devel/2011-April/010525.html The 2/2 patch is at http://patchwork.midlink.org/patch/899/, but I feel people should test it more first before it should be included in OpenWRT. Peter. ok, patchwork was down earlier, so i failed to find it... let me have a look at that stuff aswell ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3 1/2] (respin) 802.1Q VLAN support for ADM6996M/ADM6996FC
On 09/05/11 17:24, John Crispin wrote: applied in r26865, thx ! Thanks, great! Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://wwwhome.cs.utwente.nl/~lebbing/pubkey.txt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
2011/5/8 Andrej Vlašić andrej.vlas...@gmail.com I tried 29 again now, and no power, also tried some others, nothing. If someone want's to see here is how power is set in original fw: http://pastebin.com/00vJxdYa http://pastebin.com/00vJxdYa Another question about usb power. Is it possible that on my board USB clock gating is different than one set in current dwc_otg_ifx.c. There it says: // set clock gating writel(readl(DANUBE_CGU_IFCCR) | 0x30, DANUBE_CGU_IFCCR); On mine board it says: // set clock gating // JR: This means:: USB clock source is special internal clock generated from 36 MHz source set_bit (4, DANUBE_CGU_IFCCR); set_bit (5, DANUBE_CGU_IFCCR); Thanx for any answers ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
Another question about usb power. Is it possible that on my board USB clock gating is different than one set in current dwc_otg_ifx.c. There it says: // set clock gating writel(readl(DANUBE_CGU_IFCCR) | 0x30, DANUBE_CGU_IFCCR); On mine board it says: // set clock gating // JR: This means:: USB clock source is special internal clock generated from 36 MHz source set_bit (4, DANUBE_CGU_IFCCR); set_bit (5, DANUBE_CGU_IFCCR); Hi, BIT(4)|BIT(5) == 0x30 ;) however, i will review the driver code later to make sure usb power is setup properly John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
On 09/05/11 20:01, John Crispin wrote:
Another question about usb power.
Is it possible that on my board USB clock gating is different than one set
in current dwc_otg_ifx.c.
There it says:
// set clock gating
writel(readl(DANUBE_CGU_IFCCR) | 0x30, DANUBE_CGU_IFCCR);
On mine board it says:
// set clock gating
// JR: This means:: USB clock source is special internal clock
generated from 36 MHz source
set_bit (4, DANUBE_CGU_IFCCR);
set_bit (5, DANUBE_CGU_IFCCR);
Hi,
BIT(4)|BIT(5) == 0x30 ;)
however, i will review the driver code later to make sure usb power is
setup properly
John
inside
build_dir/linux-lantiq_xway/linux-2.6.37.6/drivers/usb/dwc_otg/dwc_otg_driver.c
you will find this code
static int __devinit
dwc_otg_driver_probe(struct platform_device *_dev)
{
int retval = 0;
dwc_otg_device_t *dwc_otg_device;
int pin = (int)_dev-dev.platform_data;
int32_t snpsid;
struct resource *res;
gusbcfg_data_t usbcfg = {.d32 = 0};
// GPIOs
if(pin = 0)
{
gpio_request(pin, usb_power);
gpio_direction_output(pin, 1);
gpio_set_value(pin, 1);
gpio_export(pin, 0);
}
dev_dbg(_dev-dev, dwc_otg_driver_probe (%p)\n, _dev);
try adding printk(foo %d\n, pin); between the // GPIOs and the if
( and see what the bootlog says
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFC] Reclaim unused space in WNDR3700 image (and maybe others?)
Gábor- I’d like your thoughts (and others’) on my proposed patch at https://dev.openwrt.org/ticket/8781 Currently, the WNDR3700 images reserve 1MB for the kernel, whether or not the kernel is actually anywhere near that size. It can be smaller, in which case space is wasted, or it can in theory be larger, in which case a broken image would be produced. Given that a 64kB block size is in use, I find that my kernels fit neatly in 832kB, which frees up 192kB of flash for other purposes. That’s a decent improvement on a system that might have as little as 8MB of flash. I realize that this approach can apply to more than just the WNDR3700. Certainly it’d work for some other members of the ar71xx family, and probably other targets as well. I haven’t tried to solve the problem in a more generic way yet. Do you think that this is something worth pursuing (or checking in as-is and iterating on) or am I doomed to continue carrying this as a local patch? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Update usb-modeswitch to v1.1.7
On 04/05/11 21:32, Layne Edwards wrote: Signed-off-by: Layne Edwards ledward...@gmail.com Index: feeds/packages/utils/usb-modeswitch/Makefile === --- feeds/packages/utils/usb-modeswitch/Makefile (revision 26751) +++ feeds/packages/utils/usb-modeswitch/Makefile (working copy) @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=usb-modeswitch -PKG_VERSION:=1.1.4 +PKG_VERSION:=1.1.7 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=http://www.draisberghof.de/usb_modeswitch -PKG_MD5SUM:=a04db36bd0fc6fb303df7567f677b714 +PKG_MD5SUM:=b75e42b7b2d30e9d4cbd5c159f925247 include $(INCLUDE_DIR)/package.mk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel this and the data package update - applied in r26866, thx! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
Al 09/05/11 17:14, En/na John Crispin ha escrit:
The next question is, how can I control (some of) the leds from an
userspace program?
Opening the /sys/class/leds/led name/trigger file and alternatively
writing none or default-on?
Or the same but with the brightness file?
Writing a trigger module? (and how since the trigger comes from user
space)?
Open the gpio directly? (again, how?)
Some other way?
TIA
Hi luca,
if it is a gpio
cd /sys/class/gpio
echo 13 export
echo out gpio13/direction
echo 0/1 gpio13/brightness
for a led in userland echo default-on /sys/class/leds/led name/trigger
or in kernel space use the default trigger as shown in this patch
https://lists.openwrt.org/pipermail/openwrt-devel/2008-January/001618.html
also look at /etc/init.d/led it allows you to setup your leds based on
a uci file
so ideally you give your leds a default brightness / trigger in the
kernel code and then setup the others in userland via uci depending on
which works best / makes sense for the specific case
Well, none of the above ;-)
For almost all the leds there's already a suitable trigger module (be it
network activity, usb, heartbeat, etc., so it's just a matter of enabling it
like you said above, but there are some leds that I'd like to control from
a C application (specifically fxs1, fxs2 and voip),
so I'd like to know if there's an api for it, or I just open, e.g.,
/sys/class/leds/soc:green:fxs1/trigger, and fprintf default-on to turn it
on and none to turn it off (i.e., like the above shell commands but from C).
I just wanted to know if is there a more elegant way.
Note that those 3 leds are controlled by the ebu driver, and I assigned them
to the gpio_led structure, i.e.:
static struct gpio_led
arv7518pw_leds_gpio[] __initdata = {
{ .name = soc:green:power, .gpio = 2, .active_low = 1, },
{ .name = soc:green:adsl, .gpio = 4, .active_low = 1, },
{ .name = soc:green:internet, .gpio = 5, .active_low = 1, },
{ .name = soc:green:wlan, .gpio = 6, .active_low = 1, },
{ .name = soc:red:internet, .gpio = 8, .active_low = 1, },
{ .name = soc:green:usb, .gpio = 19, .active_low = 1, },
{ .name = soc:green:voip, .gpio = 32, .active_low = 1, },
{ .name = soc:green:fxs1, .gpio = 33, .active_low = 1, },
{ .name = soc:green:fxs2, .gpio = 34, .active_low = 1, },
/* no fxo on this board but the led is there, unlabeled */
{ .name = soc:red:fxo, .gpio = 35, .active_low = 1, },
{ .name = soc:yellow:wps, .gpio = 36, .active_low = 1, },
{ .name = soc:red:wps, .gpio = 38, .active_low = 1, },
};
so I'm not sure I can use the /sys/class/gpio method
(the echo xxx /sys/class/leds/yyy/trigger method works, that's how it tested
from userspace).
Bye
--
Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
Note that those 3 leds are controlled by the ebu driver, and I assigned them
to the gpio_led structure, i.e.:
static struct gpio_led
arv7518pw_leds_gpio[] __initdata = {
{ .name = soc:green:power, .gpio = 2, .active_low = 1, },
{ .name = soc:green:adsl, .gpio = 4, .active_low = 1, },
{ .name = soc:green:internet, .gpio = 5, .active_low = 1, },
{ .name = soc:green:wlan, .gpio = 6, .active_low = 1, },
{ .name = soc:red:internet, .gpio = 8, .active_low = 1, },
{ .name = soc:green:usb, .gpio = 19, .active_low = 1, },
{ .name = soc:green:voip, .gpio = 32, .active_low = 1, },
{ .name = soc:green:fxs1, .gpio = 33, .active_low = 1, },
{ .name = soc:green:fxs2, .gpio = 34, .active_low = 1, },
/* no fxo on this board but the led is there, unlabeled */
{ .name = soc:red:fxo, .gpio = 35, .active_low = 1, },
{ .name = soc:yellow:wps, .gpio = 36, .active_low = 1, },
{ .name = soc:red:wps, .gpio = 38, .active_low = 1, },
};
so I'm not sure I can use the /sys/class/gpio method
(the echo xxx /sys/class/leds/yyy/trigger method works, that's how it
tested
from userspace).
Bye
sorry, i am not aware of any clean solution fprintf() FTW!
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add libFTDI
applied in r26867, thx ! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] dnsmasq: direct address return option for uci config
On 09/04/11 07:00, Linus Lüssing wrote:
With this commit the --address option of dnsmasq, directly returning ip
addresses for certain domains instead of querying the dns server, can be
configured in the dhcp uci configuration file. See the dnsmasq manpage
for further details of this option.
Signed-off-by: Linus Lüssing linus.luess...@web.de
---
package/dnsmasq/files/dhcp.conf|1 +
package/dnsmasq/files/dnsmasq.init |5 +
2 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/package/dnsmasq/files/dhcp.conf b/package/dnsmasq/files/dhcp.conf
index 660b06a..5ba772e 100644
--- a/package/dnsmasq/files/dhcp.conf
+++ b/package/dnsmasq/files/dhcp.conf
@@ -15,6 +15,7 @@ config dnsmasq
option leasefile'/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.auto'
#list server'/mycompany.local/1.2.3.4'
+ #list address '/whatever.domain/192.168.123.45'
#option nonwildcard 1
#list interface br-lan
#list notinterface lo
diff --git a/package/dnsmasq/files/dnsmasq.init
b/package/dnsmasq/files/dnsmasq.init
index cd5a78a..8334b38 100644
--- a/package/dnsmasq/files/dnsmasq.init
+++ b/package/dnsmasq/files/dnsmasq.init
@@ -41,6 +41,10 @@ append_server() {
append args -S $1
}
+append_address() {
+ append args -A $1
+}
+
append_interface() {
local ifname=$(uci_get_state network $1 ifname $1)
append args -i $ifname
@@ -88,6 +92,7 @@ dnsmasq() {
append_parm $cfg domain -s
append_parm $cfg local -S
config_list_foreach $cfg server append_server
+ config_list_foreach $cfg address append_address
config_list_foreach $cfg interface append_interface
config_list_foreach $cfg notinterface append_notinterface
config_list_foreach $cfg addnhosts append_addnhosts
hi,
you should simply symlink /etc/resolv.conf to /tmp/resolv.conf.auto in
this case
thx,
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
I'm curious about this box, it looks very interesting as a replacement for my current ADSL modem/router which is one of the last non-Free computer I use daily. Is the ADSL modem working well under OpenWRT? And what about the FXO/FXS ports? Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
2011/5/9 John Crispin j...@phrozen.org try adding printk(foo %d\n, pin); between the // GPIOs and the if ( and see what the bootlog says ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel This is what it says: dwc_otg: version 2.60a 22-NOV-2006 foo 29 DWC_otg: Using DMA mode dwc_otg dwc_otg.0: DWC OTG Controller dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1 dwc_otg dwc_otg.0: irq 62, io mem 0xbe101000 DWC_otg: Init: Port Power? op_state=1 DWC_otg: Init: Power Port (0) hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected I also tried some other GPIOs, and none works, but I'm sure that it is 29, because I also found inside router GPL source // P1.13 GPIO29 is EN_USB_PWR on Porta-Danube and there was also something about 13 in that patch I got to power up USB on old ifxmips. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Gigaset SX763
On Sat, May 07, 2011 at 11:23:36PM +0200, Andrej Vlašić wrote:
I'm trying to set up openwrt on this router, it is based on Lantiq Xway
Danube Soc ( PSB50702 E), and manufactured by Sagem(previously by Siemens).
Wiki page is here http://wiki.openwrt.org/toh/gigaset/sx76x
I already managed to boot openwrt on it, but I cannot get USB working,
because there is no power on the port (DISCONNECTED PORT).
It was possible to get power on old ifxmips target by modifying GPIO
addresses in usb_vbus_enable function, but since that is now changed I dunno
how to make it work on a new one. ( I asked that on forums
https://forum.openwrt.org/viewtopic.php?pid=134415#p134415 )
I also looked up at those arcadyan board configs, and some of them have
_EBU addess and _USB pin defined.
I know that on this router usb power is on gpio 29( gpl source says that ),
and that irq at dwc_otg driver in original fw is 54, but I dunno which
address should go to EBU ( if any).
Also this board doesn't have wlan eeprom, instead it is read by a wlan
driver from a file inside fw. If someone has some answers on how to modify
current ath5k driver, would like to know.
I have been trying to set up JTAG on this board, but without success. I
have connected using this device:
http://www.diygadget.com/universal-jtag-adapter-for-routers-modem-fta-and-more.html
The board has standard EJTAG pinout. With urjtag I can dump only part of
flash:
==
jtag cable wiggler ppdev /dev/parport0
Initializing ppdev port /dev/parport0
jtag detect
IR length: 10
Chain length: 2
Device Id: 00011011 (0x0183)
Unknown manufacturer!
Device Id: 00011011 (0x0183)
Unknown manufacturer!
chain.c(149) Part 0 without active instruction
chain.c(200) Part 0 without active instruction
chain.c(149) Part 0 without active instruction
jtag discovery # output attached
jtag include admtek/adm5120/adm5120
jtag part 0
jtag include admtek/adm5120/adm5120
jtag instruction bypass
jtag part 1
jtag include admtek/adm5120/adm5120
jtag initbus ejtag
jtag readmem 0x5002 0x0002 0x0002.bin
==
This is the file from include (modified endian):
==
pc# cat /usr/share/urjtag/admtek/adm5120/adm5120
registerBR 1
registerBSR 1
registerDIR 32
registerEJIMPCODE 32
registerEJADDRESS 32
registerEJDATA 32
registerEJCONTROL 32
registerEJALL 96
registerEJFASTDATA 33
instruction length 5
instruction BYPASS 1 BR
instruction SAMPLE/PRELOAD 00010 BSR
instruction IDCODE 1 DIR
instruction EJTAG_IMPCODE 00011 EJIMPCODE
instruction EJTAG_ADDRESS 01000 EJADDRESS
instruction EJTAG_DATA 01001 EJDATA
instruction EJTAG_CONTROL 01010 EJCONTROL
instruction EJTAG_ALL 01011 EJALL
instruction EJTAGBOOT 01100 BR
instruction NORMALBOOT 01101 BR
instruction EJTAG_FASTDATA 01110 EJFASTDATA
initbus ejtag
endian big
==
But as you can see urjtag detects IR length: 10 and not 5 as set in
the file above. I suspect that is the reason why the output file looks
like this:
==
pc# xxd 0x0002.bin | head -n 20
000: beef 0100 0562 de5b ...b...[
010: 1e52 7ceb b8da 029d ...R..|.
020: 6d8b 88ee 6109 2d91 ..m...a...-.
030: be36 f86b 9154 cf09 ...6...k...T
040: 0cc2 422a a647 17d0 ..B*...G
050: 028f 8e11 59f6 3077 ..Y...0w
060: 458f 25e8 0999 85e9 ..E...%.
070: ee9c 7bb6 f508 44f3 ..{...D.
080: 8532 204c ab11 ...2.. L
090:
0a0:
0b0:
0c0:
0d0:
0e0:
0f0:
100: 3736 ..76
110: 6461 6265 0006 ..da..be
120: 0002 3036 ..06
130: 5f31 335f 6e74 655f .._1..3_..nt..e_
==
On the line 110 should be string danube, but it's not and every second
column is .
Anybody have suggestions how to change config file so it can dump memory
corectly?
Info here:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=339713 (comcute's post)
Re: [OpenWrt-Devel] Gigaset SX763
Al 10/05/11 00:51, En/na Luka Perkov ha escrit: The board has standard EJTAG pinout. With urjtag I can dump only part of flash: If the board uses the brn bootloader, maybe you can use my quick'n'dirty tool to dump the flash: http://code.google.com/p/brndumper/ Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
