|author||John Hughes <firstname.lastname@example.org>||2011-11-16 19:51:57 +0100|
|committer||Matthew Garrett <email@example.com>||2012-03-20 12:02:03 -0400|
to fix scancodes returned by sony-laptop driver
Fix scancodes returned by driver to match scancodes used to remap keys. (Before the patch FN/E returned scancode 0x1B, but to remap scancode 0x14 had to be used). The scancodes returned by the sony-laptop driver for function keys did not match the scancodes used to remap keys. Also, since the scancode was sent to the input subsystem after the mapped keysym the /lib/udev/keymap utility was confused about which scancode to report for which keysym. This patch fixes the driver so the correct scancode is shown for each key. It also adds to the documentation a description of where to find the scancodes. Signed-off-by: John Hughes <firstname.lastname@example.org> Acked-by: Dmitry Torokhov <email@example.com> Signed-off-by: Matthew Garrett <firstname.lastname@example.org>
Diffstat (limited to 'Documentation/laptops')
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/laptops/sony-laptop.txt b/Documentation/laptops/sony-laptop.txt
index 2bd4e82e5d9f..0d5ac7f5287e 100644
@@ -17,6 +17,11 @@ subsystem. See the logs of acpid or /proc/acpi/event and
devices are created by the driver. Additionally, loading the driver with the
debug option will report all events in the kernel log.
+The "scancodes" passed to the input system (that can be remapped with udev)
+are indexes to the table "sony_laptop_input_keycode_map" in the sony-laptop.c
+module. For example the "FN/E" key combination (EJECTCD on some models)
+generates the scancode 20 (0x14).
If your laptop model supports it, you will find sysfs files in the