2014-06-09 17:45 GMT+02:00 Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>: > On Mon, 09 Jun 2014, Tobias Stegmann wrote: >> After upgrading the kernel toggling the hardware radio switch doesn't >> generate an acpi event anylonger. > > Ideed. But it should be generating an input event, and also whatever event > the rfkill core generates, if any (it used to generate an uevent, which udev > receives. Nowadays, I don't know). > > Can you test that? You should receive a SW_EV SW_RFKILL_ALL event on the > thinkpad-acpi input event device, where all hotkeys go. > > You will also receive a poll() event on the thinkpad-specific sysfs node for > the radio switch, but that's not a nice interface for shell script use. > > You might also receive some sort of uevent over udev, if the rfkill core did > not stop issuing those, and I belive you can use "udevadm" to verify it. > Udev can launch scripts. There are indeed both rfkill udev events and SW_EV SW_RFKILL_ALL input events. I couldn't find any documentation how to use input device events for triggering scripts except using crazy udev key mappings. Using rfkill udev rules works fine. Thanks for pointing that out. > Well, the logic is like this: there is a generic event for this type of > information, and it is an input event. The thinkpad-acpi-specific event has > been, therefore, deprecated way back in 2007. Thanks for clarification. No need to patch it then. -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
