Brian J. Murrell wrote: > On Sat, 2008-10-18 at 19:24 -0700, [EMAIL PROTECTED] wrote: > >> Since you're running a custom distro for a particular branch of >> hardware, have you communicated on their lists about this issue? >> > > Not yet. I thought I would come to the source first. The larger > concentration of experience with b43 is likely here rather than the > OpenWrt developers don't you think? > No. > >> The standard b43 has no issues with it, but I have no idea which version >> of b43 they've picked to be their reference. >> > > http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/08/compat-wireless-2008-08-06.tar.bz2 > That's nice, thank you.
> >> From the firmware rev I suspect it's not a fairly recent one meaning >> the codebase isn't the newest either. >> > > Firmware appears to be from broadcom-wl 4.150.10.5 > Looks correct according to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware > >> In any case, you're on an embedded device running a kernel you didn't >> compile >> > > I sure did! > > >> and whose version you don't mention >> > > 2.6.25.17 > Thanks :) > >> and a driver you didn't build in an environment which I'm guessing you >> also don't build. >> > > Wrong and wrong. All built from source here. > > Awesome. >> Let me know if I've erred on any of my assumptions. >> > > As above. > > Awesome. Thanks for the info. >> For instance if >> you're able to build your own drivers and install >> them on that Linksys, or if you're able to build your own kernels that >> work on that Linksys, those would be two good things >> to know. >> > > Indeed, I can. > > You've got the 2.6.25 code running with the latest firmware. There have been some changes. Can you try and pull the b43 code from the current 2.6.27.1 distro and see if it will run? There's also the wireless-compat tree, but I would try the vanilla 2.6.27.1 tree first. >> If not, talk to OpenWRT. >> > > I may end up doing that. My query here was merely to ascertain whether > what I am seeing is consistent with the current revision of the b43 > driver or not. I believe I am understanding that it is not and that > others are able to run the b43 driver in AP mode with WPA2 encryption > and not having the encryption done in software -- or have high level of > interrupts otherwise. > You are correct. > >> Regards and a good weekend to you, sir, >> > > And you. > > Cheers, > b. > I think you're on the right track. Just fyi (and please take this without insult) had you included your kernel (uname -a) as well as "I built this myself from source from XXXX") it would have made it easier to provide more useful suggestions in the first cut. I think you can make it work. The hardware DOES does do what you want. I suspect either b43 or mac80211 is not as up to date as it ought to be in your newly built kernel. Others know more. I'm just waiting for Shanghai F1 ;) Cheers, Ehud > > ------------------------------------------------------------------------ > > _______________________________________________ > Bcm43xx-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > -- Legal Disclaimer that you are now contractually bound to under all laws with no recourse: http://attrition.org/security/rants/z/disclaimers.html _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
