kbd/kbd-1.12-keycodes-man.patch
Miloslav Trmac dc56124efe - Document that setkeycodes doesn't affect USB keyboards and that the
kernel doesn't provide the raw scan codes by default Resolves: #211803
2006-12-07 17:12:31 +00:00

50 lines
1.5 KiB
Diff

--- kbd-1.12/man/man1/showkey.1.keycodes-man 2006-12-07 17:37:00.000000000 +0100
+++ kbd-1.12/man/man1/showkey.1 2006-12-07 18:03:08.000000000 +0100
@@ -66,6 +66,19 @@
Starts
.B showkey
in `ascii' dump mode.
+
+.SH NOTES
+The raw scan codes are available only on AT and PS/2 keyboards,
+and even then they are disabled unless the
+.B atkbd.softraw=0
+kernel parameter is used.
+When the raw scan codes are not available, the kernel uses a fixed built-in
+table to produce scan codes from keycodes. Thus,
+.BR setkeycodes (8)
+can affect the output of
+.B showkey
+in scan code dump mode.
+
.SH "SEE ALSO"
.BR loadkeys (1),
.BR dumpkeys (1),
--- kbd-1.12/man/man8/setkeycodes.8.keycodes-man 2006-12-07 18:00:40.000000000 +0100
+++ kbd-1.12/man/man8/setkeycodes.8 2006-12-07 18:05:24.000000000 +0100
@@ -40,11 +40,24 @@
.RE
will assign the keycode 112 to it, and then loadkeys(1) can be used
to define the function of this key.
+
+USB keyboards have standardized keycodes and
+.B setkeycodes
+doesn't affect them at all.
+
.SH OPTIONS
None.
.SH 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.
+
+.B setkeycodes
+affects only the "first" input device
+that has modifiable scancode-to-keycode mapping.
+If there is more than one such device,
+.B setkeycodes
+cannot change the mapping of other devices than the "first" one.
+
.SH "SEE ALSO"
.I "dumpkeys (1), loadkeys (1), showkey (1), getkeycodes (8)"