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? > 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 > 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 > 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 > 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. > Let me know if I've erred on any of my assumptions. As above. > 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. > 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. > Regards and a good weekend to you, sir, And you. Cheers, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
