From: Pavel Machek <pavel@ucw.cz>
To: Florian Festi <florian@festi.info>, vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: Meaning of keycodes unclear
Date: Tue, 5 Dec 2006 12:15:41 +0100 [thread overview]
Message-ID: <20061205111541.GB6987@elf.ucw.cz> (raw)
In-Reply-To: <45753BB1.6030102@festi.info>
On Tue 2006-12-05 10:28:17, Florian Festi wrote:
> I am looking for the meaning of the following key codes as #defined in
> include/linux/input.h. I need to know what hardware produces the keycode
> and what happens/should happen when the corresponding key is pressed.
>
> KEY_AB
> KEY_ANGLE
> KEY_ARCHIVE
> KEY_CONNECT
> KEY_DIGITS
> KEY_MACRO
Macro key was present on some old keyboards. It allowed macro definitions.
> KEY_ISO
> KEY_LIST
> KEY_POWER2
> KEY_QUESTION
> KEY_TEEN # 1- ???
> KEY_TWEN # 2- ???
Yep. Very common on remote controls.
> KEY_RED, KEY_GREEN, KEY_YELLOW, KEY_BLUE # Video text navigation?
Yes.
> I am currently trying to make all special keys just work by fixing the
> whole keyboard/input stack from the kernel up to the desktop
> environments. On part of this effort is to complete the mappings applied
> to the keys during their way up.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-12-05 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 9:28 Florian Festi
2006-12-05 11:15 ` Pavel Machek [this message]
2006-12-05 14:23 ` Johannes Stezenbach
2006-12-05 20:13 ` Bill Davidsen
2006-12-14 15:09 ` Florian Festi
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=20061205111541.GB6987@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=florian@festi.info \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®