**** BEGIN LOGGING AT Mon May 02 02:59:57 2011
May 02 03:21:13 <builder_> build #20 of kirkwood is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/20
May 02 03:31:58 <builder_> build #16 of octeon is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/16
May 02 03:51:31 <builder_> build #23 of ps3 is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/ps3/builds/23
May 02 03:52:23 <builder_> build #26 of brcm63xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/26
May 02 04:21:35 <builder_> build #23 of pxcab is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/23
May 02 06:32:30 <builder_> build #26 of s3c24xx is complete: Failure [failed compile_10]  Build details are at http://buildbot.openwrt.org:8010/builders/s3c24xx/builds/26
May 02 06:43:20 <builder_> build #21 of ar71xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/21
May 02 07:58:31 <CIA-83> florian * r26803 /trunk/target/linux/ (9 files in 4 dirs): [uml] update to 2.6.38
May 02 09:31:53 <builder_> build #25 of brcm47xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/25
May 02 12:37:13 <builder_> build #23 of orion is complete: Failure [failed compile_7]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/23
May 02 12:42:51 <lightb> Anybody have any experience with the Atheros AP83 reference board?
May 02 12:54:37 <CIA-83> jow * r26804 /trunk/tools/quilt/patches/100-patch_2.6.1_version.patch:
May 02 12:54:37 <CIA-83> [PATCH] quilt: fix building with dash
May 02 12:54:37 <CIA-83> `test x == x` gives a syntax error with dash (standard in Debian).
May 02 12:54:37 <CIA-83> The modified patch reflects the current upstream:
May 02 12:54:37 <CIA-83> http://git.savannah.gnu.org/cgit/quilt.git/commit/?id=38df0b210c3df67f3e784af92232ae1946b98ecd
May 02 12:55:35 <CIA-83> jow * r26805 /trunk/package/firewall/files/ (firewall.config lib/core_interface.sh):
May 02 12:55:35 <CIA-83> [PATCH] firewall: provide examples of ssh port relocation on firewall and IPsec passthrough
May 02 12:55:35 <CIA-83> Two examples of potentially useful configurations (commented out, of course):
May 02 12:55:35 <CIA-83> (a) map the ssh service running on the firewall to 22001 externally, without modifying the configuration of the daemon itself. this allows port 22 on the WAN side to then be port-forwarded to a
May 02 12:55:36 <CIA-83> LAN-based machine if desired, or if not, simply obscures the port from external attack.
May 02 12:55:36 <CIA-83> (b) allow IPsec/ESP and ISAKMP (UDP-based key exchange) to happen by default. useful for most modern VPN clients you might have on your WAN.
May 02 12:55:36 <CIA-83> Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
May 02 12:56:37 <CIA-83> jow * r26806 /trunk/package/firewall/files/lib/core_interface.sh: [package] firewall: revert accidential committed changes from r26805
May 02 13:40:35 <builder_> build #23 of lantiq is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/23
May 02 14:09:12 <builder_> build #17 of ep93xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/17
May 02 15:59:50 <builder_> build #23 of ramips is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/23
May 02 16:38:39 <will__> jow_laptop, xMff, u around?
May 02 16:39:08 <jow_laptop> yes, but only for a few minutes
May 02 16:39:14 <will__> kk
May 02 16:39:20 <will__> im making a patch
May 02 16:39:32 <will__> where does quilt store the patches/?/?
May 02 16:39:45 <jow_laptop> patches/ ?
May 02 16:39:56 <will__> my 'new' patch
May 02 16:40:02 <jow_laptop> too?
May 02 16:40:18 <jow_laptop> you need to "refresh" at least once
May 02 16:40:26 <will__> i did :/
May 02 16:40:32 <will__> says my patch is on top
May 02 16:40:41 <jow_laptop> so you find it in patches/
May 02 16:41:10 <jow_laptop> or in patches/generic/ or patches/platform/ for the kernel
May 02 16:41:46 <will__> target/linux/ar7/patches-2.6.37  >?
May 02 16:42:01 <will__> should be in there yeah?
May 02 16:42:15 <jow_laptop> no in build_dir/linux-*/linux-2.6.*/patches/*/
May 02 16:42:22 <will__> oooo
May 02 16:42:25 <will__> ty :)
May 02 16:42:39 <jow_laptop> it ends up in target/linux/... only after you ran "make target/linux/update"
May 02 16:42:49 <jow_laptop> which copies the patches from builddir back into the buildroot
May 02 16:43:40 <jow_laptop> when doing kernel patches, make always sure you respect the subdirectory, e.g. quilt new platform/999-foo.patch or quilt new generic/999-foo.patch
May 02 16:43:54 <jow_laptop> if you miss the subdir the patch will get lost on make target/linux/update
May 02 16:44:32 <will__> ahh ty ty
May 02 16:44:32 <jow_laptop> bbl
May 02 16:44:57 <will__> my  patch ended up in that patches folder cause my mistake
May 02 16:45:02 <will__> jow_laptop, ty ttyl
May 02 18:17:47 <builder_> build #23 of ppc44x is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/23
May 02 18:58:47 <stintel> hmmm seems there are quite some changes to target/linux/x86/config-default when running make kernel_menuconfig and then just saving
May 02 18:58:54 <stintel> should they be added in svn ?
May 02 19:00:41 <stintel> http://paste.pocoo.org/show/381699/
May 02 19:06:38 <stintel> or maybe some of them should rather go in target/linux/generic/config-2.6.37 ?
May 02 19:29:02 <markmentovai> xMff: wondering if you've come to any conclusions on that "ieee80211d" configuration parameter thing from last week.
May 02 19:47:58 <markvvv> hello, i'd like to compile kernel 2.6.38 for kirkwood. I changed the LINUX_VERSION in target/linux/kirkwood/Makefile. However I encounter errors when kernel sources are patched, even if patch is not specific for kirkwood
May 02 19:51:00 <markvvv> ok..i edited linux-kirkwood/linux-2.6.38/patches/series removing the diff files that were failing
May 02 20:07:13 <xMff> markmentovai: I hoped for a comment from nbd but I suppose we can commit it as is
May 02 20:07:59 <markmentovai> i suppose if he doesn't here the banter here, he'll never hear us
May 02 20:08:08 <nbd> i'll look into it
May 02 20:08:12 <markmentovai> there we go
May 02 20:10:56 <xMff> markmentovai: personally I'd give it an ack after you streamlined the code
May 02 20:11:02 <xMff> s/after/now that/
May 02 20:12:45 <builder_> build #24 of atheros is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/24
May 02 20:13:06 <markmentovai> xMff: ok. let's see what nbd says.
May 02 20:13:12 <markmentovai> (or does.)
May 02 20:13:16 <nbd> i guess that would work, though it emits the option once per vif even though internally it's a global setting
May 02 20:13:19 <nbd> afaik
May 02 20:14:00 <markmentovai> is it? it's per-beacon frame, so it *could* be a per-vif setting, even if hostapd doesn't currently treat it that way
May 02 20:14:34 <xMff> hm not sure
May 02 20:14:41 <markmentovai> looking
May 02 20:14:52 <xMff> seems to be global (within hostapd) atm
May 02 20:15:02 <markmentovai> yeah, it is, it's on conf and not bss
May 02 20:19:27 <markmentovai> the existing ieee80211d param is defined on the vif
May 02 20:19:34 <markmentovai> are there other backends that allow it to be per-vif?
May 02 20:20:12 <xMff> no
May 02 20:21:10 <markmentovai> i suppose it could be moved to the device, then. but then if hostapd (or whatever else) ever grew support to have a different 11d setting per beacon on multiple vifs, it'd have to move back
May 02 20:22:48 <xMff> hmm
May 02 20:23:05 <xMff> broadcom has such a settings as well, per-device
May 02 20:23:15 <xMff> though it is hardcoded to off there
May 02 22:41:59 <builder_> build #24 of x86 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/24
May 02 23:08:05 <russell--> how do i most easily prevent wifi from getting enabled at boot, but rather bring up wifi w/ hostapd manually?
May 02 23:08:25 * russell-- trying to gather information on a kernel pani
May 02 23:08:26 <russell--> c
May 02 23:10:59 <xMff> chmod -x /sbin/wifi
May 02 23:11:07 <xMff> sh /sbin/wifi up
May 02 23:11:32 <xMff> or save the generated hostapd.conf away
May 02 23:11:44 <xMff> and do hostapd -ddd /etc/hostapd.conf
May 02 23:11:52 <xMff> it should do anything by itself
May 02 23:13:03 <russell--> nice, thaks
May 02 23:20:19 <russell--> hmm. "Configuration file: /var/run/hostapd-phy0.conf
May 02 23:20:21 <russell--> Line 2: invalid/unknown driver 'nl80211'"
May 02 23:22:19 <xMff> miscompiled hostapd
May 02 23:24:39 <russell--> hmm. could be, i menuconfig'd from madwifi to ath5k
May 02 23:57:40 <russell--> /etc/config/wireless seems to get stomped on/removed on every boot, but restorable from /rom
May 03 00:02:14 <philipp64|laptop> xMff: so how did the firewall patch look?
May 03 00:03:53 <philipp64|laptop> oh, never mind... just saw the merge log.  Thanks!
May 03 00:12:20 <russell--> panics with just adhoc mode, hostapd not needed
May 03 00:31:59 <will> jow_laptop,
May 03 00:52:06 <builder_> build #22 of ar7 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/22
May 03 01:54:16 <builder_> build #22 of sibyte is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/22
May 03 02:05:15 <builder_> build #23 of uml is complete: Failure [failed compile_10]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/23
May 03 02:22:14 <russell--> when i configure to build a cross-gdb, where does it land?  /me is searching so far without success
**** ENDING LOGGING AT Tue May 03 02:59:58 2011