ir-keytable(1) [centos man page]

IR-KEYTABLE(1)							   User Commands						    IR-KEYTABLE(1)

NAME

       ir-keytable - a swiss-knife tool to handle Remote Controllers.

SYNOPSIS

       ir-keytable [OPTION]... --device [/dev/input/event* device]
       ir-keytable [OPTION]... --sysdev [ir class (f. ex. rc0)]
       ir-keytable [OPTION]... [for using the rc0 sysdev]

DESCRIPTION

       ir-keytable  is a tool that lists the Remote Controller devices, allows one to get/set IR keycode/scancode tables, test events generated by
       IR, and to adjust other Remote Controller options.

       Note: You need to have read permissions on /dev/input for most of the options to work.

OPTIONS

       -a, --auto-load=CFGFILE
	      Auto-load a table, based on a configuration file. Only works with sysdev.

       -c, --clear
	      clears the old table

       -d, --device=DEV
	      ir device to control

       -D, --delay=DELAY
	      Sets the delay before repeating a keystroke

       -k, --set-key=SCANKEY
	      Change scan/key pairs

       -p, --protocol=PROTOCOL
	      Protocol to enable (the other ones will be disabled). To enable more than one, use the option more than one time

       -P, --period=PERIOD
	      Sets the period to repeat a keystroke

       -r, --read
	      reads the current scancode/keycode table

       -s, --sysdev=SYSDEV
	      ir class device to control

       -t, --test
	      test if IR is generating events

       -v, --verbose
	      enables debug messages

       -w, --write=TABLE
	      write (adds) the scancodes to the device scancode/keycode table from the specified TABLE file

       -?, --help
	      Prints the help message

       --usage
	      Give a short usage message

       -V, --version
	      print the v4l2-utils version

       Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. Options can be combined
       together.

   The options arguments are:
       DEV    the /dev/input/event* device to control

       SYSDEV the ir class as found at /sys/class/rc

       TABLE  a file wit a set of scancode=keycode value pairs

       SCANKEY
	      a set of scancode1=keycode1,scancode2=keycode2.. value pairs

       PROTOCOL
	      protocol name (nec, rc-5, rc-6, other) to be enabled

       DELAY  Delay before repeating a keystroke

       PERIOD Period to repeat a keystroke

       CFGFILE
	      configuration file that associates a driver/table name with a keymap file

EXIT STATUS

       On success, it returns 0. Otherwise, it will return the error code.

EXAMPLES

       To list all connected Remote Controller devices:
	    ir-keytable

       To clean the keycode table and use a newer one:
	    ir-keytable -c -w /etc/rc_keymaps/nec_terratec_cinergy_xs

       To append more codes to the existing table:
	    ir-keytable -w /etc/rc_keymaps/nec_terratec_cinergy_xs

       To read the current keytable, on the second remote controller:	   ir-keytable -s rc1 -r

BUGS

       Report bugs to Mauro Carvalho Chehab <mchehab@redhat.com>

COPYRIGHT

       Copyright (c) 2010-2011 by Mauro Carvalho Chehab <mchehab@redhat.com>.

       License GPLv2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>.
       This is free software: you are free to change and redistribute it.  There is NO WARRANTY, to the extent permitted by law.

v4l-utils							   January 2011 						    IR-KEYTABLE(1)

Check Out this Related Man Page

SETKEYCODES(8)							 Keyboard Support						    SETKEYCODES(8)

NAME

       setkeycodes - load kernel scancode-to-keycode mapping table entries

SYNOPSIS

       setkeycodes scancode keycode ...

DESCRIPTION

       The  setkeycodes  command  reads  its arguments two at a time, each pair of arguments consisting of a scancode (given in hexadecimal) and a
       keycode (given in decimal). For each such pair, it tells the kernel keyboard driver to map the specified scancode to the specified keycode.

       This command is useful only for people with slightly unusual keyboards, that have a few keys which produce scancodes that the  kernel  does
       not recognize.

THEORY

       The  usual  PC  keyboard  produces  a  series  of  scancodes  for  each	key press and key release. (Scancodes are shown by showkey -s, see
       showkey(1).)  The kernel parses this stream of scancodes, and converts it to a stream of keycodes (key  press/release  events).	 (Keycodes
       are  shown  by showkey.)  Apart from a few scancodes with special meaning, and apart from the sequence produced by the Pause key, and apart
       from shiftstate related scancodes, and apart from the key up/down bit, the stream of scancodes consists of unescaped scancodes xx (7  bits)
       and  escaped  scancodes	e0  xx	(8+7  bits).   To these scancodes or scancode pairs, a corresponding keycode can be assigned (in the range
       1-127).	For example, if you have a Macro key that produces e0 6f according to showkey(1), the command
	      setkeycodes e06f 112
       will assign the keycode 112 to it, and then loadkeys(1) can be used to define the function of this key.

       Some older kernels might hardwire a low scancode range to the equivalent keycodes; setkeycodes will fail when you try to remap these.

2.6 KERNELS
       In 2.6 kernels key codes lie in the range 1-255, instead of 1-127.  (It might be best to confine oneself to the range 1-239.)

       In 2.6 kernels raw mode, or scancode mode, is not very raw at all.  The code returned by showkey -s will change after use  of  setkeycodes.
       A kernel bug. See also showkey(1).

OPTIONS

       None.

BUGS

       The keycodes of X have nothing to do with those of Linux.  Unusual keys can be made visible under Linux, but not under X.

SEE ALSO

       dumpkeys (1), loadkeys (1), showkey (1), getkeycodes (8)

Local								    8 Nov 1994							    SETKEYCODES(8)

Linux and UNIX Man Pages

ir-keytable(1) [centos man page]

Check Out this Related Man Page