From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Gildea <stepheng+linux@gildea.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: Dell Latitude E6530 keyboard mapping
Date: Tue, 19 Mar 2013 10:55:31 -0700 [thread overview]
Message-ID: <1426990.1ajUrW6ygT@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <8157.1363531900@owl>
Hi Stephen,
On Sunday, March 17, 2013 07:51:40 AM Stephen Gildea wrote:
> On my Dell Latitude E6530 laptop, some of the function keys and keypad
> keys are mapped incorrectly by the kernel. I first tested this with
> Linux 3.6; testing now with the current head (3.8+), I find that some of
> the keys have been fixed (End, NumLock, KbdLightOnOff, AudioPlayPause).
> Some of the other wrong keys have changed mappings but are still wrong
> (External Screen).
>
> What change fixed these keys, and where should I be looking to fix the
> rest of them? I looked through drivers/platform/x86/, but I don't see
> any other drivers dealing with keyboard mappings.
The mappings for AT keyboards is done by udev (look at its keymaps).
--
Dmitry
prev parent reply other threads:[~2013-03-19 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 14:51 Dell Latitude E6530 keyboard mapping Stephen Gildea
2013-03-19 17:55 ` 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=1426990.1ajUrW6ygT@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stepheng+linux@gildea.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