**** BEGIN LOGGING AT Thu Nov 25 02:59:58 2010 Nov 25 03:42:15 build #33 of avr32 is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/avr32/builds/33 Nov 25 04:34:15 joh: i think the kismet/libnl-tiny issue is resolved.... https://dev.openwrt.org/ticket/8249#comment:6 Nov 25 04:54:42 build #28 of xburst is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/xburst/builds/28 Nov 25 05:00:49 jow_laptop: (oops not joh: ) i think the kismet/libnl-tiny issue is resolved.... https://dev.openwrt.org/ticket/8249#comment:6 Nov 25 05:46:04 build #33 of sibyte is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/sibyte/builds/33 Nov 25 06:37:53 build #29 of iop32x is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/iop32x/builds/29 Nov 25 07:32:28 build #29 of ifxmips is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ifxmips/builds/29 Nov 25 08:01:19 build #29 of ep93xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ep93xx/builds/29 Nov 25 09:02:03 hello Nov 25 09:33:49 sn9: pong Nov 25 10:44:03 danage: http://sourceforge.net/projects/acx100/forums/forum/257272/topic/3764011 Nov 25 10:44:44 [florian]: now, about the patch... ? Nov 25 10:45:05 sn9: what do you mean by this post Nov 25 10:45:31 <[florian]> sn9: have not had the time to review it yet Nov 25 10:45:38 danage: look at what he says at the end of the thread Nov 25 10:46:04 oliver? Nov 25 10:46:45 yes Nov 25 10:50:01 danage: he says basically that the acx drivers are useful only on the 1130 chip on ar7, not the 1350, which should use the wl12xx driver Nov 25 10:51:50 that said, there was a project to port wl12xx to pci devices: http://gitorious.org/wl12xx Nov 25 10:51:56 sorry that is techy stuff that i have no knowledge of. but as far as i know, the drivers in question only support the ACX100 and ACX111 chipsets (TWNET1100 and TWNET1130) Nov 25 10:52:13 and those, to my knowledge, use the VLYNQ bus, not PCI Nov 25 10:53:05 the acx100 and acx111 chipsets support both pci and vlynq, just on different pins Nov 25 10:53:49 <[florian]> sn9: from your patch, the reset sequence is different depending on the vlynq bus revision, is that right? Nov 25 10:54:09 [florian]: essentially yes (i speculate) Nov 25 10:54:18 <[florian]> sn9: kind of make sense Nov 25 10:55:27 sn9: the chipsets yes, but the drivers are for VLYNQ afaik Nov 25 10:56:08 the acx drivers oliver works on are for pci and vlynq Nov 25 10:58:15 assuming you can finally solve the legal issues, it seems to me acx and wl12xx can be easily merged, like at http://gitorious.org/wl12xx Nov 25 11:00:08 when oliver wrote his conclusion in that thread, i'm betting he was unaware of that effort Nov 25 11:00:24 <[florian]> sn9: sure about that? Nov 25 11:00:48 <[florian]> sn9: last I talked about that with oliver he said that he was not too sure about the number of changes required in wl12xx to work with acx devices Nov 25 11:01:16 exactly; and that's an existing effort to do exactly that Nov 25 11:02:39 <[florian]> whether it's vlynq, pci, memory-mapped does not really matter in the end Nov 25 11:02:55 <[florian]> it can be easily abstracted using low-level operations for accessing regs and doing dma Nov 25 11:03:08 <[florian]> I am more worried about the quirks that might be needed to support older devices Nov 25 11:03:13 <[florian]> and the firmware stuff Nov 25 11:03:13 based on oliver's conclusion about the 1350, i speculate that merging the drivers that way would instantly give us a working driver for it Nov 25 11:03:56 the quirks of devices that acx already supports are already known Nov 25 11:05:59 <[florian]> okay, great Nov 25 11:06:29 too bad he's not on irc Nov 25 11:06:38 <[florian]> yep Nov 25 11:09:02 i looked at http://gitorious.org/wl12xx and it seems to just replace the sdio with pci i/o, rather than create a unified driver Nov 25 11:13:21 hmm, i just reread my convo with dpm, and it seems i misunderstood him Nov 25 11:13:42 ifxmips -> http://pastebin.com/sNRkJRJM thx ngp !! Nov 25 11:14:50 dpm had said that wl12xx is based directly on acx, but now i see he was referring to the effort on gitorious Nov 25 11:21:13 blogic: are the license problems finally fixed for the dwc driver? Nov 25 11:30:25 KanjiMonster: no idea Nov 25 11:32:23 sn9: olivers drivers are on sourceforge now (acx ones) Nov 25 11:32:47 and afaik, the acx-mac80211 stuff he's working on don't have the same legal issues as the original acx ones. Nov 25 11:32:48 EqUaTe: and? Nov 25 11:32:55 just saying ;) Nov 25 11:33:10 acx-mac80211 is the driver with the legal issues Nov 25 11:33:21 they're rather a lot more up to date than the acx ones on gitorious Nov 25 11:33:34 hm.. i'm pretty certain from a lot of reading that it was acx that had the legal issues Nov 25 11:33:37 blogic: iirc the dwc core is also used on octeon, and they were trying to get the code licensed under a GPL compatible license (the gwc one isn't quite) to get it included in mainline, I remember having read the discussion somewhere Nov 25 11:34:56 EqUaTe: what do the old acx drivers on gitorious have to do with anything? the wl12xx driver on gitorious is unrelated Nov 25 11:38:32 KanjiMonster: yes, that is the case Nov 25 11:40:49 [10:48:20] the acx drivers oliver works on are for pci and vlynq Nov 25 11:40:49 [10:50:27] assuming you can finally solve the legal issues, it seems to me acx and wl12xx can be easily merged, like at http://gitorious.org/wl12xx Nov 25 11:40:49 [10:52:20] when oliver wrote his conclusion in that thread, i'm betting he was unaware of that effort Nov 25 11:41:37 i presume you're referring to oliver winker, and the ones he's working on are the acx-mac80211 ones hosted at sourceforge. Nov 25 11:41:47 previously on gitorious Nov 25 11:42:09 EqUaTe: by "acx" i was referring to acx-mac80211 on SF Nov 25 11:42:31 right. what legal issues are you referring to for those then? Nov 25 11:43:03 acx-mac80211 directly uses the tainted code verbatim Nov 25 11:43:29 hrm. ok. Nov 25 11:44:53 dpm said wl12xx does also, but he was referring to the wl12xx on gitorious and not the wl12xx in the mainline kernel, unaware that they are unrelated Nov 25 11:51:47 fair enough. Nov 25 11:56:23 danage: anything happening on the legal end? Nov 25 12:05:31 florian * r24137 /trunk/package/acx-mac80211/ (Makefile patches/001-wlan_cipher_suite.patch): [ar7] update acx-mac80211 to 20101030 snapshot, patch from sn9 Nov 25 12:05:35 florian * r24138 /trunk/target/linux/ar7/patches-2.6.32/110-flash.patch: [ar7] increase flash window size to 32MiB, patch from sn9. Nov 25 12:05:40 florian * r24139 /trunk/target/linux/ar7/patches-2.6.32/160-vlynq_try_remote_first.patch: [ar7] handle new revisions of vlynq wrt reset sequence, patch from sn9 Nov 25 12:05:47 florian * r24140 /trunk/target/linux/ar7/patches-2.6.32/ (4 files): [ar7] handle mvswitch in cpmac, rework MII probing logic, patch from sn9 and Wipster Nov 25 12:17:04 [florian]: two goofups Nov 25 12:17:33 1) 973-cpmac_handle_mvswitch.c ends in .c instead of .patch Nov 25 12:17:51 2) you left out 972-cpmac_multi_probe.patch Nov 25 12:18:17 <[florian]> sn9: ah, sorry about that, yes, I got trapped by diffstat Nov 25 12:19:57 <[florian]> sn9: are you sure baout 972-cpmac_multi_probe.patch ? Nov 25 12:20:22 in what way? Nov 25 12:20:40 <[florian]> I cannot see if in the svn Nov 25 12:20:52 because you left it out Nov 25 12:21:12 <[florian]> ok got it Nov 25 12:26:20 florian * r24141 /trunk/target/linux/ar7/patches-2.6.32/ (973-cpmac_handle_mvswitch.c 973-cpmac_handle_mvswitch.patch): [ar7] rename 973-cpmac_handle_mvswitch.c to 973-cpmac_handle_mvswitch.patch Nov 25 12:26:24 florian * r24142 /trunk/target/linux/ar7/patches-2.6.32/972-cpmac_multi_probe.patch: [ar7] patch 972-cpmac_multi_probe.patch correctly, thanks sn9 Nov 25 12:26:30 <[florian]> should be much better now Nov 25 12:40:48 hi i have a c program here which uses syslog.h and syslog calls for status messages, where can i see them in openwrt ? Nov 25 12:40:55 logread doesnt show them :( Nov 25 12:41:53 oh sorry ... investigating further .. it shows them :/ Nov 25 12:45:46 phiamo_: and kernel messages are also in dmesg Nov 25 12:45:56 you can test the log manually using logger in the shell Nov 25 12:46:00 logger hello world Nov 25 12:46:10 logger "hello world" Nov 25 13:59:47 blogic: you got mail Nov 25 14:02:15 k Nov 25 14:59:25 hauke * r24143 /trunk/package/mac80211/patches/002-disable_rfkill.patch: Nov 25 14:59:25 mac80211: cfg80211 should not depend on rfkill. Nov 25 14:59:25 If rfkill is build as an module CONFIG_RFKILL_MODULE is set and cfg80211 will also depend on that. Nov 25 14:59:25 Now all modules build from compat-wireless will not use rfkill. Nov 25 15:24:26 build #30 of kirkwood is complete: Failure [failed compile_12] Build details are at http://tksite.gotdns.org:8010/builders/kirkwood/builds/30 Nov 25 15:58:56 build #30 of ixp4xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ixp4xx/builds/30 Nov 25 17:11:19 jow * r24144 /packages/multimedia/ushare/patches/200-compile-fixes.patch: [packages] ushare: fix compilation against libupnp v1.6.8 Nov 25 18:07:08 build #33 of ar71xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ar71xx/builds/33 Nov 25 18:10:22 jow * r24145 /trunk/package/opkg/patches/001-ship-pkg-m4.patch: [package] opkg: ship pkg.m4, this fixes building on FreeBSD Nov 25 18:25:34 build #30 of adm5120 is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/adm5120/builds/30 Nov 25 19:04:11 acoul * r24146 /trunk/tools/pkg-config/Makefile: tools/pkg-config: update to version 0.25 Nov 25 19:58:11 build #29 of au1000 is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/au1000/builds/29 Nov 25 20:30:33 build #29 of rdc is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/rdc/builds/29 Nov 25 20:38:40 build #29 of octeon is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/octeon/builds/29 Nov 25 21:22:05 build #34 of ubicom32 is complete: Failure [failed compile_4] Build details are at http://tksite.gotdns.org:8010/builders/ubicom32/builds/34 Nov 25 22:58:18 hmmm... slow day. who is 'ngp'? Nov 26 01:11:32 build #29 of mpc52xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/mpc52xx/builds/29 **** ENDING LOGGING AT Fri Nov 26 02:59:58 2010