On Dec 17, 2007 5:45 PM, Michael Buesch <[EMAIL PROTECTED]> wrote: > > Ehm, excuse me. > What are you doing exactly? In this thread you told me you have > a device which requires b43: >
Well, I'm not sure what you mean by "requires" b43, but I did say that the device uses the b43 driver. > > I don't know what happened before, but after a reboot, I can't repeat > > the 200 kB/s speed. It's back down to 40 kB/s, just like originally. I > > didn't move the laptop, or the ap, the only thing I can think of that > > might have changed is the noise level. FWIW, link quality is > > consistently the same or better with b43. > > How the hell can you now "force it to use b43legacy"?? > Sorry, I should have been more specific. I figured since the device could use bcm43xx, it could also use b43legacy, so I copied the entries in b43_ssb_tbl[] to b43legacy_ssb_tbl[] and rebuilt the b43legacy driver. I removed the b43 and ssb modules, and inserted the b43legacy module. Afterwards, I noticed b43 had still been autoloaded, so I removed it (I checked dmesg and only b43legacy had initialized anyway) , and proceeded to use the b43legacy driver with the version 3 firmware. And like I said, it works exactly like the b43 driver with the version 4 firmware. I'm not sure if it was the best way to go about it, but it worked. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
