Re: getting new hardware (arbor M1526) buttons to work w/ acpi

[Thomas Renninger <trenn@suse.de>]

On Monday 13 September 2010 20:11:55 Yedidia Klein wrote:
> ok, found that wmi is compiled into my kernel and not built as module.
> while the grep for PNP0C32 returned nothing - so I assume that it;s
> not that.
> 
> is there any way to read these addresses directly via C and not via
> ACPI ?
If the button is ACPI driven you have to look at ACPI code sooner or 
later.
Have you tried showkey yet?

Try:
sleep 1;showkey
and
sleep 1;showkey -s
(the sleep is only that you can escape with CTRL-c).
If you get output if you hit the keys, then forget about ACPI and all
I said. There is a lot documentation about this out there.
Best you learn about:
/etc/X11/Xmodmap
the input layer, xev is a nice tool for these, etc.

If you don't see something with showkey, it's likely that it's ACPI 
driven.
Do:
rmmod battery
rmmod thermal
to avoid other ACPI interrupts
Then:
watch -n1 cat /proc/interrupts
Press the buttons, is the ACPI irq (normally 9) increasing when you
hit any of these?
If yes, it's likely ACPI driven.

Next step would to find out which GPE is fired on each press:
VALID="";for x in /sys/firmware/acpi/interrupts/gpe*;do if cat $x|grep 
enabled;then VALID="$VALID $x";fi;done;watch -n1 cat $VALID

modprobe battery
modprobe thermal
afterwards...

          Thomas