Difference between revisions of "Map scancodes to keycodes"

From ArchWiki
Jump to: navigation, search
(updated dead HAL Keymap Quirks url to new location)
Line 1: Line 1:
 
[[Category:General (English)]][[Category:Input devices (English)]][[Category:Other desktop user's resources (English)]]
 
[[Category:General (English)]][[Category:Input devices (English)]][[Category:Other desktop user's resources (English)]]
=Introduction=
+
{{stub}}
 
scancodes are the lowest identification numbers for a key, they are from the kernel and are not used by applications that's why we have to map them to keycodes which correspond to functions.
 
scancodes are the lowest identification numbers for a key, they are from the kernel and are not used by applications that's why we have to map them to keycodes which correspond to functions.
  

Revision as of 01:55, 13 February 2010

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Map scancodes to keycodes#)

scancodes are the lowest identification numbers for a key, they are from the kernel and are not used by applications that's why we have to map them to keycodes which correspond to functions.

See Extra Keyboard Keys for more informations.

There are two ways of mapping scancodes to keycodes:

  • Using HAL
  • Using the kernel tool setkeycodes

The preferred one is to use HAL because it uses hardware information (which is a quite reliable source) to choose the keyboard model in a database. It means that if your keyboard model as been defined in the database your keys are recognized "out of the box" and can be seen by Xorg. That's why by expanding the database you are helping the linux community and maybe someday we won't have to care about scancodes.

Using HAL

See HAL Keymap Quirks.

Using the kernel tool setkeycodes

See the detailed article: setkeycodes.