From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-input <linux-input@vger.kernel.org>,
linux-hotplug@vger.kernel.org, xorg@lists.freedesktop.org,
Peter Hutterer <peter.hutterer@who-t.net>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Martin Pitt <martin.pitt@ubuntu.com>
Subject: Re: Touchpad toggle mess
Date: Thu, 4 Nov 2010 19:20:05 -0700 [thread overview]
Message-ID: <20101105022004.GA26173@core.coreip.homeip.net> (raw)
In-Reply-To: <1288915209.5418.72.camel@novo.hadess.net>
Hi Bastien,
On Fri, Nov 05, 2010 at 12:00:09AM +0000, Bastien Nocera wrote:
> Heya,
>
> In GNOME 2.32, we added support for touchpad toggle buttons, by
> capturing the XF86TouchpadToggle button in gnome-settings-daemon,
> showing a nice popup, and disabling the touchpad in software.
>
> That works great for a number of laptops, but completely breaks a number
> of others where the hardware handles the request, but still sends a key
> event (usually separate ones for on and off). In those cases, we'd need
> 2 more key types, in the kernel, and in X.org.
Rfkill story all over I guess ;(
>
> The patches in https://bugs.freedesktop.org/show_bug.cgi?id=31300
> implement this for the kernel, and for X.org.
>
> Then we have the problem that udev's keymaps seem to use different
> function keys depending on the hardware [1], when X.org (because of the
> limitations of XKB) standardised on F22 for "XF86TouchpadToggle".
>
> So we'll need to standardise on the keys used. I selected F21 for
> XF86TouchpadToggle, F22 for XF86TouchpadOn and F23 for XF86TouchpadOff.
> See the patch in:
> https://bugs.freedesktop.org/show_bug.cgi?id=31333
>
> The remaining fixes would need to be in udev's keymaps, to set hardware
> handled keys to F22 and F23, and software ones to F21. Patch is attached
> for that.
>
> Questions, comments?
I still believe we need dedicated keycodes in kernel for that and make
sure that in-kernel maps use proper keycodes so that programs that do
not have the same limitations that X has could differentiate between
touchpad events and real F2* events. X can still continue to use f21, 22
and 23 (at least while it can't handle higher keycodes), and common
setups may rely on udev's facilities to remap the keys.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-11-05 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 0:00 Touchpad toggle mess Bastien Nocera
2010-11-05 2:20 ` Dmitry Torokhov [this message]
2010-11-06 15:56 ` Bastien Nocera
2010-11-06 15:30 ` Martin Pitt
2010-11-06 15:58 ` Bastien Nocera
2010-11-06 16:33 ` Martin Pitt
2010-11-06 17:17 ` Bastien Nocera
2010-11-13 18:10 ` Julien Cristau
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=20101105022004.GA26173@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=mjg59@srcf.ucam.org \
--cc=peter.hutterer@who-t.net \
--cc=xorg@lists.freedesktop.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 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).