[Debian-eeepc-devel] eeepc-acpi-scripts integration: drop conflict with acpi-support

[Luca Niccoli]

I think it would be useful to stop conflicting with acpi-support.
This would mean:

* drop the suspend, lid and hotkey-video event rules;
* drop the ac_adapter events and find a way to manage SHE anyway
(hooks in /etc/pm/power.d seems the best solution to me)
* resolve the event conflict for the hotkeys:

acpi-support ships the following event rules

/etc/acpi/events/asus-eee-volume-down:event=hotkey ATKD 00000014
/etc/acpi/events/asus-eee-volume-mute:event=hotkey ATKD 00000013
/etc/acpi/events/asus-eee-volume-up:event=hotkey ATKD 00000015

These three rules just generate key symbols for special eee keys.
The kernel module already does that, they can be dropped from acpi-support.

/etc/acpi/events/asus-brightness-down:event=hotkey (ATKD|HOTK)
0000002[0123456789abcdef]
/etc/acpi/events/asus-brightness-up:event=hotkey (ATKD|HOTK)
0000001[0123456789abcdef]

These three rules just generate key symbols for special eeepc and asus keys.
On the eee this is done by a kernel module; if this is true on the
other asus laptops as well, they can be dropped.
We could mask them away, giving up the OSD for brightness change.
There could be some problems with double brightness keys symbols
reported to X though.

/etc/acpi/events/asus-video:event=hotkey (ATKD|HOTK) 0000006[123]
/etc/acpi/events/asus-media-eject:event=hotkey (ATKD|HOTK) 0000004c

This rules just generate key symbols for non-eee keys. If this is done
by the kernel, they can be dropped; we should mask them away.

/etc/acpi/events/asus-f8sv-touchpad:event=hotkey ATKD 0000008a
/etc/acpi/events/asus-rotate:event=hotkey (ATKD|HOTK) 0000009b
/etc/acpi/events/asus-wireless-off:event=hotkey (ATKD|HOTK) 0000005e
/etc/acpi/events/asus-wireless-on:event=hotkey (ATKD|HOTK) 0000005f

We should mask these away.

/etc/acpi/events/asus-touchpad:event=hotkey (ATKD|HOTK) (0000006[ab]|00000037)

We should drop this from e-a-s and let acpi-support manage it.


I didn't notice any other conflict.
Did I miss anything?

The plan I imagine would be these:
Push changes in acpi-support.
Start using a selective hotkey mask in /etc/acpi/events/hotkey
Then, all in a single upload:
Drop the conflict on acpi-support and start depending on it.
Drop sleep, lid, ac, hotkey-video event rules.
Ship a hook in /etc/pm/power.d/ to switch the SHE if it is set to auto.

If there is consensus, I'll start by preparing a patch for e-a-s with
a selective hotkey mask, and by filing a bug report on acpi-support to
drop the three volume keys rules.

Cheers,

Luca