On 11/18/2010 01:30 PM, Luca Niccoli wrote: > On 18 November 2010 18:00, Ben Armstrong <[email protected]> wrote: > >> I've patched & locally built acpi-support and have locally built >> eeepc-acpi-scripts from master & installed them both, along with my >> patched 2.6.32 (adds eeepc-wmi.ko) but these are not working for me on >> 1001PX for a number of keys (volume keys, which I have configured to be >> bound to their handlers, and the touchpad toggle). Haven't yet had a >> chance to figure out why. I'll give you more details when I can. > > The changes I've pushed are justto fix notifications, not button handling. > I wasn't sure how you meant the hotkey detection to be implemented, so > I didn't touch that.
Ah, right. Didn't have a chance to look at your patches yet, and I suspected something like this. :) > Where should the file that records that hotkey events are being sent live? > If in /tmp/, the first time after every boot that the user presses a > hotkey is not guaranteed to work (the button notification could arrive > first, so the scripts would react twice to the keypress). > If in /var/lib, we risk keeping stale information in case the user > migrates to a new netbook. > Thinking again about it, the "quirks" approach based on module name > seems safer for now. I agree. Also I confirmed with upstream that for the foreseeable future, eeepc_laptop will continue to issue hotkeys. > If new kernels do completely away with hotkeys sooner than we feel > ready to do the same, we can easily add them to the quirks list. Yup. Ben _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
