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
KEY_ISO
KEY_LIST
KEY_POWER2
KEY_QUESTION
KEY_TEEN # 1- ???
KEY_TWEN # 2- ???
KEY_RED, KEY_GREEN, KEY_YELLOW, KEY_BLUE # Video text navigation?
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.
TIA
Florian Festi
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
On Tue, Dec 05, 2006 at 12:15:41PM +0100, Pavel Machek wrote:
> 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
I'm guessing it's "A/B" key on (TV) remote control, e.g. to switch between
two input sources
> > KEY_ANGLE
probably DVD or set-top-box remote control key to switch
between alternate video streams (video viewing angle / camera position)
> > KEY_LIST
might be used on TV remote control for "channel list"
> > KEY_RED, KEY_GREEN, KEY_YELLOW, KEY_BLUE # Video text navigation?
>
> Yes.
these are really application-defined multi-purpose keys,
not just limited to teletext; present on every European
TV or set-top-box remote control
HTH,
Johannes
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_MACRO
I presume this is the macro defining key, used on keyboards like the
Gateway102. I thought it was handled internally and didn't send a
keycode, but other keyboards had/have that feature as well.
Used G102 for application work, had the function keys both next-to and
above the alpha keys, so you could bind up to 48 application functions
and still have function keys as other things wanted them.
Hope that answers your question.
--
bill davidsen <[email protected]>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
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.
Thanks for all you comments! They helped a lot.
The meaning for some keycodes is still missing, though:
* KEY_ARCHIVE, KEY_FILE, KEY_DIRECTORY - What's the difference here?
* KEY_DIGITS
* KEY_ISO - somehow related to KEY_KATAKANAHIRAGANA ??? (mapped to same
scancode in rawmode emulation)
* KEY_MODE
* KEY_QUESTION - what's the difference to KEY_INFO and KEY_SEARCH?
* KEY_SCREEN - switch between 4:3 and 16:9 ???
> 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.
Thanks again
Florian Festi