From: John Hughes <john@calvaedi.com>
To: linux-kernel@vger.kernel.org
Cc: Mattia Dongili <malattia@linux.it>, Stelian Pop <stelian@popies.net>
Subject: Bug: changing keycodes generated by sony-laptop doesn't work
Date: Sun, 16 Oct 2011 14:30:17 +0200 [thread overview]
Message-ID: <4E9ACE59.2000003@calvaedi.com> (raw)
In-Reply-To: <4E9ABBF6.3000504@calvaedi.com>
Something about the way sony-laptop sends scancodes and keycodes to the
input subsystem doesn't work.
1. using the /lib/udev/keymap utility to show the scancodes and keycodes
generated by the Sony Vaio keys device shows them out-of sync:
start keymap, press EJECT (mapped by sony-laptop to FN_E) twice, then AV
MODE (mapped to PROG1) twice:
# /lib/udev/keymap -i input/event5
Press ESC to finish
scan code: 0x00 key code: fn_e
scan code: 0x1B key code: fn_e
scan code: 0x1B key code: prog1
scan code: 0x20 key code: prog1
^C
Notice that each time a key is pressed the scancode shown is the
scancode of the previous key.
2. Changing the keycode for a given scancode has no effect:
# /lib/udev/keymap input/event5 0x1B ejectcd
setting scancode 0x1B to key code 161
# /lib/udev/keymap -i input/event5
Press ESC to finish
scan code: 0x00 key code: fn_e
scan code: 0x1B key code: fn_e
^C
next prev parent reply other threads:[~2011-10-16 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 11:11 sony-laptop driver: Volume keys on Sony Vaio TX3 don't work John Hughes
2011-10-16 12:30 ` John Hughes [this message]
2011-10-16 13:30 ` Bug: changing keycodes generated by sony-laptop doesn't work John Hughes
2011-10-17 9:08 ` John Hughes
2011-10-16 13:27 ` sony-laptop driver: Volume keys on Sony Vaio TX3 don't work John Hughes
2011-10-16 17:45 ` John Hughes
2011-10-16 18:20 ` Valdis.Kletnieks
2011-10-16 21:38 ` Mattia Dongili
2011-10-16 21:50 ` Valdis.Kletnieks
2011-10-16 23:17 ` John Hughes
2011-10-17 21:43 ` Mattia Dongili
2011-10-18 9:02 ` John Hughes
2011-10-17 21:45 ` Mattia Dongili
2011-10-18 9:07 ` John Hughes
2011-10-19 22:01 ` John Hughes
2011-10-16 23:13 ` John Hughes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9ACE59.2000003@calvaedi.com \
--to=john@calvaedi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malattia@linux.it \
--cc=stelian@popies.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.