From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Christen <davidchristen@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Enable addition function keys
Date: Mon, 23 May 2011 23:22:56 -0700 [thread overview]
Message-ID: <20110524062256.GA20829@core.coreip.homeip.net> (raw)
In-Reply-To: <000001cc1403$1e0ede10$5a2c9a30$@com>
Hi David,
On Mon, May 16, 2011 at 09:54:49PM +0200, David Christen wrote:
> I have a custom made keyboard with 48 Function keys attached to an embedded
> PC running on a RISC CPU. With hid module in the kernel the regular part of
> the keyboard (i.e. all letters, num pad and Fxx keys up to F12) are working
> perfectly fine. However with the additional keys I don't get any events in
> /dev/input/event0. This is the same behavior as found on a regular Linux PC
> and also under Windows. Although the manufacturer of the keyboard confirmed
> that those keys do send proper HID codes (0x68 to 0x8b for F13 to F48).
> I don't have any experience in programming on the Kernel level. Could you
> maybe direct me in how to get the input events of those keys running?
>
Even though the usage codes are not mapped you should be able to map
them yourself using EVIOCSKEYCODE ioctl. See udev sources for how to
adjust keymaps on input devices.
We have F1 through F24 keycode defines, but no F25-F48 (nor do I want to
add these since userspace would not really know what to do with these,
they are device-specific); you'll have to pick some standard ones that
match the functions you want to assign to your extended keys.
Hope this helps.
--
Dmitry
next prev parent reply other threads:[~2011-05-24 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:54 Enable addition function keys David Christen
2011-05-24 6:22 ` Dmitry Torokhov [this message]
2011-05-24 11:30 ` David Christen
2011-05-24 16:27 ` David Christen
2011-05-24 16:49 ` Dmitry Torokhov
2011-05-24 17:39 ` David Christen
2011-05-24 17:52 ` Dmitry Torokhov
2011-05-24 18:03 ` Thadeu Lima de Souza Cascardo
2011-05-25 9:48 ` David Christen
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=20110524062256.GA20829@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=davidchristen@gmail.com \
--cc=linux-input@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).