On Mon, 07 Jul 2008, Andrew Lutomirski wrote: > I agree that rfkill is about stopping rf emission, but rf devices with > the emission turned off are generally useless (other than monitor > mode) and it might be nice to do everything possible to reduce power > consumption when rfkill is blocked. Also, even if a device can't Well, I assume the wireless device drivers will do their best to save power on its own. It already knows it is rfkilled, after all... I don't see what else rfkill could do to help :-) > specifically block RF emission, having an easy-to-use off switch is > still handy. I can't agree with that unless we rename the whole rfkill stuff to something else. Otherwise, you are giving the user the wrong idea (that the transmitter is silent, when it is still sending out a carrier, or beacons, or whatever), and that can be dangerous. IMHO, the easy-to-use generic off switch for data is "ip link set ethX down"... > Now I'm running wireless-testing + thinkpad-acpi 0.21-20080703 and > everything appears to work (the button controls just bluetooth, the > switch works and gets noticed by the driver, etc). I turned off > Ubuntu's hotkey-setup, which had some alternate thinkpad thing. Some stuff might have lingered inside HAL or acpid, though. Just a head's up. > Nice work on the new thinkpad-acpi, BTW. It's quite an improvement. Thanks. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
