On Fri, 31 Oct 2008, Matthew Garrett wrote: > > Actually, normal boot doesn't preserve the setting either. Your commit > > changes the behaviour from the rfkill state being persistent across > > reboot / power off (as a bios setting), to being always enabled on > > boot. It seems like a bad idea to me. > > This is the behaviour of the rfkill core. When you don't use rfkill_set_default(). Which, if you are a platform driver, and your platform can store state across power off, you should use. Yeah, it is a new thing, sort of. But it is in mainline already, so feel free to use it. The right way to do it is to call it BEFORE doing any rfkill_register or rfkill_allocate. Only the first caller for a given rfkill type, wins. -- "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-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
