From: Vojtech Pavlik <vojtech@suse.cz>
To: ryutaroh@it.ss.titech.ac.jp
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cannot input bar with JP106 keyboards
Date: Sat, 20 Dec 2003 10:35:32 +0100 [thread overview]
Message-ID: <20031220093532.GB6017@ucw.cz> (raw)
In-Reply-To: <20031220.183049.74735752.ryutaroh@it.ss.titech.ac.jp>
On Sat, Dec 20, 2003 at 06:30:49PM +0900, ryutaroh@it.ss.titech.ac.jp wrote:
> Thank you for your very quick reply.
>
> From: Vojtech Pavlik <vojtech@suse.cz>
> > Can you try the attached patch?
>
> The problem was not solved.
>
> When I pressed the bar key on JP 106 keyboard, the output of "showkey
> -k" is
>
> keycode 0 press
> keycode 1 release
> keycode 54 release
> keycode 0 release
> keycode 1 release
> keycode 54 release
>
> The scancode does not change. Before applying your patch to the
> original kernel, the output was
>
> keycode 0 press
> keycode 1 release
> keycode 55 release
> keycode 0 release
> keycode 1 release
> keycode 55 release
>
> which corresponds to keycode 183 (= 1*128 + 55).
>
> The output of Linux 2.4.23 was
>
> keycode 124 press
> keycode 124 release
>
>
> 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.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2003-12-20 9:35 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 [this message]
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=20031220093532.GB6017@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ryutaroh@it.ss.titech.ac.jp \
/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®