On Thu, 11 Dec 2008, Tony Vroon wrote: > The laptop has one "big" kill switch that kills everything, > WLAN/Bluetooth/3G, you name it. I have no means to turn individual > radios on or off, all I'll get is a big notifier (from which I can fire > up a query to see whether the kill switch state got changed). That is an input device, that should issue EV_SW SW_RFKILL_ALL events (and not EV_KEY, etc). So, you won't even #include <linux/rfkill.h>. The only pitfall I know of is that you have to re-sync the input layer at every point it could have missed a state change. This means you must issue gratuitous EV_SW SW_RFKILL_ALL events with the current state of the switch after you created the input device, after resume (from S3/S4), and when you get the notifier from ACPI that the switch state could have changed. -- "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
