On Tue, Dec 08, 2009 at 04:45:05PM +0100, Jes Sorensen wrote: > On 12/08/09 13:55, Matthew Garrett wrote: >> The problem with that is that there's no event to indicate that the >> switch has been turned back on, so there's no way to update the rfkill >> core appropriately. Giving userspace potentially stale information >> doesn't seem helpful. > > I believe I can call into BTST and determine whether the switch is set > to on or not. It's quite easy to add this to the resume handler and only > call if it's set to on. Right, but in normal use it's an issue. Unless we get notifications for both types of state change, we can't add an rfkill device. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
