|
 |
2eee48 |
diff -up kbd-2.0.4/docs/man/man1/showkey.1.orig kbd-2.0.4/docs/man/man1/showkey.1
|
|
|
2eee48 |
--- kbd-2.0.4/docs/man/man1/showkey.1.orig 2016-10-31 16:56:02.000000000 +0100
|
|
|
2eee48 |
+++ kbd-2.0.4/docs/man/man1/showkey.1 2017-01-11 10:45:03.763312393 +0100
|
|
|
2eee48 |
@@ -84,6 +84,19 @@ corresponds to what the keyboard hardwar
|
|
|
2eee48 |
to know the scan codes sent by various keys it is better to boot a
|
|
|
2eee48 |
2.4 kernel. Since 2.6.9 there also is the boot option atkbd.softraw=0
|
|
|
2eee48 |
that tells the 2.6 kernel to return the actual scan codes.
|
|
|
2eee48 |
+
|
|
|
2eee48 |
+.SH NOTES
|
|
|
2eee48 |
+The raw scan codes are available only on AT and PS/2 keyboards,
|
|
|
2eee48 |
+and even then they are disabled unless the
|
|
|
2eee48 |
+.B atkbd.softraw=0
|
|
|
2eee48 |
+kernel parameter is used.
|
|
|
2eee48 |
+When the raw scan codes are not available, the kernel uses a fixed built-in
|
|
|
2eee48 |
+table to produce scan codes from keycodes. Thus,
|
|
|
2eee48 |
+.BR setkeycodes (8)
|
|
|
2eee48 |
+can affect the output of
|
|
|
2eee48 |
+.B showkey
|
|
|
2eee48 |
+in scan code dump mode.
|
|
|
2eee48 |
+
|
|
|
2eee48 |
.SH "SEE ALSO"
|
|
|
2eee48 |
.BR loadkeys (1),
|
|
|
2eee48 |
.BR dumpkeys (1),
|
|
|
2eee48 |
diff -up kbd-2.0.4/docs/man/man8/setkeycodes.8.orig kbd-2.0.4/docs/man/man8/setkeycodes.8
|
|
|
2eee48 |
--- kbd-2.0.4/docs/man/man8/setkeycodes.8.orig 2016-10-31 16:56:02.000000000 +0100
|
|
|
2eee48 |
+++ kbd-2.0.4/docs/man/man8/setkeycodes.8 2017-01-11 10:45:03.763312393 +0100
|
|
|
2eee48 |
@@ -38,6 +38,10 @@ to showkey(1), the command
|
|
|
2eee48 |
.RE
|
|
|
2eee48 |
will assign the keycode 112 to it, and then loadkeys(1) can be used
|
|
|
2eee48 |
to define the function of this key.
|
|
|
2eee48 |
+
|
|
|
2eee48 |
+USB keyboards have standardized keycodes and
|
|
|
2eee48 |
+.B setkeycodes
|
|
|
2eee48 |
+doesn't affect them at all.
|
|
|
2eee48 |
.LP
|
|
|
2eee48 |
Some older kernels might hardwire a low scancode range to the
|
|
|
2eee48 |
equivalent keycodes; setkeycodes will fail when you try to remap
|
|
|
2eee48 |
@@ -56,6 +60,14 @@ None.
|
|
|
2eee48 |
.SH BUGS
|
|
|
2eee48 |
The keycodes of X have nothing to do with those of Linux.
|
|
|
2eee48 |
Unusual keys can be made visible under Linux, but not under X.
|
|
|
2eee48 |
+
|
|
|
2eee48 |
+.B setkeycodes
|
|
|
2eee48 |
+affects only the "first" input device
|
|
|
2eee48 |
+that has modifiable scancode-to-keycode mapping.
|
|
|
2eee48 |
+If there is more than one such device,
|
|
|
2eee48 |
+.B setkeycodes
|
|
|
2eee48 |
+cannot change the mapping of other devices than the "first" one.
|
|
|
2eee48 |
+
|
|
|
2eee48 |
.SH "SEE ALSO"
|
|
|
2eee48 |
.I "dumpkeys (1), loadkeys (1), showkey (1), getkeycodes (8)"
|
|
|
2eee48 |
|