Richard, Now that KEY_UNKNOWN as the top choice is gone, and that HAL seems to want to map keys by default, the solution I used to not generate hotkey input events and ACPI events in duplicate is busted. I can only think of a few ways to go about it: 1: always generate both events (may cause problems for sleep to disk and sleep to ram, at the very least) 2: allow the user to select which one using an extra mask in sysfs, default is ACPI 3: allow the user to select which one using a module parameter, default is ACPI And the default of 2 and 3 will be bad for input/HAL, because it either will require a module parameter or a write to sysfs to enable input hotkeys, otherwise it would break the ACPI event ABI (because ACPI events would not be generated anymore). Any ideas? -- "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 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
