linux-kernel - Re: Meaning of keycodes unclear

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 5 Dec 2006 12:15:41 +0100
From:	Pavel Machek <pavel@....cz>
To:	Florian Festi <florian@...ti.info>, vojtech@...e.cz
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Meaning of keycodes unclear

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/