On Sun, Feb 07, 2010 at 03:37:36PM +0100, Michael Buesch wrote: > On Sunday 07 February 2010 15:30:18 strk wrote: > > On Sun, Feb 07, 2010 at 02:05:09PM +0100, Michael Buesch wrote: > > > > > rfkill is a hardware lock in the case of broadcom. Software can only read > > > the state. > > > > > > (There may be laptops with broadcom cards where rfkill can be changed by > > > software. > > > But that's done by other means (BIOS) and the broadcom hardware doesn't > > > know about it.) > > > > Uhm, but still I'm pretty sure there's no physical switch on this laptop > > (L5800C). > > Also, if there was one, surely I wasn't turning it on and off continuosly to > > justify those notices coming down to b43legacy. > > > > Note that bcm43xx used to work fine. > > I'm not talking about possible bugs in the software. I'm just explaining > how the hardware works, because I think there's some confusion here.
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 ? --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
