From: ryutaroh@it.ss.titech.ac.jp
To: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: [PATCH] cannot input bar with JP106 keyboards
Date: Fri, 19 Dec 2003 21:24:56 +0900 (JST) [thread overview]
Message-ID: <20031219.212456.74735601.ryutaroh@it.ss.titech.ac.jp> (raw)
Hello,
I found a problem in drivers/input/keyboard/atkbd.c in Linux 2.6.0.
We cannot input | (bar) with the JP 106 keyboards (the standard Japanese
keyboards). This is because the scancode 0x7d (125) is translated to
the keycode 0xb7 (183). The scancode 0x7d corresponds to | (bar) on
the JP 106 keyboard. In Linux 2.4.23, the scancode 0x7d (125) is
translated to the keycode 0x7c (124). Scancodes and keycodes can be
displayed by showkey(1).
The following patch makes the translation rule the same as that in
Linux 2.4.23. We also have to update drivers/char/keyboard.c in order
to get correct scancode.
If you send comments, please send them to
ryutaroh@it.ss.titech.ac.jp. I don't subscribe LKML.
Best regards,
Ryutaroh Matsumoto, Ph.D., Research Associate
Department of Communications and Integrated Systems
Tokyo Institute of Technology, 152-8552 Japan
Web page: http://www.rmatsumoto.org/research.html
--- linux-2.6.0/drivers/input/keyboard/atkbd.c.org 2003-12-18 11:59:19.000000000 +0900
+++ linux-2.6.0/drivers/input/keyboard/atkbd.c 2003-12-19 15:36:52.000000000 +0900
@@ -54,7 +54,7 @@
91, 49, 48, 35, 34, 21, 7, 0, 0, 0, 50, 36, 22, 8, 9, 0,
0, 51, 37, 23, 24, 11, 10, 0, 0, 52, 53, 38, 39, 25, 12, 0,
122, 89, 40,120, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 0,
- 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
+ 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,124, 75, 71,121, 0,123,
82, 83, 80, 76, 77, 72, 1, 69, 87, 78, 81, 74, 55, 73, 70, 99,
0, 0, 0, 65, 99, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
--- linux-2.6.0/drivers/char/keyboard.c.org 2003-12-18 11:58:46.000000000 +0900
+++ linux-2.6.0/drivers/char/keyboard.c 2003-12-19 17:09:07.000000000 +0900
@@ -943,7 +943,7 @@
64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79,
80, 81, 82, 83, 43, 85, 86, 87, 88,115,119,120,121,375,123, 90,
284,285,309,298,312, 91,327,328,329,331,333,335,336,337,338,339,
- 367,288,302,304,350, 92,334,512,116,377,109,111,373,347,348,349,
+ 367,288,302,304,350, 92,334,512,116,377,109,111,125,347,348,349,
360, 93, 94, 95, 98,376,100,101,321,316,354,286,289,102,351,355,
103,104,105,275,287,279,306,106,274,107,294,364,358,363,362,361,
291,108,381,281,290,272,292,305,280, 99,112,257,258,359,270,114,
next reply other threads:[~2003-12-19 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 12:24 ryutaroh [this message]
2003-12-19 12:36 ` Vojtech Pavlik
2003-12-20 9:30 ` ryutaroh
2003-12-20 9:35 ` Vojtech Pavlik
2003-12-20 9:52 ` ryutaroh
2003-12-20 12:46 ` John Bradford
2003-12-21 11:23 ` Jamie Lokier
2003-12-21 14:36 ` John Bradford
2003-12-22 1:59 ` ryutaroh
[not found] ` <fa.kfih9j0.q4e8bi@ifi.uio.no>
2003-12-23 20:58 ` Junio C Hamano
2003-12-24 1:28 ` ryutaroh
2003-12-21 11:07 Norman Diamond
2003-12-21 14:23 ` John Bradford
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=20031219.212456.74735601.ryutaroh@it.ss.titech.ac.jp \
--to=ryutaroh@it.ss.titech.ac.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®