On Fri, 04 Jul 2008, Matthew Garrett wrote: > I'd still have a preference for not including the proc_generate_event > stuff, but I'm not sure that there's any real consensus on that so I'm > not going to block it. FWIW, thinkpad-acpi had to keep the proc_generate_event stuff (it is an established ABI for thinkpad-acpi since 2.6.12 or thereabouts...), but it does NOT issue those events over netlink at all, so anyone switching to the new ACPI event infrastructure is forced to also switch to the input-device infrastructure to get hotkey presses. And once /proc/acpi is gone, the old way will be gone. Unless someone posts a recipe here of how to get HAL to connect to an input device, and how to tell it to run code when a KEY_* event is received (which you could add to the driver documentation), I'd say proc_generate_event will have to be tolerated. It is all most people know how to deal with in userspace. So, FW(little)IW... Acked-by: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> -- "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
