On Tue, Sep 20, 2011 at 05:43:45PM -0300, Ben Armstrong wrote: > > The general solution *is* the window manager solution. Window managers > and desktop environments should have default mappings for standard keys. > Drivers should fire standard key events. ACPI scripts should not get in > the middle unless they absolutely have to (and I would say what they > should do in that case is map the ACPI event to fire a key with > acpi_fakekey and *then* let the WM/DE handle it). ...
Ok, thank you for your detailed explanation; I eventually found out how to configure my windowmanager to map the keys. > Right. You'll find in git this reads: > > [ -d /sys/devices/platform/eeepc ] || [ -d > /sys/devices/platform/eeepc-wmi ] || exit 0 > > i.e. it continue on so long as either eeepc-laptop or eeepc-wmi is > loaded. we haven't fully finished support for eeepc-wmi. ... OK, I was assuming that the package in testing/sid was rather up-to-date; good that you already fixed those. Thanks again! Cri -- GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc
signature.asc
Description: Digital signature
_______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-eeepc-devel
