From: Andrew Morton <akpm@osdl.org>
To: Stefan Seyfried <seife@suse.de>
Cc: vojtech@suse.cz, dtor_core@ameritech.net, luming.yu@intel.com,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
len.brown@intel.com, bero@arklinux.org
Subject: Re: [git pull 02/14] Add Wistron driver
Date: Mon, 12 Dec 2005 00:13:15 -0800 [thread overview]
Message-ID: <20051212001315.0e2c64f1.akpm@osdl.org> (raw)
In-Reply-To: <20051211224059.GA28388@midnight.suse.cz>
Stefan Seyfried <seife@suse.de> wrote:
>
> In article <20051211224059.GA28388@midnight.suse.cz> you wrote:
> > On Sun, Dec 11, 2005 at 01:10:13PM +0000, Bernhard Rosenkraenzer wrote:
> >> I think routing them to the input layer makes most sense because they are keys
> >> like everything else -- of course hacking acpid to pass on ACPI key events to
> >> Xorg via the XTest extension is not exactly hard, but that would break the
> >> keys in text mode (who knows, maybe someone wants to map his mail key to
> >> "mutt[RETURN]"?), and of course launching an application from acpid is a bit
> >> hard (acpid runs as root --> need to figure out which user is pressed the
> >> button, switch user IDs, find the correct X display if any, .....) if it's an
> >> input event, solutions for the expected functionality already exist - e.g.
> >> khotkeys.
> >
> > You also can hack acpid to use uinput to feed the events back to the
> > input subsystem, but I agree with you that going there directly is
> > probably the best way to go.
>
> pcc_acpi already does this successfully and is a pleasure to use.
That's not in the tree any more. Did something replace it?
next prev parent reply other threads:[~2005-12-12 8:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 8:11 Yu, Luming
2005-12-06 15:21 ` Dmitry Torokhov
2005-12-11 13:10 ` Bernhard Rosenkraenzer
2005-12-11 22:40 ` Vojtech Pavlik
2005-12-12 8:13 ` Andrew Morton [this message]
2005-12-12 9:14 ` Stefan Seyfried
2005-12-12 9:38 ` Andrew Morton
2005-12-12 11:22 ` Stefan Seyfried
2005-12-12 11:33 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 8:57 Yu, Luming
2005-12-07 14:43 ` Miloslav Trmac
2005-12-06 8:38 Yu, Luming
2005-12-06 7:35 Yu, Luming
2005-12-06 8:15 ` Miloslav Trmac
2005-12-06 8:30 ` Miloslav Trmac
2005-11-20 6:36 [git pull 00/14] Input updates for 2.6.15 Dmitry Torokhov
2005-11-20 6:36 ` [git pull 02/14] Add Wistron driver Dmitry Torokhov
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=20051212001315.0e2c64f1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bero@arklinux.org \
--cc=dtor_core@ameritech.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=seife@suse.de \
--cc=torvalds@osdl.org \
--cc=vojtech@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®