From: ryutaroh@it.ss.titech.ac.jp
To: vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cannot input bar with JP106 keyboards
Date: Sat, 20 Dec 2003 18:52:44 +0900 (JST) [thread overview]
Message-ID: <20031220.185244.71103628.ryutaroh@it.ss.titech.ac.jp> (raw)
In-Reply-To: <20031220093532.GB6017@ucw.cz>
From: Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [PATCH] cannot input bar with JP106 keyboards
Date: Sat, 20 Dec 2003 10:35:32 +0100
> > By the way, the bar key on JP 106 keyboard is actually the backslash
> > key and bar is equal to shift-backslash on JP 106. But there is
> > another backslash key (scancode 0x73) and input of backslash is not a
> > problem.
>
> Keycode 183 is correct for the japanese backslash key. 2.4 didn't
> differentiate, 2.6 does. You just need to update your keymap.
2.4 kernel does differentiate two backslash key on JP 106 keyboard.
When I press lower-right backslash (scancode 0x73), I get keycode
89 on both Linux 2.4 and 2.6.
When I press upper-right backslash (scancode 0x7d), whose key top is
Japanese yen and bar, I get keycode 124 on Linux 2.4 but 183 on Linux
2.6.
Is the change of keycode of upper-right backslash a new feature of
Linux 2.6? What is the advantage of this new feature?
The following is from /usr/share/keymaps/i386/qwerty/jp106.kmap in
Debian:
keycode 89 = backslash underscore
control keycode 89 = Control_backslash
keycode 124 = backslash bar
control keycode 124 = Control_backslash
Ryutaroh Matsumoto
next prev parent reply other threads:[~2003-12-20 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 12:24 ryutaroh
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 [this message]
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=20031220.185244.71103628.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®