good job! 2010/12/20 George Kashperko <geo...@academy.zt.ua>
> Hi All, > > Might be posting not in a proper thread but one regarding ASUS RT-N16 looks > like dead one atm. Anyway afaik Linksys WRT610n v2 is built around BCM4718 > soc, > the same as N16 one is based on. So may be I could be of some use for those > who wanna get Openwrt running on their boxes. > > I've spent some time with RT-N16 GPL code from ASUS (you can get one from > ftp://ftp.asus.com/pub/ASUS/wireless/RT-N16/GPL_RT_N16_1019.zip). Cleaned > it up a > bit as it was based on some intermediate git of 2.6.22 and got a patch > (about 250Kb) against linux-2.6.22. Unfortunately this code is built around > Broadcom's SDK one (release 5.10.147.0 if I got it right). Everything about > soc hw (ssb, pci, etc.) in kernel itself is left intact, instead bunch of > Broadcom's code doing all the stuff about detecting, initializing and > managing BCM471x hardware. Also to get this kernel built one need at least > two > proprietary Broadcom's .o object files (one for wireless driver, and > another one for ctf driver code) both provided with original ASUS GPL > package (ftp > link to .zip from ASUS is above) and two more .o's to get wl supplicant and > configuration tool running (from > http://mirror2.openwrt.org/sources/broadcom-wl- > 5.10.56.27.0.tar.bz2). Also you can get just these .o's alone at > http://www.znau.edu.ua/temp/asus-rt-n16/asus-rt-n16.2.6.22.mips2.files.tar.bz2 > > Attached is the patch against current (last tried it with 24667) Openwrt > trunk to get it run on RT-N16 with 2.6.22.19 kernel. Also you can dl it from > > http://www.znau.edu.ua/temp/asus-rt-n16/asus-rt-n16.2.6.22.mips2.files.tar.bz2 > > I know pre2.6.34 kernel support is wiped out from Openwrt trunk, and this > one is based on 2.6.22. Just hope this could be of some use as the > alternative to > original/dd-wrt/tomato/wl500g/etc. firmware till we get mainline kernel > working with 4716/18, and maybe of some use for porting ssb/pcie code from > Broadcom's SDK. > > Atm I've got 3 RT-N16 boxes running with this stuff and it seems they work > smooth enough (except for bunch of annoying messages "protocol 0000 is > buggy, > dev eth1" in dmesg). > > For those who will decide to try it out keep in mind that: > 1. 2.6.22'based code is moved out into different target (brcm4716 instead > of the brcm47xx as used in trunk and earlier Openwrt releases) in order not > to > break current 47xx functionality. > 2. Packages "base-files", "broadcom-diag", "nvram" and "switch" where > patched to get them working with this new target, but those changes should > not affect > original brcm47xx target's functionality. > 3. To get broadcom-hnd package compiled (mainly its for ethernet and > wireless drivers with wl supplicant and cfg tool) one need four precompiled > .o files > (nas_exe.o, wl_exe.o, ctf.o and either wl_ap.o or wl_apsta.o or wl.sta.o > depending on planned wl mode) - get them from > http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.0.tar.bz2 and > ftp://ftp.asus.com/pub/ASUS/wireless/RT-N16/GPL_RT_N16_1019.zip or dl > > http://www.znau.edu.ua/temp/asus-rt-n16/asus-rt-n16.2.6.22.mips2.files.tar.bz2for > just these files alone. > 4. After patching the trunk chmod +x following scripts: > target/linux/brcm4716/base-files/etc/init.d/netconfig > target/linux/brcm4716/base-files/etc/init.d/wmacfixup > target/linux/brcm4716/base-files/sbin/hotplug.failsafe > 5. You will need to get things compiled with binutils 2.20.1 and gcc 4.2.4. > Newer gcc refuses to compile that stuff. Other binutils might work but never > tried it itself so better stick to 2.20.1 one. The same stands to uClibc - > tested it with 0.9.30.1, others might work or might not. Issue make > menuconfig > and set proper gcc/binutils/uClibc vers in "Advanced configuration options > (for developers)"/"Toolchain Options" or just cp 2.6.22.19.config .config to > use > mine template config provided with patch. > 6. Keep in mind that after reflash during first boot your box will start > formatting mtdblock3 for linux-data jffs2 partition and it could take some > time > (about 3-5 mins for mine N16 with 32Mb flash). If you reset the box before > it finish with format and after then run "mtd fixtrx" your box will enter > emergency repair mode (at least N16 does so) or potentially could get > bricked - so better let it finish with format or even better get yourself > uart->rs232 > to watch how's it going online. This one thingy could get been fixed with > proper drivers/mtd/maps/bcm947xx-flash.c code ofcourse, but I just dont > think it > worth time spent. > 7. See files "network" and "wireless" in /etc/config.tmp/ after you get box > flashed and running for network/wireless uci config templates. > > For those who are interested in cleaned up Broadcom's kernel patch code > look for it in > target/linux/brcm4716/patches-2.6.22/000-linux-2.6.22.19.asus- > gpl.rc8.patch (there were bits more things in netfilter code managing h/w > acceleration - keep in mind I've wiped that code out). > > Also, I would be pleased to help with porting brcm4716/18 support into > mainline kernels but dunno atm at which point should I start. Regarding > patches by > Bernhard Loos, Hauke Mehrtens and Jonas Gorski allowing thingy to boot I > would be much appreciated if you point me in right direction where to assist > - > either consider new ssb search/init/management code stable and start > rewiewing pcie code or maybe ssb stuff still need some more work? Also would > be > much appreciated if one will advise where to get bits more tech info > regarding newer ssb and pcie in 4716/18's if such exists (I've seen > http://voodoowarez.com/bcm5365p.pdf mentioned alot regarding ssb but it > seems http://voodoowarez.com is completely dead by now). > > George > > -----Original Message----- > From: Ryan Bair <ryandb...@gmail.com> > To: openwrt-devel@lists.openwrt.org > Date: Thu, 16 Dec 2010 12:09:12 -0500 > Subject: [OpenWrt-Devel] WRT610n v2 support > > > Hi all, > > > > I have a bit of time off between now and the end of the year and a > > new-to-me WRT610n v2 sitting in the box. > > > > From what I can tell, the majority of the hardware is the same between > > the newly supported v1 and the unsupported v2 with the very notable > > exception of the bcm4716 soc. It also seems like at least some level > > of support for the bcm4716 exists, although on last note it looks like > > it might only boot with serial access. > > > > Has anyone attempted to flash the wrt610n v2 from trunk? Can anyone > > let me know what the current status of the 4716 (and the wrt610n v2 > > specifically) is and what next steps are? > > > > Thanks > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
