[OpenWrt-Devel] toolchain's gdb add-symbol-file doesn't honor file address
The line number is correct, but the start/end addresses ignore the file address. $ ./staging_dir/toolchain-mips_r2_gcc-4.3.3+cs_uClibc-0.9.31/bin/mips-openwrt-linux-gdb GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as --host=i686-redhat-linux --target=mips-openwrt-linux-uclibc. (gdb) add-symbol-file bin/ar71xx/debug/modules/ath9k.ko 0x8300 add symbol table from file bin/ar71xx/debug/modules/ath9k.ko at .text_addr = 0x8300 (y or n) y Reading symbols from /home/brown/wifi/dev/openwrt/trunk-wndr-svn/bin/ar71xx/debug/modules/ath9k.ko...done. (gdb) info line ath_beacon_config Line 709 of /home/brown/wifi/dev/openwrt/trunk-wndr-svn/build_dir/linux-ar71xx_generic/compat-wireless-2011-01-24/drivers/net/wireless/ath/ath9k/beacon.c starts at address 0xcfc ath_beacon_config and ends at 0xd20 ath_beacon_config+36. (gdb) quit A gdb run on the mips target also has this same problem. The x86 gdb doesn't have this problem with x86 modules. Any idea what's wrong? Steve ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] default stack size limit is too big
Hi! I have a device with only 16MB of memory and I want to run threaded applications on it. The size of allocated stack space in uClibc's implementation of pthread_create equals to the stack size limit as returned by ulimit -s (or the default for the current architecture if the limit is set to 'unlimited' which is 2MB for MIPS). The problem is that the limit on my 16MB box is somehow set to 8MB for all processes which is a half of available RAM so the allocation fails. If I enable aggressive overcommit (echo 1 /proc/sys/vm/overcommit_memory) or lower the limit (ulimit -s 2048 or ulimit -s unlimited) then everything works like a charm. Where is the 8MB stack size limit set? BTW I use openwrt trunk, uClibc 0.9.32 with nptl, everything else is default. -- Alexander signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] default stack size limit is too big
On 2011-01-28 1:28 PM, Alexander Gordeev wrote: Hi! I have a device with only 16MB of memory and I want to run threaded applications on it. The size of allocated stack space in uClibc's implementation of pthread_create equals to the stack size limit as returned by ulimit -s (or the default for the current architecture if the limit is set to 'unlimited' which is 2MB for MIPS). The problem is that the limit on my 16MB box is somehow set to 8MB for all processes which is a half of available RAM so the allocation fails. If I enable aggressive overcommit (echo 1 /proc/sys/vm/overcommit_memory) or lower the limit (ulimit -s 2048 or ulimit -s unlimited) then everything works like a charm. Where is the 8MB stack size limit set? BTW I use openwrt trunk, uClibc 0.9.32 with nptl, everything else is default. Please try copying this patch to toolchain/uClibc/patches-0.9.32 - http://nbd.name/190-nptl_use_arch_default_stack_limit.patch and see if rebuilding uclibc with it fixes the problem. The issue that I found is that if getrlimit returns a valid value for the stack limit, it will be used as a default even if the architecture specific default is lower. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] cron: Add path
On 2011-01-27 3:22 AM, kentarou matsuyama wrote: Override PATH for /etc/init.d/cron. This is necessary to ensure all programs can be found when executing the script from remote by using ssh. (e.g. ssh IP /etc/init.d/cron restart) Applied in r25196, thanks. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211.sh setting ESSID in station mode
in station/client mode we forgot to set the ESSID, so there was no connection possible. this is just a proposal - i'am unsure if there is a better place for the command. Signed-off-by: Bastian Bittorf bitt...@bluebottle.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211.sh setting ESSID in station mode
in station/client mode we forgot to set the ESSID,
so there was no connection possible. this is just
a proposal - i'am unsure if there is a better place
for the command.
Signed-off-by: Bastian Bittorf bitt...@bluebottle.com
From 831ce3fda06bbccc0a2be09b783a4a2e2db41b69 Mon Sep 17 00:00:00 2001
From: Bastian Bittorf bitt...@bluebottle.com
Date: Fri, 28 Jan 2011 13:56:59 +0100
Subject: [PATCH] setting ESSID in client/station-mode, after the interface is up
---
package/mac80211/files/lib/wifi/mac80211.sh |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/package/mac80211/files/lib/wifi/mac80211.sh b/package/mac80211/files/lib/wifi/mac80211.sh
index ac1562f..61032eb 100644
--- a/package/mac80211/files/lib/wifi/mac80211.sh
+++ b/package/mac80211/files/lib/wifi/mac80211.sh
@@ -439,6 +439,8 @@ enable_mac80211() {
continue
}
fi
+
+ iw dev $ifname connect $ssid
;;
esac
mac80211_start_vif $vif $ifname
--
1.6.3.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mac80211.sh setting ESSID in station mode
On 2011-01-28 1:57 PM, Bastian Bittorf wrote: in station/client mode we forgot to set the ESSID, so there was no connection possible. this is just a proposal - i'am unsure if there is a better place for the command. Signed-off-by: Bastian Bittorf bitt...@bluebottle.com No, we didn't forget to set the ESSID, it was intentionally left out. mac80211 will not reconnect or roam on its own after connection loss, which makes supporting client mode without wpa_supplicant a pointless exercise. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] 802.1q range on Broadcom based WRTs
Hi, I hope that someone here on the list knows enough about the Broadcom WRT hardware used in the Linksys E3000 to help me answer something that googling didn't get me anywhere. I have a setup where I need to have 802.1q tagged frames come out of this E3000, and the site network admin has assigned vlan IDs 920, 930, and 940. All the documentation I can find always talks about vlans 1..15, and vlan 3 always maps to 802.1q vlan ID 3 (if tagged on an external port). So - can someone point me to the actual hardware capabilities of the switch chip built into these boxes? Is it 15 parallel VLANs, no matter which VIDs or 802.1q VLAN IDs up to 15 (read: no way to use 920)? gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgp7r5YBUXyiQ.pgp Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uhttpd / bug when decoding URL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I will add a substitution to replace + with , to maintain compatibility with BusyBox httpd. ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1DCVcACgkQdputYINPTPP2eQCeJ8sym1DbC6T6SuBue8+ztuY5 d6cAn3nN2xvKF3A80ioreNpkR4s15w2s =7YRS -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Clean way of adding custom scripts and firstrun
@ Ithamar Thank you. That is well understood. However, when you write a script to automate a router configuration that should be working cross platform, then you cannot preconfigure the wireless configuration with a static file. First you cannot make assumptions about the hardware present, it could be anything, so you have to allow the system to go through the process of discovery it goes through, when first writing the /etc/config/wireless file. You would also loose router specific configuration, as for the nanostation, or for the various profiles for the ar71xx chipset. You actually want to take up what was preconfigured there, and add, but not remove as you would loose the benefit of the device specific configuration. Consequently a process running after /etc/config/network boot is what is required. @ Jo-Philip The process triggered in /etc/init.d/boot is a great pointer. Thank You. I am toying with the thought of adding a boot command in one of my own start-up scripts, like /etc/init.d/xyz boot Could I just confirm when the init scripts triggered by boot are running: Does the system first run through all boot commands and then through all start commands or does the system run through all scripts in the order given in /etc/rc.d running the boot command first and then the start command for each init script in turn? Please advise. Thank You -Original Message- From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Ithamar R. Adema Sent: Saturday, 29 January 2011 1:47 a.m. To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] Clean way of adding custom scripts and firstrun On Fri, 2011-01-28 at 11:28 +1300, Hanno Schupp wrote: I am asking as some configuration like network and wireless may be set by the system on boot, so if one would like to add to the /etc/config/wireless configuration (i.e. by setting the power to max possible or, setting diversity etc.) then this is not possible, as the /etc/config/wireless file does not exist before /etc/init.d scripts are fired. So this means one would be looking for a first-boot-script facility that is triggered after /etc/init.d is all completed. Does this facility exist? For the example of the wireless configuration file, it will not be generated if it already exists. So if you need to preconfigure it, you could write it out in the uci-defaults script and have the network init.d script pick the generated configuration up and use it. HTH, Ithamar. ___ 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] Supporting platform-in-a-box
2011/1/28 Philip Prindeville philipp_s...@redfish-solutions.com: and I was wondering... would it be useful to have a directory called bouquets (sorry, that's a hang-over from working with Dreambox and other FTA satellite STB's) that contain useful configuration bundles where someone can just do: The scripts/env should be suitable: http://wiki.openwrt.org/doc/devel/env ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Supporting platform-in-a-box
On 1/28/11 1:44 PM, Claudio wrote: 2011/1/28 Philip Prindevillephilipp_s...@redfish-solutions.com: and I was wondering... would it be useful to have a directory called bouquets (sorry, that's a hang-over from working with Dreambox and other FTA satellite STB's) that contain useful configuration bundles where someone can just do: The scripts/env should be suitable: http://wiki.openwrt.org/doc/devel/env Ok, but currently there are no provisions for sharing configurations between users. So the infrastructure is there, but we don't leverage to the full extent we could. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Attempt to build r25222 fails
Just working through the latest updates, and when I build, I get the following error: configure: creating ./config.status config.status: error: cannot find input file: `Makefile.in' make[3]: *** [/home/jhenderson/Downloads/openwrt/build_dir/host/ opkg-576/.configured] Error 1 make[3]: Leaving directory `/home/jhenderson/Downloads/openwrt/package/ opkg' make[2]: *** [package/opkg/host/compile] Error 2 make[2]: Leaving directory `/home/jhenderson/Downloads/openwrt' make[1]: *** [/home/jhenderson/Downloads/openwrt/staging_dir/target- mips_r2_uClibc-0.9.30.1/stamp/.package_compile] Error 2 make[1]: Leaving directory `/home/jhenderson/Downloads/openwrt' make: *** [world] Error 2 This happens at this stage: make[3] -C package/opkg host-compile (errors shown using V=99 as suggested in the output) I tried doing both a: make package/opkg/clean And doing a make clean before doing a build. I'd rather not do a distclean if I can avoid it since I have to then re-configure the additional packages (is there an easy way to back that up? - talking about the scripts/feeds installed packages) I also tried nuking everything under the build_dir and that didn't help either. Thanks, Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Resend: [PATCH 1/1] Build breaks if libusb-1.0 selected
There seems to be a dependency between libusb-1.0 and opkg. libusb-1.0 will only build if opkg has already been built. Index: tools/Makefile === --- tools/Makefile (revision 25095) +++ tools/Makefile (working copy) @@ -57,6 +57,7 @@ $(curdir)/missing-macros/compile := $(curdir)/automake/install $(curdir)/e2fsprogs/compile := $(curdir)/automake/install $(curdir)/libelf/compile := $(curdir)/automake/install +$(curdir)/libusb-1.0/compile := $(curdir)/opkg/install $(curdir)/builddirs := $(tools-y) $(tools-dep) $(tools-) $(curdir)/builddirs-default := $(tools-y) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attempt to build r25222 fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, see https://dev.openwrt.org/ticket/8418#comment:1 . ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1DY8sACgkQdputYINPTPNjKwCfTnDooYpeZPe1Qeoefk6bot4T lkAAni2X7kgew9mLDR6lhgLLV8ZQOjKA =GB9o -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attempt to build r25222 fails
On Sat, 29 Jan 2011 01:48:11 +0100, Jo-Philipp Wich wrote: see https://dev.openwrt.org/ticket/8418#comment:1 . Thanks, Jow - next time I'll remember to do this. Do I need to do anything to preserve the packages that I've installed, or will the fact that they're configured take care of that for me? Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Supporting platform-in-a-box
On 2011-01-28 9:27 PM, Philip Prindeville wrote: I have the following ~/.openwrt/defconfig contents: CONFIG_PACKAGE_usbutils=y CONFIG_PACKAGE_libusb-1.0=y CONFIG_PACKAGE_pciutils=y CONFIG_PACKAGE_ip=y CONFIG_PACKAGE_iftop=y CONFIG_PACKAGE_coreutils-uptime=y CONFIG_PACKAGE_coreutils-users=y CONFIG_PACKAGE_coreutils-who=y CONFIG_PACKAGE_fdisk=y CONFIG_PACKAGE_kmod-wprobe=y CONFIG_PACKAGE_wprobe-util=y CONFIG_PACKAGE_libnl=y CONFIG_PACKAGE_libnl-tiny=y CONFIG_PACKAGE_p910nd=y CONFIG_TARGET_x86_geos=y CONFIG_TARGET_x86=y and I was wondering... would it be useful to have a directory called bouquets (sorry, that's a hang-over from working with Dreambox and other FTA satellite STB's) that contain useful configuration bundles where someone can just do: cp bouquets/some-platform ~/.openwrt/defconfig rm .config .config.old make defconfig You don't need to mess with ~/.openwrt/defconfig at all to apply a partial config, simply throw the partial config into .config directly and run make defconfig. and be good to go? This would give a platform-in-a-box capability... well, possibly also adding a files/ tarball that goes with it. We could write a simple script... #!/bin/bash platform=$1 [ -z $platform ] echo need a platform name 12 exit 1 mkdir -p $HOME/.openwrt cp -p bouquets/$platform.cfg $HOME/.openwrt/defconfig rm -rf .config .config.old files/ if [ -f bouquets/$platform.tgz ]; then mkdir files tar -C files -zxf bouquets/$platform.tgz fi make defconfigdefconfig.log I just added a script that makes it much easier to maintain defconfig files for different preselections. Make a config (leave it in .config), then run ./scripts/diffconfig.sh and take a look at its output. It generates a very minimal list of config changes that are (or at least should be) enough to regenerate the full .config, but is easy to review at the same time. Maybe I'll use this to make ./scripts/env store reduced config files by default. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Supporting platform-in-a-box
On 2011-01-29 3:39 AM, Felix Fietkau wrote: On 2011-01-28 9:27 PM, Philip Prindeville wrote: I have the following ~/.openwrt/defconfig contents: CONFIG_PACKAGE_usbutils=y CONFIG_PACKAGE_libusb-1.0=y CONFIG_PACKAGE_pciutils=y CONFIG_PACKAGE_ip=y CONFIG_PACKAGE_iftop=y CONFIG_PACKAGE_coreutils-uptime=y CONFIG_PACKAGE_coreutils-users=y CONFIG_PACKAGE_coreutils-who=y CONFIG_PACKAGE_fdisk=y CONFIG_PACKAGE_kmod-wprobe=y CONFIG_PACKAGE_wprobe-util=y CONFIG_PACKAGE_libnl=y CONFIG_PACKAGE_libnl-tiny=y CONFIG_PACKAGE_p910nd=y CONFIG_TARGET_x86_geos=y CONFIG_TARGET_x86=y and I was wondering... would it be useful to have a directory called bouquets (sorry, that's a hang-over from working with Dreambox and other FTA satellite STB's) that contain useful configuration bundles where someone can just do: cp bouquets/some-platform ~/.openwrt/defconfig rm .config .config.old make defconfig You don't need to mess with ~/.openwrt/defconfig at all to apply a partial config, simply throw the partial config into .config directly and run make defconfig. and be good to go? This would give a platform-in-a-box capability... well, possibly also adding a files/ tarball that goes with it. We could write a simple script... #!/bin/bash platform=$1 [ -z $platform ] echo need a platform name 12 exit 1 mkdir -p $HOME/.openwrt cp -p bouquets/$platform.cfg $HOME/.openwrt/defconfig rm -rf .config .config.old files/ if [ -f bouquets/$platform.tgz ]; then mkdir files tar -C files -zxf bouquets/$platform.tgz fi make defconfigdefconfig.log I just added a script that makes it much easier to maintain defconfig files for different preselections. Make a config (leave it in .config), then run ./scripts/diffconfig.sh and take a look at its output. It generates a very minimal list of config changes that are (or at least should be) enough to regenerate the full .config, but is easy to review at the same time. Maybe I'll use this to make ./scripts/env store reduced config files by default. Oh, one more thing that I forgot, you may need to run make -C scripts/config clean before running this script. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] TP-Link TL-WA901ND V2 support
OK, so, I was finally able to compile forcedeth support into the kernel. It seems that the kernel compile process prompts whether to actually compile that in. Without running V=99, I had no way of telling it to actually include forcedeth support. That said, I still have no ethernet support. Strangely enough, absolutely no pci devices show up in /proc/bus/pci/devices. The file is altogether empty. A couple questions: First, should I continue to document my efforts here, or create a thread in the forums? Second, when I dumped the flash, I did a 'dd if=/dev/mtd[#] of=/tmp/901V2dump[#].bin' Should I have dd'ed from mtdblock instead? The stock boot log is now up here: http://oneru.dyndns.org/openwrt/WA901NDv2/901V2BootLog.txt I do see one item that sticks out. There is a '/lib/modules/2.6.15/net/ag7100_mod.ko' in the stock firmware. Could it be a proprietary driver? I'd try to investigate it further, but I can't think of a way to transfer the file off the router. Cheers, Jonathan Bennett ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Supporting platform-in-a-box
On 1/28/11 7:42 PM, Felix Fietkau wrote: On 2011-01-29 3:39 AM, Felix Fietkau wrote: On 2011-01-28 9:27 PM, Philip Prindeville wrote: I have the following ~/.openwrt/defconfig contents: CONFIG_PACKAGE_usbutils=y CONFIG_PACKAGE_libusb-1.0=y CONFIG_PACKAGE_pciutils=y CONFIG_PACKAGE_ip=y CONFIG_PACKAGE_iftop=y CONFIG_PACKAGE_coreutils-uptime=y CONFIG_PACKAGE_coreutils-users=y CONFIG_PACKAGE_coreutils-who=y CONFIG_PACKAGE_fdisk=y CONFIG_PACKAGE_kmod-wprobe=y CONFIG_PACKAGE_wprobe-util=y CONFIG_PACKAGE_libnl=y CONFIG_PACKAGE_libnl-tiny=y CONFIG_PACKAGE_p910nd=y CONFIG_TARGET_x86_geos=y CONFIG_TARGET_x86=y and I was wondering... would it be useful to have a directory called bouquets (sorry, that's a hang-over from working with Dreambox and other FTA satellite STB's) that contain useful configuration bundles where someone can just do: cp bouquets/some-platform ~/.openwrt/defconfig rm .config .config.old make defconfig You don't need to mess with ~/.openwrt/defconfig at all to apply a partial config, simply throw the partial config into .config directly and run make defconfig. and be good to go? This would give a platform-in-a-box capability... well, possibly also adding a files/ tarball that goes with it. We could write a simple script... #!/bin/bash platform=$1 [ -z $platform ] echo need a platform name 12 exit 1 mkdir -p $HOME/.openwrt cp -p bouquets/$platform.cfg $HOME/.openwrt/defconfig rm -rf .config .config.old files/ if [ -f bouquets/$platform.tgz ]; then mkdir files tar -C files -zxf bouquets/$platform.tgz fi make defconfigdefconfig.log I just added a script that makes it much easier to maintain defconfig files for different preselections. Make a config (leave it in .config), then run ./scripts/diffconfig.sh and take a look at its output. It generates a very minimal list of config changes that are (or at least should be) enough to regenerate the full .config, but is easy to review at the same time. Maybe I'll use this to make ./scripts/env store reduced config files by default. Oh, one more thing that I forgot, you may need to run make -C scripts/config clean before running this script. - Felix I'm not finding scripts/diffconfig.sh ... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
