**** BEGIN LOGGING AT Thu Feb 12 02:59:58 2009 Feb 12 03:00:49 I think MateIn4 put a mask in there... for the phys so it would not probe non existant phys Feb 12 03:01:40 yup... line 140 of the patch Feb 12 03:03:21 for example... here in the patch... Feb 12 03:03:21 .phy_mask = 0x0F0000, Feb 12 03:03:21 .rxq = 4, Feb 12 03:03:21 .txreadyq = 21, Feb 12 03:04:22 what are .rxq and .txreadyq ? Irqs? Feb 12 03:05:12 but nonexistant phys on one board... may not be the same on other revs... mebe Feb 12 03:05:36 could be. check the header file to find what rxq/txreadyq means Feb 12 03:06:01 set phy_mask to 0x0 to not-mask-anything Feb 12 03:06:17 that sounds like a plan Feb 12 03:06:28 or 0xffffff, try both Feb 12 03:06:38 anyway Feb 12 03:10:25 otoh... does the phymask apply to both NPE-B and C? It is only in one... but yet both aren't working... Feb 12 03:12:25 i would assume it should apply to both, note some ixp42x, e.g. pronghorn metro, only uses NPE-B(or C, can't remember), maybe the old code is used where one phy mask is needed Feb 12 03:12:49 the usr8250's code is actually based off pronghorn metro code Feb 12 03:13:18 that's all i know...hope i can affort a usr8250 to play with :) Feb 12 03:13:32 $350, wow Feb 12 03:14:23 anyone here ever worked on Dlink 2590? Feb 12 03:14:34 an MIMO AP with cavium chips Feb 12 03:18:30 on ebay they range from 45 ~ 100 Feb 12 03:20:57 http://home.comcast.net/~johnrw/ has my early pictures... (big!) and http://wiki.openwrt.org/OpenWrtDocs/Hardware/USRobotics/USR8200 has the openwrt info... Feb 12 03:22:07 you can see very clearly the BB etched on the end of the model on the cpu here http://home.comcast.net/~johnrw/image/M5110025.JPG Feb 12 03:22:39 350... was so that nobody would buy the unit... Feb 12 03:23:40 i would focus on the MII/PHY code to make sure it's detected Feb 12 03:24:18 once it was determined that the relationship between Jungo and US Robotics was a no go...(they never hired Jungo again) well that is a bad situation isn't it...? Feb 12 03:26:12 The last firmware delivered by Jungo has some real "Gotcha's"... like for example... any drive attached... well once it goes to sleep... the kernel writes a log message about "corrupt superblock" Feb 12 03:27:25 I personally think it was probably an intentional... bug... kinda like giving US Robotics the middle finger... Feb 12 03:28:08 It was not there in some of the earlier firmware released... like the 2.x versions that came with my BB routers. Feb 12 03:28:56 the mii/phy code is above my paygrade... Feb 12 03:29:40 but I think I'll put the old firmware back in... and see what /proc says... Feb 12 03:32:25 I finally finished my last purchase to make a complete Zephyrtronics workstation... with the purchase of a pcb rack today http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270340079120 Feb 12 03:33:31 funny my top bid was 105... and it was barely just enough... Feb 12 07:05:04 noz: Would would supporting YABD (Yet another Broadcom device) such as the Asus WL-330gE entail? Adding its LEDs and marking it with some identifier in package/broadcom-diag? Supporting its ethernet port in target/linux/{brcm-2.4,brcm47xx}/base-files/etc/init.d/netconfig? Anything else other than testing, testing, testing? Feb 12 07:05:55 kupesoft: typically that's all that is needed Feb 12 07:06:58 I'm worried I'll be locked out of the device when I flash, since its ethernet configuration is presumably just one logical device Feb 12 07:06:59 newer netgear boards do stupid stuff with the flash layout but I haven't seen that on any asus or linksys boards Feb 12 07:08:27 I'll build my image to disable the firewall, I guess Feb 12 07:10:39 Today let it be known that I coined the acronym YABD -- yet another broadcom device. Feb 12 07:11:20 ^^ (c) with CC attribution license Feb 12 07:12:20 kupesoft: what's the bootloader? Feb 12 07:12:30 RoundSparrow: CPE says the firmware bundle Feb 12 07:12:37 kupesoft: any way to ramdisk boot? Feb 12 07:12:49 No idea Feb 12 07:12:59 that's the safest way to make sure devices work... and/or find a way to flash from bootloader if you end up with unusable devices Feb 12 07:13:17 I know nothing of CPE, I only know redboot and u-boot right now Feb 12 07:14:31 RoundSparrow: er, CFE Feb 12 07:14:52 CFE, CFE, CFE Feb 12 07:17:55 RoundSparrow: I'm assuming it has a bootloader failsafe mode like the WL-500gP, but I'm going to test how recoverable it is with the stock images first Feb 12 08:08:17 juhosg * r14482 /trunk/target/linux/ar71xx/files/arch/mips/ar71xx/prom.c: Feb 12 08:08:17 [ar71xx] parse the board parameter from the command line first Feb 12 08:08:17 Signed-off-by: Andrea Tassi and WiFi(ed) - The Feb 12 08:08:17 Embedded Development Team (of Riccardo Coppola , Feb 12 08:08:20 Andrea Tassi and Massimiliano Toce Feb 12 08:08:22 ) Feb 12 08:10:58 PACKAGE_kmod-ath9k isnt available at my build root for x86 any suggestion? Feb 12 08:11:49 juhosg ! Feb 12 08:13:55 Bartman007 points out to me two things I overlooked. 1) that the Netgear WNR2000 AP81 has source code for u-boot! And.... 2) it has the same ar8216 LAN switch as the Planex! http://agb.openwrt.org/wnr2000/uboot.5fbb2cd3b1b11352dfb73f0b8326c323662182a8.diff Feb 12 10:09:45 florian * r14483 /packages/net/aircrack-ng/ (Makefile patches/): [package] update aircrack-ng to r1396, patch from David Cooper (#4180)x Feb 12 11:43:48 juhosg * r14484 /trunk/target/linux/generic-2.6/patches-2.6.28/ (920-00-spi-gpio.patch 920-spi-gpio.patch): [kernel] generic-2.6/2.6.28: rename spi-gpio patch Feb 12 12:48:21 lars * r14485 /feeds/desktop/libs/libstartup-notification/ (. Makefile): Add libstartup-notification pcakage. Feb 12 13:26:15 aroscha_: ping Feb 12 13:48:04 blogic, time today to poke around the danube? Feb 12 13:49:12 maligor: not today Feb 12 14:07:05 juhosg * r14486 /trunk/target/linux/ar71xx/ (2 files in 2 dirs): [ar71xx] pull ethernet mac out of reset before registering the mdio_bus Feb 12 14:12:03 juhosg: you see msg earlier about WNR2000 u-boot? Feb 12 14:21:00 RoundSparrow: yes Feb 12 14:31:10 juhosg: so does this cover the technical needs for the LAN driver, or should I keep looking/digging? Feb 12 14:31:23 (switch driver) Feb 12 14:38:52 blogic: hi ping Feb 12 14:50:59 RoundSparrow: well, i have this code already, all boards use this or very similar code in their driver Feb 12 15:05:35 juhosg: are you aware of any active PoE board? looks like adiengineering, routerboard,gateworks(?) are all doing passive PoE these days? Feb 12 15:05:59 juhosg: the reason i'm asking, is that i need a solution to remotely restart the board if it hangs Feb 12 15:06:31 juhosg: an external watchdog with gpio ping could do similar things, but i doubt any AP has it Feb 12 15:06:42 s/ping/pin/ Feb 12 15:10:55 juhosg * r14487 /trunk/target/linux/ar71xx/patches-2.6.28/802-ag71xx_mdio_dynamic_mdio_bus.patch: [ar71xx] fix a typo in the dynamic mdio patch Feb 12 15:11:38 xxiao: i don't know about such boards Feb 12 15:14:36 xxiao: the SoC on your board has no built-in hardware watchdog? Feb 12 15:15:24 juhosg: that's for the worst scenario, i.e. the SoC itself hangs. out in the field really only external watchdog can do the restarting job Feb 12 15:15:36 juhosg: avoid truck rolls, you know it's costly here in us Feb 12 15:23:12 xxiao: something similar to this: http://www.wline.info/buxus/generate_page.php?page_id=1766&productID=3240 ? Feb 12 15:24:01 looks like gateworks's board has external watchdog timer on board Feb 12 15:24:53 juhosg: yeah..good finding Feb 12 15:29:11 juhosg: i used iperf to measure ag71xx on SR71 and it can only reach 28mbps, is this normal? my other pc on the same LAN can easily reach to 94mbpc Feb 12 15:33:19 xxiao: i assume something is wrong with the ubnt boards, the driver can do ~95 Mbps on the others Feb 12 15:53:19 xxiao: btw, i have found the possible reason why the ag71xx driver did not find any phy chip Feb 12 15:53:29 xxiao: can you try out the phy stuff on the SR71 again Feb 12 16:23:14 juhosg: sorry, was on a phone. yes let me know how to try it out Feb 12 16:33:50 the fix is in trunk already, you should run 'svn update' or you simply modify the 'ag71xx_mdio.c' in you build dir according to this: Feb 12 16:33:53 https://dev.openwrt.org/changeset/14486/trunk/target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx_mdio.c Feb 12 16:37:11 use ag71xx_add_device_mdio(0), and ag71xx_eth0_data.phy_mask=0x1 in the board setup code Feb 12 16:37:23 and enable debug mode in the ag71xx driver Feb 12 16:38:00 xxiao: ^^ Feb 12 16:38:45 juhosg: yes i'm wol my home machine to do the compilation and tests :) Feb 12 16:38:57 need about 10 minutes to get results Feb 12 16:39:45 ok, thanks Feb 12 16:49:09 still compiling...if this works that all mach-rb4xx.c's hard-coded speed/duplex can be changed, i hope Feb 12 16:49:18 s/that/then/ Feb 12 16:49:40 i can test 411 as i have one board Feb 12 16:53:36 the rb-433/450/493 require the fixed settings, because the mac is connected to a switch Feb 12 16:56:42 i c Feb 12 16:58:40 juhosg: http://www.mibbit.com/pb/lcflat not working :( Feb 12 17:03:30 seems to be you did not modify the ag71xx_mdio.c: Feb 12 17:03:34 eth0: mac_cfg1=80000005, mac_cfg2=00007115, ipg=40605060, hdx=00a1f037, mfl=00000600 Feb 12 17:03:39 the mac_cfg1 ^^^^^^^^^^ should be 00000000 Feb 12 17:05:48 or if you did a svn update, you may forgot to run 'make target/linux/clean' Feb 12 17:07:04 juhosg: yes that's what happened :( Feb 12 17:07:08 a few more minutes Feb 12 17:07:26 ok, np Feb 12 17:14:50 juhosg: http://www.mibbit.com/pb/pXB2Ln Feb 12 17:15:43 ok, we are close Feb 12 17:15:46 mii_read: addr=0001, reg=0002, value=0022 Feb 12 17:15:50 mii_read: addr=0001, reg=0003, value=1619 Feb 12 17:16:28 the phy_mask must be 0x2 Feb 12 17:17:05 juhosg: building now Feb 12 17:24:23 juhosg: looks working http://pastebin.com/m3a984c6d Feb 12 17:24:59 :) Feb 12 17:28:45 \o/ Feb 12 17:32:17 xxiao: thank you for testing, although i don't know it will be working or not on the original LSX, but i will commit it Feb 12 17:34:56 How can I generate a core dump using OpenWRT? Feb 12 17:39:57 juhosg: thanks a lot! can you also add the basic LSX hacking so that I do not need patch the trunk? Feb 12 17:41:10 juhosg: as LSX is replaced by SR71, actually LSX was not really a product anymore, does it make sense to change LSX to SR71 naming? Feb 12 17:41:52 the difference so far I found on LSX and SR71 is that the size of flash is 4M vs. 8M, SR71 has 8M Feb 12 18:03:43 xxiao: yes, we can change the name to LS-SR71, because we know that this works, and the LSX may have other differences Feb 12 18:03:50 http://www.ubnt.com/products/lsx.php says that the LSX is based on the ar7131 Feb 12 18:04:13 the board on this page has two eth connectors: http://www.streakwave.com/Itemdesc.asp?ic=LSX&eq=&Tp= Feb 12 18:12:45 juhosg: Sr71 is also 7131 but with 680Mhz cpu Feb 12 18:12:52 http://www.ubnt.com/products/lssr71.php Feb 12 18:14:35 juhosg: Sr71 only has one ethernet, with larger flash Feb 12 18:14:42 xxiao: Atheros AR7161 rev 2 (id:0xaa), CPU:680.000 MHz, AHB:85.000 MHz, DDR:170.000 MHz Feb 12 18:14:59 juhosg: i read somewhere in ubnt's forum, it says LSX is replaced by SR71 before it goes to the public market Feb 12 18:16:57 juhosg: i think you're right, we should trust whatever openwrt reports other than ubiquits's marketing page on their site :) Feb 12 18:17:16 juhosg: so just add a SR71 to mach-ubnt.c? Feb 12 18:18:54 xxiao: yup Feb 12 18:19:02 xxiao: and in fact the ar7131 does not support 680MHz Feb 12 18:20:21 juhosg: guess the 6 means 6xxmhz, 3 means 3xx mhz then Feb 12 18:21:46 I suggest adding firmware assembly for Netgear WN802Tv2 firmware since it seems spelled out here: http://blog.chinaunix.net/u2/83623/showart_1353786.html Looking at the firmware downloads on Netgear site, they provide a tar you upload that has kernel, jffs2 and checksums - and it assembles them after upload. AP81 is right in firmware filenames. Interestingly, the files exceed 5MB, so flash must be 8MB. Feb 12 18:22:01 xxiao: probably, because there is an ar7141 which supports 400MHz Feb 12 18:26:31 juhosg: do you need me to submit a more official patch(to support SR71, with board name LS-SR71) or you can just do it? http://www.mibbit.com/pb/A6JxXO Feb 12 18:31:24 RoundSparrow: i would not like to add this yet, i assume the u-boot on the WN802T also verify the checksum Feb 12 18:31:53 xxiao: i can do it Feb 12 18:33:22 juhosg: thanks! no need to patch trunk then :) Feb 12 18:35:24 juhosg: ok, but I am determined to focus some hack of u-boot ;) Feb 12 18:35:38 juhosg: regarding TP-Link, is this of any use? http://linux.chinaunix.net/bbs/redirect.php?fid=46&tid=892003&goto=nextnewset Feb 12 18:37:04 I notice it is talking about u-boot on ar9130 and comment of "Clearing CP0 registers - WAR for the Linux hang issue" sparked my interest Feb 12 18:37:23 I assume WAR = "Work ARound" Feb 12 18:37:58 RoundSparrow: can you read chinese? Feb 12 18:38:11 No ;) Feb 12 18:38:55 Bu it is 2009 and TP-Link is the largest sellers of routers in China, and they talk about u-boot and hanging Linux workaround Feb 12 18:39:35 anybody read chinese? Feb 12 18:41:31 RoundSparrow: actually i can :) Feb 12 18:41:41 RoundSparrow: let me know if you need translation Feb 12 18:41:46 oh, well, what is the thread about ? Feb 12 18:43:34 http://linux.chinaunix.net/bbs/redirect.php?fid=46&tid=892003&goto=nextnewset Feb 12 18:44:12 is talking about how to add a gpio-interrupt-routine to u-boot, and the guy did not know how to get it working, and i know u-boot does not really care about any interrupts Feb 12 18:45:18 he posted here on bottom of thread too: http://www.cublog.cn/u/26710/showart_402757.html "U-Boot Practically Porting Guide" Feb 12 18:46:59 2008-01-17 : Maybe this guy was Atheros contractor for the u-boot of the AP81 ;) Feb 12 18:47:22 wb51job@163.com Feb 12 18:50:20 RoundSparrow: i don't feel that, he is a junior hacker writing down studying notes on u-boot for some arm boards Feb 12 18:50:51 I figured a long shot, but hoping someone in china hacking on the TP-Link Feb 12 18:52:20 RoundSparrow: i would bet you will brick your WNR2000 sooner or later ;) Feb 12 18:52:46 oh, I've done it several times Feb 12 18:52:55 tftprecovery works well ;) Feb 12 18:53:07 but yha, touching u-boot without jtag... Feb 12 18:53:14 yup Feb 12 18:53:31 on the wnr2000 should not be too difficult to ftpboot and test a new u-boot Feb 12 18:54:07 RoundSparrow: so...i'm a bit confused, what are you trying to do with those tp-link routers? first why TP-Link Feb 12 18:54:25 RoundSparrow: with this method, you can't test the ram initialization for example Feb 12 18:55:42 yes, is discussed here: http://linux.omap.com/pipermail/davinci-linux-open-source/2007-February/002467.html "Loading u-boot from u-boot" Feb 12 18:58:58 and you can't be sure that the RAM initialization will be working if you flash it Feb 12 18:59:06 Is there a gdb command to generate a core dump from a running (hung) process ? Feb 12 19:00:21 Kaloz: ping, is there some reason why an xscale ixp4xx cpu would fail to init an A0 stepping's NPE devices... did Intel swap them around or something between rev A0 and B0? the usr8200 port was developed on B0 stepped chips... but both NPE's fail on AO. Feb 12 19:00:33 xxiao: as TP-Link has 3x3 MIMO, potential for USB, and good worldwide distribution. The Planex is nicer, but I think they will not discount it. They are coming out with TL-WR1043ND :, Atheros, 3T3R, Built-in Vitesse 4-port Gigabit Switch, USB 2.0 network storage with 3 detachable antennas. Some references to 64MB of RAM. Feb 12 19:00:45 RoundSparrow: imho, the best choice would to remove the md5sum check from the original u-boot binary, and then flash it back Feb 12 19:01:02 juhosg: yep, just binary edit it? Feb 12 19:01:09 exactly Feb 12 19:01:16 I have seen this done for other u-boot, when people upgrade RAM and such Feb 12 19:03:26 juhosg: what if the flash failed, a dead u-boot will require jtag Feb 12 19:04:02 RoundSparrow: i see, do you have a link for TL-WR1043ND Feb 12 19:04:03 xxiao: ultimate goal I see is to attract new emerging AP81/AP83 vendors (and ar71xx in general) to choose OpenWRT as the basis for their firmware. ideal outcome is better ath9k driver or even one of them making the minor changes to the madwifi ath_ahb to forward-port it to 2.6.28 or newer kernel (which even in binary-only form would open up to current OpenWRT or other Linux router projects). Netgear choose on their t Feb 12 19:05:07 Atheros LSDK based on 2.6.15 must be obsoleted soon ;) I do not want to see routers coming out with 3 year old Linux on them. We will just be stock forever like the broadcom 2.4 kernel issues Feb 12 19:05:55 RoundSparrow: madwifi is dead. any version that supports 11n is from the interal atheros code and doesn't have much relevance to the open madwifi codebase. Feb 12 19:06:21 I agree, but saying that is one sided. ath9k is a drunken 12 year old. Feb 12 19:06:28 Bartman007: does atheros still maintain wifi drivers on their own? Feb 12 19:06:39 It would be nice to have source of madwifi for ar9102/ar9103 and compile it for 2.6.28 Feb 12 19:06:47 Bartman007: is the opensource ath5k/ath9k the only choice for customers? Feb 12 19:06:49 xxiao: yes, if you are lucky and the board has JTAG header Feb 12 19:07:47 juhosg: better somebody did that and document it, so the rest of us don't kill the router Feb 12 19:07:49 xxiao: all commercial offerings use madwifi, atheros does maintain their own trees. ath[59]k isn't stable/performant enough for production yet. Feb 12 19:08:48 Bartman007: i'm just beginning to test ath9k on LS SR71 board, was told it's not that good yet Feb 12 19:09:27 i guess there is no 802.11n code in madwifi, it's only a bug-fix-feature-frozen open source project now, right? Feb 12 19:10:08 ath5k for 5xxx and ath9k for 9xxx are the future, correct? Feb 12 19:10:17 madwifi can do 802.11n Feb 12 19:10:29 there are atheros cards that use madwifi, in fact pretty much all of them Feb 12 19:10:33 (802.11n) Feb 12 19:11:08 RoundSparrow: thanks. guess i should give madwifi a shot then, is it in openwrt trunk for selection? i guess the big difference is that madwifi is maintained out of the kernel.org Feb 12 19:11:22 madwifi is the old man who is scarred from many divorces, wars, and attacks ;) But it has a lot of accumulated knowledge. Feb 12 19:12:31 xxiao: additionally you have to find a suitable JTAG software, which supports the SPI flash chips and the ar71xx/913x SoCs Feb 12 19:12:43 xxiao: and i can't explain to everyone that this process has too many risks Feb 12 19:13:22 JTAG and madwifi ? Or we talking u-boot again? Feb 12 19:13:40 RoundSparrow: ok i'm building madwifi into the image, see if it works with 9160 on 802.11n mode Feb 12 19:13:57 what is brand/model of chip? Feb 12 19:14:01 RoundSparrow: i guess it makes sense to compare these two, i really don't know how 9160 is supported under madwifi though Feb 12 19:14:12 RoundSparrow: it's the SR71A card from ubnt Feb 12 19:14:51 juhosg: agree. we're talking about TP-Link's u-boot right? or somebody else's? Feb 12 19:15:49 " Ubiquiti Radio Driver is built upon the original MADWIFI Linux Driver authored by Sam Lefler" Feb 12 19:16:56 RoundSparrow: so the reason to abandon madwifi: it's out side of kernel.org, and it's ieee80211 instead of mac80211, also it has a binary HAL, that's all? Feb 12 19:17:26 xxiao: madwifi isn't the promised land. But specific to the AP81, it is what Atheros ships a binary-only madwifi driver for 2.6.15 that I would love to have compiled for 2.6.28 (probably needs updates of course to deal with kernel changes in locking and such) Feb 12 19:17:42 xxiao: all linux wireless is in turmoil ;) Feb 12 19:19:19 Intel drivers on Linux don't work nearly as well as Linux, they have AP mode on Windows but on Linux basic stability issues abound; Athreos of all kinds don't work as well as WIndows or OS X; ralink - on Windows they have a driver for AP on all cients, I kid you not. On Linux, they have two forked drivers - one for client one for AP. Feb 12 19:19:21 ath9k, mac80211, light in the tunnel :) Feb 12 19:19:41 ath5k too, they are talking on the old chips in the rewrite Feb 12 19:19:51 and a bunch of their USB too Feb 12 19:20:25 broadcom is with b43, ralink is kind of spinning. Intel is keeping at it, obviously the laptops are huge issue for them Feb 12 19:21:14 but if you are working on b43, ath5k, ath9k - you are helping the future of Linux in a big way. Even just testing and quality bug reporting. Feb 12 19:22:30 juhosg: on your station mode testing on ap81, did you always see the 1Mb/0Mb rate issue? Feb 12 19:23:26 I was retesting last night against a WRT54GL and it starts at 24Mbps on driver load but very quickly goes to 1Mbps. Stable, pings not lost, but erratic response times. Feb 12 19:26:18 xxiao: we are talking about TP-Link's and Netgear's u-boot Feb 12 19:29:40 RoundSparrow: i have checked it only in G mode, and i did not see this yet Feb 12 19:31:12 RoundSparrow: thanks for those info Feb 12 19:42:35 juhosg: how exactly did you set G vs N mode? Feb 12 19:43:39 I mean when you set station mode, I don't even know how you pick G vs N... I only know how to tell hostapd with it's config file Feb 12 19:48:32 juhosg * r14488 /trunk/target/linux/ar71xx/ (4 files in 3 dirs): [ar71xx] add preliminary support for the Ubiquiti LS-SR71 board (thanks to Xianghua Xiao for the initial patch, and for testing) Feb 12 19:48:51 xxiao: ^ Feb 12 19:51:59 juhosg: thanks for get it there, no need to patch trunk that is great! Feb 12 19:52:57 RoundSparrow: simply i have tested it with an AP which support G mode only Feb 12 19:54:48 xxiao: np, the board value must be 'UBNT-LSSR71' in RedBoot Feb 12 19:57:07 yes...noticed that :0 Feb 12 20:08:25 juhosg: with a Trendnet running Trendnet firmware, WRT54G, and a netgear WNDR3300 running stock firmware I always get 1Mb/s in station mode as reported by iwconfig wlan0 Feb 12 20:09:33 another user on forum first brought that to my attention, wonder how you are getting station at 54 Feb 12 20:38:54 http://ubnt.com/forum/viewtopic.php?p=25762#25762 Feb 12 20:39:36 the guy at ubnt said AR9160 is not supported under madwif, so my only option is ath9k, hope to get 802.11n running Feb 12 20:47:11 xxiao: this mail says that is supported by ath9k: https://lists.ath9k.org/pipermail/ath9k-devel/2009-February/001161.html Feb 12 20:53:44 juhosg: great link! thanks. finding ath9k-debug option now Feb 12 20:56:28 xxiao: the debug option is enabled by default on ath9k now Feb 12 20:56:35 ubnt is chasing routerboard/mikrotik, selling hardware with their own os(airos), guess it's too "hard" to make money out of "hard"ware Feb 12 20:57:06 juhosg: good to know, i failed to find it on menuconfig/kernel_menuconfig and am thinking about hacking the code :) Feb 12 20:57:47 :) Feb 12 20:58:37 https://dev.openwrt.org/browser/trunk/package/mac80211/patches/402-ath9k-enable-debug.patch Feb 12 20:58:40 ubnt "We are not working on, nor will support a Linux driver directly. The Ath9k team is working on the open source community driver at this time and all support will be handled through them. " Feb 12 21:05:10 lars * r14489 /feeds/desktop/libs/libgamin/ (. Makefile patches/ patches/configure.patch): Add libgamin package. Feb 12 23:52:07 mirko * r14490 /packages/Xorg/lib/gtk1/Makefile: add missing dependency libnotimpl to package gtk1 Feb 13 00:12:31 florian * r14491 /trunk/package/mac80211/Makefile: [package] make b43/b43legacy selectable again (#4596) Feb 13 00:13:40 florian * r14492 /trunk/target/linux/brcm63xx/Makefile: [brcm63xx] always select kmod-ssb, pci is supported Feb 13 01:35:39 I just bought a WL-330gE, Feb 13 01:35:46 It's really small, sleek, a pretty an awesome device Feb 13 01:35:54 s/an// Feb 13 01:36:20 I'm looking mess of the Asus code, and it's heavily based on the WL-520gU Feb 13 01:36:27 noz: ping! Feb 13 01:36:29 submit patches, or a device and I'll commit them :) Feb 13 01:36:45 Bartman007: Uh, I'm not as savvy as all that, Feb 13 01:36:49 kupesoft: makes sense everyone is moving to bcm5354 for their low-cost devices Feb 13 01:37:14 I was hoping for helping probing the GPIO crap for what are the LEDs and reset switch Feb 13 01:37:14 it's the cpu, switch, usb and wifi in one chip Feb 13 01:37:31 Okay, dinner, then we play Feb 13 01:37:48 grab the gpio stuff from mbm.openwrt.org Feb 13 01:38:14 allows you to twiddle each gpio until you see something happening. Feb 13 01:38:40 I saw that Feb 13 01:39:01 It seems to have the good bootloader failsafe that my WL-500gP has Feb 13 01:39:26 So just a few lines in kmod-diag and setup in netconfig, that's it? Feb 13 01:39:30 seems to easy Feb 13 01:39:36 (I haven't flashed yet, though...) Feb 13 01:39:50 *too Feb 13 01:40:10 oh, I flash first and figure out the gpios later :) **** ENDING LOGGING AT Fri Feb 13 02:59:57 2009