**** BEGIN LOGGING AT Wed Jul 09 02:59:58 2014 Jul 09 03:22:15 build #114 of pxa is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/114 Jul 09 04:25:18 build #112 of omap is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/112 Jul 09 04:44:32 build #619 of ppc44x is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/619 Jul 09 04:56:37 build #3 of x86.xen_domu is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.xen_domu/builds/3 Jul 09 05:00:30 build #24 of brcm47xx.legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/24 Jul 09 05:02:42 build #588 of sibyte is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/588 Jul 09 05:19:25 build #599 of avr32 is complete: Failure [failed compile_3] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/599 Jul 09 05:54:12 build #630 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/630 Jul 09 07:19:08 build #666 of atheros is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/666 Jul 09 07:41:50 build #9 of ar71xx.nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.nand/builds/9 Jul 09 07:48:48 build #696 of brcm63xx is complete: Failure [failed shell compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/696 Jul 09 07:50:04 build #526 of iop32x is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/526 **** BEGIN LOGGING AT Wed Jul 09 08:42:18 2014 Jul 09 09:13:27 build #554 of au1000 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/554 Jul 09 09:26:01 according to the wireless wiki: http://wireless.kernel.org/en/users/Documentation/hostapd hostapd should need 2 interfaces: master and monitor Jul 09 09:26:21 but using OpenWrt and ath9k, having AP running, i can see one interface only Jul 09 09:26:55 there is only "wlan0", why is that? Jul 09 09:28:36 afair the master mode interface was hidden from userspace long ago Jul 09 09:28:41 sometime around 2.6.24 or so Jul 09 09:29:07 there used to be a "wmaster0" pseudo interface in the early mac80211 days, but that was eventually not exposed by the kernel anymore Jul 09 09:33:26 so does hostapd use wlan0 to sending/receiving management frames? Jul 09 09:33:36 and system users wlan0 for sending standard traffic? Jul 09 09:34:06 *system uses Jul 09 09:36:39 if wlan0 is now a standard inteface, how hostapd can listen for management frames on it? :| Jul 09 09:39:25 mgmt frames are sent/received through nl80211 Jul 09 09:39:31 not wlan0 Jul 09 09:39:37 ahh Jul 09 09:45:09 thanks, just found it :) http://w1.fi/cgit/hostap/tree/src/drivers/driver_nl80211.c#n3996 Jul 09 09:45:25 "If poll command and tx status are supported, mac80211 is new enough to have everything we need to not need monitor interfaces." Jul 09 10:14:08 nbd r41554 trunk/target/linux/generic/patches-3.10/140-revert_usb_unbind_interfaces.patch Jul 09 10:14:08 kernel: revert an upstream linux-stable commit that is causing usb regressions on some brcm47xx and ar71xx devices Jul 09 13:50:29 jow_laptop: nbd: it seems that brcmfmac doesn't set probe_client: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c#n4271 Jul 09 13:50:48 jow_laptop: nbd: so hostapd's poll_command_supported will be 0: http://w1.fi/cgit/hostap/tree/src/drivers/driver_nl80211.c#n3557 Jul 09 13:51:31 and I believe that will make hostapd use extra interface in monitor mode: drv->use_monitor = !info.poll_command_supported || !info.data_tx_status; Jul 09 13:51:33 is that right/ Jul 09 13:51:38 do I understand it correctly? Jul 09 14:17:01 zajec: could be, not sure Jul 09 14:17:36 are there any openwrt devices that could potentially make use of brcmfmac? Jul 09 14:17:40 i'm not aware of any Jul 09 14:20:24 not likely Jul 09 14:20:36 i'm just trying to understand how things works in AP mode :) Jul 09 14:24:22 nbd: *maybe* BCM43236B Jul 09 14:24:33 maybe it's that magic rev 3 chipset Jul 09 14:24:41 (the only rev supported by brcmfmac) Jul 09 14:24:44 https://wikidevi.com/wiki/Netgear_WNDR3400v3 Jul 09 14:36:06 nbd ? Jul 09 14:36:16 has the regdb been changed lately ? Jul 09 14:38:49 nighty^: this is a question you can answer yourself (assuming you know where to look) ;) -> http://git.openwrt.org/?p=openwrt.git;a=history;f=package/kernel/mac80211/files/regdb.txt;h=3d1593014aa62caa23114b71c1cd3fa11497103c;hb=HEAD Jul 09 14:53:59 meh... I didn't know that there's -devel channel :( Jul 09 14:54:39 maybe anyone here, besides Mr. KanjiMonster, develop custom kernel drivers/modules? Jul 09 15:00:17 scrts_w: do you need some real help? or Eclipse setup help? Jul 09 15:00:31 scrts_w: not sure, but someone was asking about Eclipse setup recently :| Jul 09 15:03:30 too bad, anyway, I am not into eclipse, I am more like how can I set up all the include paths correctly. The IDE doesn't matter actually Jul 09 15:03:50 well, you don't Jul 09 15:03:55 Linux's Makefile does that for you Jul 09 15:04:07 so you don't have to care about that Jul 09 15:04:16 ok, so I still need to write my own Makefile then? Jul 09 15:04:31 moo Jul 09 15:04:40 or it's a matter of putting my source file to a correct location and modify the existing Makefile? Jul 09 15:05:05 scrts_w: really, why don't you use Google? e.g.: http://www.tldp.org/LDP/lkmpg/2.6/html/x181.html Jul 09 15:05:38 there is 3-line example Makefile Jul 09 15:05:39 just use it Jul 09 15:06:00 you can change "/lib/modules/$(shell uname -r)/build" to another kernel dir location Jul 09 15:06:25 but I suggest you to compile module for your host machine first Jul 09 15:06:33 then start playing with OpenWrt once you got sth Jul 09 15:07:16 there is another (a bit longer) article: https://www.kernel.org/doc/Documentation/kbuild/modules.txt Jul 09 15:07:34 yep, but then how can I put it into the main OpenWRT build workflow? My main idea is to have my driver in the menuconfig, I simply select it, save the .config, run make, it builds the whole system, generates the image and I can find my driver in the image written to the system Jul 09 15:08:01 just like all the regular drivers from there Jul 09 15:08:30 scrts_w: http://wiki.openwrt.org/doc/devel/packages Jul 09 15:08:49 scrts_w: http://wiki.openwrt.org/doc/devel/packages#creating.packages.for.kernel.modules Jul 09 15:09:37 oook, so it's a package Jul 09 15:09:40 scrts_w: you also need to decide if your driver should be an in-kernel driver (i.e. requires some stuff built into the kernel, and potentially future submission to linux), or if you are fine with it as an external module package Jul 09 15:09:41 many thanks for the hint! Jul 09 15:10:29 KanjiMonster: I will start with the module at the moment as this would allow me to rebuild the module only and try to load it in the system without the whole system recompilation Jul 09 15:10:56 see package/kernel/gpio-button-hotplug for a an example of a rather simple out of kernel driver Jul 09 15:11:08 -a Jul 09 15:11:16 thanks Jul 09 15:12:51 does someone want to explain to me how the prodc/nand upgrade thing is supposed to work? Jul 09 15:13:16 I see it calls ubus, and then there's some mechanism that's supposed to take over at that point. But "nothing happens" for me Jul 09 15:23:48 scrts_w: i sent u e-mai Jul 09 15:24:11 scrts_w: u just need to fill helloworld.c with a code for kernel module Jul 09 15:24:35 scrts_w: so put some Jul 09 15:24:37 module_init(luxulctf_init) Jul 09 15:24:38 module_exit(luxulctf_exit); Jul 09 15:24:40 in it Jul 09 15:24:50 have to go Jul 09 15:24:51 good luck Jul 09 15:29:15 scrts_w: do you use Linux? Jul 09 15:29:21 scrts_w: as your host machine? Jul 09 15:29:30 scrts_w: did you already compile some kernel module on it? Jul 09 15:29:38 scrts_w: that may really help to start with that :) Jul 09 15:29:51 scrts_w: but with the bash commands i sent yo Jul 09 15:29:55 it should be easy anyway Jul 09 15:30:22 scrts_w: it's usually just much faster to compile something for your host machine Jul 09 15:30:28 and give it some quick testing Jul 09 15:33:36 zajec: I run XUbuntu on my home machine Jul 09 15:34:17 thanks for the email! Jul 09 16:30:25 build #208 of mvebu is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/208 Jul 09 16:51:27 build #115 of adm8668 is complete: Failure [failed shell compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/115 Jul 09 17:05:59 build #225 of imx6 is complete: Failure [failed shell shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/225 Jul 09 17:46:56 build #514 of mcs814x is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/514 Jul 09 17:51:57 build #624 of x86 is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/624 Jul 09 21:35:53 build #568 of ar71xx is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/568 Jul 10 00:16:33 build #660 of cobalt is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/660 Jul 10 02:29:16 build #666 of orion is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/666 **** ENDING LOGGING AT Thu Jul 10 02:59:58 2014