[kbd] [PATCH 2/2] Update setkeycodes manpage information about hardwired keycodes

[Michael Schutte <michi@uiae.at>]

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