From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Dell Latitude E6530 keymap
Date: Tue, 26 Mar 2013 00:46:46 +0000 [thread overview]
Message-ID: <12404242.vZyCnnzvRk@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20580.1364167284@owl>
On Sunday, March 24, 2013 04:21:24 PM Stephen Gildea wrote:
> I have a Dell Latitude E6530 laptop
> (system vendor "Dell Inc.", product name "Latitude E6530").
> A few of the keys are mapped incorrectly:
>
> Fn+F5, Touchpad Toggle
> ----------------------
>
> Fn+F5 is labeled on my keyboard with a "touchpad" icon, and in
> udev 198, the line in /lib/udev/keymaps/dell for it is this:
>
> 0x9E f21 #touchpad toggle
>
> Since we know it is "touchpad toggle" (and I confirm it is), and there
> is a key name for that, how about changing this line to read thusly:
>
> 0x9E touchpad_toggle # Fn+F5
>
> In the same "dell" file, 0xD9 is mapped the same ("f21 # touchpad toggle");
> perhaps it also should be changed to send a real touchpad_toggle?
Unfortunately X can't deal with keycodes above 255 :(
--
Dmitry
prev parent reply other threads:[~2013-03-26 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 23:21 Dell Latitude E6530 keymap Stephen Gildea
2013-03-26 0:46 ` Dmitry Torokhov [this message]
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=12404242.vZyCnnzvRk@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-hotplug@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).