George: I have been following the changes you have posted, and attempting to get them to work on a Linksys E3000 as well (same hardware as the WRT610nV2). I had a working image using the 2.6.22 patches you had posted a while back; and the 2.6.37 version boots up with working USB, but no success with ethernet. Interestingly, one of the wireless devices can be made to work on the E3000 using the existing broadcom-wl driver in trunk with a small patch to recognize the device. I have a number of patches that can be submitted once there is something to submit them against; some of them could be applied directly to trunk as well. I'm anxious to see your latest set of kernel patches if you have the ethernet working, as it shouldn't take much to get the ethernet working on the E3000/WRT610nV2. If the patches aren't submitted to trunk soon; is there a chance you could post your latest patches here again?
Thanks, Nathan > From: geo...@znau.edu.ua > To: openwrt-devel@lists.openwrt.org > Date: Fri, 11 Feb 2011 00:09:19 +0200 > Subject: Re: [OpenWrt-Devel] [PATCH 002/002] ASUS RT-N16 kmod-diag > and base-files detection/setup support > > Hi, > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi, > > > > the patches look okay but afaik we don't even have a bootable version > > for the RT-N16 yet, are you planning to do more work on this? > > > > ~ Jow > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.10 (GNU/Linux) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > > > iEYEARECAAYFAk1UXgsACgkQdputYINPTPNdvQCdErrgGh1GKK+ZTpUwUjs5oVsM > > aWEAoIOZafLPNbMQIpTLrnUvGxA81TOw > > =hVsY > > -----END PGP SIGNATURE----- > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > > No b43 yet. > Everything else works. See bootlog attached to #6580 ticket. > > Code changes required to get it work with current kernels aint agreed > yet - working with it at linux-wireless currently. Therefore code > merging with bcm47xx target aint desirable yet. > If there is such possibility would be great if you let it live under > separate bcm4716 target I could help to manage for those who desperated > to wait these 4716'based boxes working. Also this would help alot for > wider platform changes' testing. > If not I can still share patchwork to get that bcm4716 target appear but > without support from your side. Everything is up to your decision. > > As for changes proposed by those 3 patches I've posted they are 100% > working and 100% harmless for other targets - thinks its obvious ;) > > Have nice day, > George > > > _______________________________________________ > 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
