From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fn keys on Dell Latitude E6440
Date: Sat, 17 May 2014 14:39:45 +0000 [thread overview]
Message-ID: <201405171639.45722@pali> (raw)
In-Reply-To: <201404141651.08779@pali>
[-- Attachment #1: Type: Text/Plain, Size: 1815 bytes --]
On Monday 14 April 2014 16:51:07 Pali Rohár wrote:
> Hello,
>
> on my notebook dell-wmi kernel driver generates some scan
> codes when I press some of Fn key combinations. Now all these
> scan codes are mapped to key "prog3". I would like to add
> some actions for these Fn key combinations, so what do you
> think? Which key codes should be assigned for these scan
> codes? Note that these combinations are not special (and
> labeled) as other (like Fn+F11 = play/pause) and seems like
> windows does not recognize them.
>
> Matthew, you are author of dell-wmi driver, do you know if
> there are some other secrets key combinations? And why first
> 10 Fn key combinations generate scan codes?
>
> Output of commands:
>
> $ lsinput
>
> /dev/input/event7
> bustype : BUS_HOST
> vendor : 0x0
> product : 0x0
> version : 0
> name : "Dell WMI hotkeys"
> phys : "wmi/input0"
> bits ev : EV_SYN EV_KEY EV_MSC
>
> $ /lib/udev/keymap -i /dev/input/event7
>
> scan code: 0x10 key code: prog3 --> Fn+Q
> scan code: 0x11 key code: prog3 --> Fn+W
> scan code: 0x12 key code: prog3 --> Fn+E
> scan code: 0x13 key code: prog3 --> Fn+R
> scan code: 0x14 key code: prog3 --> Fn+T
>
> scan code: 0x1E key code: prog3 --> Fn+A
> scan code: 0x1F key code: prog3 --> Fn+S
> scan code: 0x20 key code: prog3 --> Fn+D
> scan code: 0x21 key code: prog3 --> Fn+F
> scan code: 0x22 key code: prog3 --> Fn+G
>
> $ cat /sys/class/dmi/id/sys_vendor
> Dell Inc.
>
> $ cat /sys/class/dmi/id/product_name
> Latitude E6440
I looked deeper into dell-wmi driver and bios DMI keycode table.
I will send patch for dell-wmi driver which adding support for Fn
key combinations.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-05-17 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 14:51 Fn keys on Dell Latitude E6440 Pali Rohár
2014-05-04 8:25 ` Pali Rohár
2014-05-17 14:39 ` Pali Rohár [this message]
2014-05-17 14:43 ` [PATCH 0/2] dell-wmi: Add support for Fn key combinations Pali Rohár
2014-05-17 14:43 ` [PATCH 1/2] Input: Add keycodes for some missing " Pali Rohár
2014-05-17 20:30 ` Dmitry Torokhov
2014-05-17 20:38 ` Pali Rohár
2014-05-17 21:32 ` Dmitry Torokhov
2014-05-17 14:43 ` [PATCH 2/2] dell-wmi: Add support for " Pali Rohár
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=201405171639.45722@pali \
--to=pali.rohar@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 NNTP newsgroup(s).