On Wed, 13 Jun 2007, Richard Hughes wrote: > > find a way to tap into the ACPI interrupts the low-level firmware does > > generate when it changes the NVRAM bits. > > Yes, although I've had no luck with this on my X60. Ideas welcome. Activate ACPI debug and tracing, and trap all _Q* ACPI GPE events. There is no way IBM or Lenovo would have been so nice to give us a high-level interface to it, and it is probably going to be very model specific, so we probably will need to do a whitelist + force-it-on option approach while we find out. > > > I understand you want to preserve compatibility, but that can be done > > > with either the KEY_UNKNOWN checks you are currently doing in the > > > input-hotkey branch, or with a use_acpi_events=1 module parameter. > > > > KEY_UNKNOWN appears to be the best choice for thinkpad-acpi, then. I > > understand HAL is going to re-map these keys to something when it loads up, > > and NOT use them as KEY_UNKNOWN, correct? > > Correct. Then, that's what thinkpad-acpi shall do. -- "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
