1 diff -up kbd-2.3.0/docs/man/man1/showkey.1.orig kbd-2.3.0/docs/man/man1/showkey.1
2 --- kbd-2.3.0/docs/man/man1/showkey.1.orig 2020-07-08 19:25:47.000000000 +0200
3 +++ kbd-2.3.0/docs/man/man1/showkey.1 2020-07-16 08:56:15.970254183 +0200
4 @@ -84,6 +84,19 @@ corresponds to what the keyboard hardwar
5 to know the scan codes sent by various keys it is better to boot a
6 2.4 kernel. Since 2.6.9 there also is the boot option atkbd.softraw=0
7 that tells the 2.6 kernel to return the actual scan codes.
10 +The raw scan codes are available only on AT and PS/2 keyboards,
11 +and even then they are disabled unless the
13 +kernel parameter is used.
14 +When the raw scan codes are not available, the kernel uses a fixed built-in
15 +table to produce scan codes from keycodes. Thus,
17 +can affect the output of
19 +in scan code dump mode.
24 diff -up kbd-2.3.0/docs/man/man8/setkeycodes.8.orig kbd-2.3.0/docs/man/man8/setkeycodes.8
25 --- kbd-2.3.0/docs/man/man8/setkeycodes.8.orig 2020-07-08 19:35:35.000000000 +0200
26 +++ kbd-2.3.0/docs/man/man8/setkeycodes.8 2020-07-16 08:57:52.293900997 +0200
27 @@ -42,6 +42,10 @@ the command
28 will assign the keycode 112 to it, and then
30 can be used to define the function of this key.
32 +USB keyboards have standardized keycodes and
34 +doesn't affect them at all.
36 Some older kernels might hardwire a low scancode range to the
37 equivalent keycodes; setkeycodes will fail when you try to remap
38 @@ -60,6 +64,14 @@ None.
40 The keycodes of X have nothing to do with those of Linux.
41 Unusual keys can be made visible under Linux, but not under X.
44 +affects only the "first" input device
45 +that has modifiable scancode-to-keycode mapping.
46 +If there is more than one such device,
48 +cannot change the mapping of other devices than the "first" one.