From: Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: How to support new buttons?
Date: Mon, 2 Dec 2002 12:39:35 +0100 [thread overview]
Message-ID: <20021202123935.4df753c1.nils@kernelconcepts.de> (raw)
Hi all!
First off: Many thanks for your big efforts on getting ACPI into Linux!
ACPI is not at all easy (from what I have seen now) and it is a lot of
work. I appreciate this very much.
So. And now that I own a brand new laptop which only works partially
with ACPI I would like to help a little. As a small first task I would
like to support the additional buttons I have here which very obviously
cause ACPI events. The machine I am talking about is an Asus L3800C.
This machine has four hotkey on top of the keyboard. One is supposed to
be a speedstep control button, on is "email" (what nonsense :), and the
other two have some strange symbols on them (no idea what they are
supposed to be good for). When I enable ACPI debugging I can see that
"something" happens when I press those buttons and this "something" is
different for all four of them. Oh, and ACPI interrupt is triggered on
press. But /proc/acpi/event does not show an event.
I suspect that those buttons are simply not supported by the button
driver yet. Looking at button.c I see that only power, sleep and lid are
supported.
So, how can I add support for those additional buttons?
Oh, I don't expect a detailed a full answer. Just a pointer for an ACPI
newbe please :)
CU
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen D1 : +49-170-2729106
--
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
reply other threads:[~2002-12-02 11:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021202123935.4df753c1.nils@kernelconcepts.de \
--to=nils-t93ne7xhvje5bsectf/tx7nah6klmebb@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.