From: Michael Schutte <michi@uiae.at> To: kbd@lists.altlinux.org Subject: [kbd] [PATCH 2/2] Update setkeycodes manpage information about hardwired keycodes Date: Thu, 11 Jun 2009 20:38:25 +0200 Message-ID: <1244745505-29716-1-git-send-email-michi@uiae.at> (raw) At least newer kernels don’t use hardwired scancode-keycode mappings. Rephrase the affected part of the setkeycodes(8) manpage. Signed-off-by: Michael Schutte <michi@uiae.at> --- man/man8/setkeycodes.8 | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/man/man8/setkeycodes.8 b/man/man8/setkeycodes.8 index 69dee20..8cad162 100644 --- a/man/man8/setkeycodes.8 +++ b/man/man8/setkeycodes.8 @@ -29,10 +29,8 @@ 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). -It is hardwired in the current kernel that in the range 1-88 -(0x01-0x58) keycode equals scancode. For the remaining scancodes -(0x59-0x7f) or scancode pairs (0xe0 0x00 - 0xe0 0x7f) a -corresponding keycode can be assigned (in the range 1-127). +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 .RS @@ -40,6 +38,10 @@ to showkey(1), the command .RE will assign the keycode 112 to it, and then loadkeys(1) can be used to define the function of this key. +.LP +Some older kernels might hardwire a low scancode range to the +equivalent keycodes; setkeycodes will fail when you try to remap +these. .SH "2.6 KERNELS" In 2.6 kernels key codes lie in the range 1-255, instead of 1-127. -- 1.6.3.1
next reply other threads:[~2009-06-11 18:38 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-11 18:38 Michael Schutte [this message] 2009-06-13 11:21 ` Alexey Gladkov
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=1244745505-29716-1-git-send-email-michi@uiae.at \ --to=michi@uiae.at \ --cc=kbd@lists.altlinux.org \ /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
Linux console tools development discussion This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/kbd/0 kbd/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kbd kbd/ http://lore.altlinux.org/kbd \ kbd@lists.altlinux.org kbd@lists.altlinux.ru kbd@lists.altlinux.com public-inbox-index kbd Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.kbd AGPL code for this site: git clone https://public-inbox.org/public-inbox.git