From: Niels de Vos <niels.devos@wincor-nixdorf.com>
To: linux-input@vger.kernel.org
Cc: linux-laptop@vger.kernel.org
Subject: Re: Support special keys on laptop by default?
Date: Tue, 06 Jan 2009 17:13:36 +0100 [thread overview]
Message-ID: <49638330.2070605@wincor-nixdorf.com> (raw)
In-Reply-To: <49636A4B.2050201@wincor-nixdorf.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Niels de Vos wrote:
> Jiri Kosina wrote:
>> On Tue, 6 Jan 2009, Niels de Vos wrote:
>>
>>> on my HP/Compaq nc6400 there are three keys (info, presentation and
>>> battery) not directly recognized. If I press any of the keys, I get:
>>>
>>> atkbd.c: Unknown key released (translated set 2, code 0xd9 on isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
>> [ ... ]
>>> Where should I start looking for creating a patch for solving problems
>>> of this kind? There seem to be quirks in atkbd.c, but I think they are
>>> used for some other workarounds.
>> Please see
>> http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-index.html
>>
Just for the record:
Okay, for these (and a lot more) keys I (and you) need at least
hal-0.5.10 as said in the link above from Jiri. The keys supported by
hal are available in the 30-keymap-*.fdi files from the hal-info git:
http://cgit.freedesktop.org/hal-info/tree/fdi/information/10freedesktop
I hope this helps people with the same questions and problems.
Thanks for your help,
Niels
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2009-01-06 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 13:14 Support special keys on laptop by default? Niels de Vos
[not found] ` <b92a6cf90901060527x1bd1d84g873d77b5f31f57d9@mail.gmail.com>
2009-01-06 13:34 ` Niels de Vos
2009-01-06 14:26 ` Jiri Kosina
2009-01-06 14:27 ` Niels de Vos
2009-01-06 16:13 ` Niels de Vos [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=49638330.2070605@wincor-nixdorf.com \
--to=niels.devos@wincor-nixdorf.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-laptop@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).