Comment 5 for bug 955176

On Thu, Mar 15, 2012 at 11:34:55PM -0000, greg wrote:
> > The handlers that are probably deprecated are mostly those for ASUS and
> > Toshiba hardware, which no one who works on this package has direct access
> > to.

> At least on Asus notebooks everything should be handled through the
> kernel, with the asus-laptop module.

Well, I'm pretty sure that there's nothing that's going to handle what
/etc/acpi/events/asus-touchpad does, for instance. Could you help to verify
for each of the events listed for /etc/acpi/events/asus-* that, first, you
have a hotkey that outputs the same ACPI event on your system, and second,
that it performs the correct system function even when acpid isn't running?

> > Could you please run acpi_listen and show the actual ACPI events generated
> > for each of these keys? This may be important later in case a different
> > ASUS model isn't being handled correctly in the kernel yet.

> The eeepc-laptop driver generates ATKD events in the range 0x20 to 0x2f,
> depending on the current brightness, where 0x20 is the lowest setting
> and 0x2f is the highest. For instance:

> increment:
> hotkey ATKD 0000002c 00000003
> hotkey ATKD 0000002e 00000006

> decrement:
> hotkey ATKD 0000002c 00000004
> hotkey ATKD 0000002a 00000004

> This conflicts with the asus-brightness-down acpid event, which matches
> all of these events, no matter if the brightness is actually incremented
> or decremented.

Thanks, I've dropped these from the package branch, so this should be fixed
in the next upload.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>