From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Joey Lee <jlee@novell.com>, Takashi Iwai <tiwai@novell.com>,
Thomas Renninger <trenn@novell.com>,
carlos@strangeworlds.co.uk, jbenc@suse.cz,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/3] Add acer wmi hotkey events support
Date: Mon, 18 Oct 2010 10:23:46 +0100 [thread overview]
Message-ID: <20101018092346.GA19058@srcf.ucam.org> (raw)
In-Reply-To: <AANLkTimxdxSz3rnbwjEzftwY_3XrUJABB9sCXPSz-J_N@mail.gmail.com>
On Mon, Oct 18, 2010 at 10:19:37AM +0200, Corentin Chary wrote:
> But if we do, we could add KEY_TOUCHPADTOGGLE 0x1b8
> Then bind it to XF86XK_TouchpadToggle (what's the right way to do that
> ? keymaps ?)
Yeah, we can add it to the X evdev map. That's not a problem. The only
problem I see is that we don't have a good semantic definition - some
machines send a toggle keycode, whereas others send on/off. That
wouldn't in itself be a problem, but sometimes that's accompanied by the
touchpad being disabled by the BIOS. In the latter case we probably
don't want to map it, since the BIOS can do it anyway, but there's an
argument that we need some way to expose that to userspace.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-10-18 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 4:53 [PATCH 1/3] Add acer wmi hotkey events support Joey Lee
2010-10-18 8:12 ` Dmitry Torokhov
2010-10-18 8:19 ` Corentin Chary
2010-10-18 8:25 ` Dmitry Torokhov
2010-10-18 8:47 ` Corentin Chary
2010-10-18 9:26 ` Takashi Iwai
2010-10-18 9:23 ` Matthew Garrett [this message]
2010-10-18 23:48 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 9:43 Joey Lee
2010-10-19 15:53 ` Dmitry Torokhov
2010-10-19 9:35 Joey Lee
2010-10-19 9:31 Joey Lee
2010-10-13 3:47 Lee, Chun-Yi
2010-10-13 18:24 ` 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=20101018092346.GA19058@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=carlos@strangeworlds.co.uk \
--cc=corentin.chary@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jbenc@suse.cz \
--cc=jlee@novell.com \
--cc=linux-input@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tiwai@novell.com \
--cc=trenn@novell.com \
/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;
as well as URLs for NNTP newsgroup(s).