On Fri, 04 Jul 2008, Matthew Garrett wrote: > On Fri, Jul 04, 2008 at 09:07:54AM -0300, Henrique de Moraes Holschuh wrote: > > 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. > > hal has bound to input devices for years. It won't run code directly, > since that's a policy decision, but lshal -m should show events come > from input devices. Is there an easy way to duplicate what acpid does (i.e. give HAL some config file that tells it to run an extrenal script when it gets a certain event)? If there is not, it is no wonder people don't want to go away from acpid and we have to keep proc_generate_event around... -- "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
