[Pkg-acpi-devel] Bug#586924: Bug#586924: Acknowledgement (acpi-support: Rules calling acpi_fakekey cause events to be reported tiwce)

[Luca Niccoli]

On 24 June 2010 10:33, Michael Meskes <meskes at debian.org> wrote:

> Which version of the Eee PC do you have? Please have a look into
> /etc/acpi/asus-brn-up.sh for instance. It already checks for the original Eee
> PC and does nothing on these systems. Apparently the same action should be done
> on other Eees but not having such a system I need some input.

I think it should do nothing on any Eee, this is a snippet from eeepc-laptop.c:

static struct key_entry eeepc_keymap[] = {
	/* Sleep already handled via generic ACPI code */
	{KE_KEY, 0x10, KEY_WLAN },
	{KE_KEY, 0x11, KEY_WLAN },
	{KE_KEY, 0x12, KEY_PROG1 },
	{KE_KEY, 0x13, KEY_MUTE },
	{KE_KEY, 0x14, KEY_VOLUMEDOWN },
	{KE_KEY, 0x15, KEY_VOLUMEUP },
	{KE_KEY, 0x1a, KEY_COFFEE },
	{KE_KEY, 0x1b, KEY_ZOOM },
	{KE_KEY, 0x1c, KEY_PROG2 },
	{KE_KEY, 0x1d, KEY_PROG3 },
	{KE_KEY, NOTIFY_BRN_MIN,     KEY_BRIGHTNESSDOWN },
	{KE_KEY, NOTIFY_BRN_MIN + 2, KEY_BRIGHTNESSUP },
	{KE_KEY, 0x30, KEY_SWITCHVIDEOMODE },
	{KE_KEY, 0x31, KEY_SWITCHVIDEOMODE },
	{KE_KEY, 0x32, KEY_SWITCHVIDEOMODE },
	{KE_END, 0},
};

As you see the keys from KEY_WLAN to KEY_PROG3 are all in the range
0000001[0123456789abcdef] that is matched by asus-brightness-up.
Moreover, both brightness up and brightness down match brightness
asus-brightness-down
My eee is a 901, but probably it would be more sensitive to check that
eeepc-laptop isn't loaded, with something like
lsmod | grep -q eeepc_laptop
if [ $? -ne 0 ]; then etc. etc.

Cheers,

Luca