Larry Finger schrieb am Do, 12.04.2007 (19:53:24 -0500): > Philipp, > > I can give you a little further info about the LED and the switch. The > switch controls the radio, but it doesn't actually control the LED. The > status is reported through a single bit that is read-only from the > processor. In addition, the switch doesn't cause an interrupt. What happens > is that the bcm43xx driver runs a periodic thread that is scheduled every > one second. Among other things, it compares the hardware bit with a saved > setting. If the bit changes, the appropriate message is logged and the LED > control bits are changed. That is why there is a delay from the time the > switch is pressed until the light changes state. The radio, however is > turned off immediately. Your description matches exactly what is programmed.
Great, so it is just a hardware limitation... Understanding this, I would personally prefer, that the driver turns on the LED and brings up the interface, when loaded and detecting the radio enabled. If the user doesnt like this, he can permanently turn off WLAN using the switch? > > I am currently working on a patch to turn off the LED when the driver is > unloaded either by rmmod or by rebooting. So far it isn't working. turning off the LED, when doing a rmmod already works. Philipp _______________________________________________ Bcm43xx-dev mailing list [EMAIL PROTECTED] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
