On Wed, 01 Aug 2007, Michael S. Tsirkin wrote: > Forcing the selection at compile-time isn't such a great idea IMHO. > Isn't there a way to support both old and new userspace? It only afects the *defaults* of various driver knobs that can be freely modified at runtime: without THINKPAD_ACPI_INPUT_ENABLED: hotkey_enable = 0 hotkey_mask unchanged from whatever is already set hot keys from ibm-acpi 0.14 are mapped to KEY_UNKNOWN, and thus will generate ACPI events if hotkey_enabled is set to 1. with THINKPAD_ACPI_INPUT_ENABLED: hotkey_enable = 1 hotkey_mask = hotkey_recommended_mask most hot keys are mapped to something other than KEY_UNKNOWN, and thus will not generate ACPI events but rather input layer events. You should select whichever works better with your userspace. -- "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: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
