On Sun, Feb 07, 2010 at 04:27:02PM +0100, RafaÅ? MiÅ?ecki wrote: > 2010/2/7 Michael Buesch <[email protected]>: > > On Sunday 07 February 2010 15:59:53 strk wrote: > >> On Sun, Feb 07, 2010 at 03:48:07PM +0100, Michael Buesch wrote: > >> > On Sunday 07 February 2010 15:44:01 strk wrote: > >> > >> > > Ok, so supposedly here the situation can be on of these: > >> > > > >> > > Â 1) b43legacy driver is wrong while reading kill switch state > >> > > Â 2) something (software) is toggling kill switch > >> > > > >> > > Would case 1 be fixed by having b43legacy NOT check the state ? > >> > > >> > Well, it would not be a fix, but it would possibly be a workaround for > >> > it. > >> > >> If it *does* work as a workaround it'd be a good reason to add > >> a load-time option to the driver (allow workaround to bogus behaviours). > >> I'll let you know if it does work. > > > > We are not going to add module options to workaround bugs. We fix the bug > > instead. > > ++ > > Please test first if it actually changes anything.
Aaargh, my laptop's screen just died. It'll probaby take some time before I go on with this task (luckly the *wired* nic still works). --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
