**** BEGIN LOGGING AT Thu Mar 31 02:59:58 2016
**** BEGIN LOGGING AT Thu Mar 31 03:29:41 2016
Mar 31 04:28:53 <builder_> build #255 of lantiq is complete: Failure [failed shell_18]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/255
Mar 31 05:40:39 <builder_> build #190 of ep93xx is complete: Failure [failed shell_13]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/190
Mar 31 07:09:03 <builder_> build #211 of xburst is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/211
Mar 31 10:16:46 <aep> any ideas where i can post a berlin based openwrt dev job?
Mar 31 10:16:59 <aep> _post_ not find
Mar 31 10:21:46 <Kaloz> probably on the lists
Mar 31 10:23:05 <Kaloz> depending on what job you want to offer, it can be -hackers, -devel or even -users
Mar 31 11:18:12 <builder_> build #218 of x86 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/218
Mar 31 12:48:27 <jakllsch> is there a reason i can't use channel 165 in the USA with ath5k in CC?
Mar 31 12:48:36 <jakllsch> iwinfo sasy it's restricted
Mar 31 12:48:54 <jakllsch> but it used to work in some older releases
Mar 31 12:49:01 <jakllsch> did the regulations change, or is this a bug?
Mar 31 12:49:19 <jakllsch> hmm, this is -devel
Mar 31 13:29:02 <plntyk> jakllsch:  hm... that might look like a bug
Mar 31 13:30:05 <jakllsch> (it's a wgt634u with a non-original dual band ath5k card)
Mar 31 13:31:26 <plntyk> looking at http://git.openwrt.org/?p=15.05/openwrt.git;a=blob;f=package/kernel/mac80211/files/regdb.txt;h=463ace3a380fa5e95fb907bef263a2dbbb9de9b0;hb=HEAD and it seems normal and should allow that channel compared w. channellist at wikipedia
Mar 31 13:32:29 <builder_> build #257 of ramips is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/257
Mar 31 13:32:35 <plntyk> older 14.07 did have that line/frequency too
Mar 31 13:32:59 <jakllsch> yeh, the dmesg regdom info looks decent
Mar 31 13:33:56 <plntyk> and "iw reg get" is normal and set to US too
Mar 31 13:33:58 <plntyk> ?
Mar 31 13:34:17 <jakllsch> or maybe that's what i was loking at
Mar 31 13:34:26 <jakllsch> (5735 - 5835 @ 80), (N/A, 30), (N/A)
Mar 31 13:34:38 <jakllsch> country US: DFS-FCC
Mar 31 13:35:31 <jakllsch> [   31.840000] ath: EEPROM regdomain: 0x66
Mar 31 13:35:36 <jakllsch> [   31.840000] ath: Country alpha2 being used: 00
Mar 31 15:38:18 <jakllsch> plntyk: hmm, i disabled DFS and it seems to be available now
Mar 31 15:38:22 <jakllsch> (at build time)
Mar 31 15:39:45 <plntyk> hm.... does some bug require DFS ? iirc ath5k does not have DFS support in driver but i am not sure
Mar 31 15:40:36 <plntyk> https://wireless.wiki.kernel.org/en/users/drivers/ath5k its in TODO there
Mar 31 15:42:09 <plntyk> but the regdb does not state DFS on the channels involved so they should be available
Mar 31 17:38:32 <builder_> build #218 of x86.kvm_guest is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/x86.kvm_guest/builds/218
Mar 31 19:54:35 <builder_> build #215 of ar7 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/215
Mar 31 20:41:44 <builder_> build #233 of brcm2708 is complete: Failure [failed shell_17 shell_18]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/233
Mar 31 20:43:57 <builder_> build #234 of x86.xen_domu is complete: Failure [failed shell_17]  Build details are at http://buildbot.openwrt.org:8010/builders/x86.xen_domu/builds/234
**** ENDING LOGGING AT Fri Apr 01 02:59:58 2016