From: Vojtech Pavlik <vojtech@suse.cz>
To: Go Taniguchi <go@turbolinux.co.jp>
Cc: vojtech@suse.cz, Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1-rc1 with JP106 keyboard
Date: Fri, 2 Jan 2004 14:20:31 +0100 [thread overview]
Message-ID: <20040102132031.GC395@ucw.cz> (raw)
In-Reply-To: <3FF5059F.4010007@turbolinux.co.jp>
On Fri, Jan 02, 2004 at 02:46:07PM +0900, Go Taniguchi wrote:
> And more....
>
> mae-kouho/henkan (scancode 0x79) 92 -> 184
> mu-henkan (scancode 0x7b) 94 -> 185
>
> - 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
> + 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
> ^ 0x79 ^ 0x7b
> These are input method control keys.
Again, this is per (microsoft [*]) specification. These keys should,
however, give the very same scancodes to X as they did on 2.4.
[*] I used this specification, because that's what the keyboard
manufacturers seem to follow recently.
> Go Taniguchi wrote:
> >>
> >>Vojtech Pavlik:
> >> o Fixes for keyboard 2.4 compatibility
> >>
> >
> >Hi,
> >2.6.1-rc1 with JP106 keybord. keycode was changed....
> > 2.6.0 -> 2.6.1-rc1
> >lower-right backslash (scancode 0x73) 89 -> 181
> >upper-right backslash (scancode 0x7d) 183 -> 182
> >
> >at atkbd_set2_keycode in drivers/input/keyboard/atkbd.c
> >
> >- 122, 89, 40,120, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 0,
> >+ 0,181, 40, 0, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0,194,
> > ^ scancode 0x73
> >
> >- 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
> >+ 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
> > ^ scancode 0x7d
> >Is this correct?
> >2.6.0 is OK, but 2.6.1-rc1 does not get [|/_] keys.
>
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-01-02 13:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 8:36 2.6.1-rc1 Linus Torvalds
2003-12-31 8:47 ` 2.6.1-rc1 Mike Fedyk
2003-12-31 10:05 ` 2.6.1-rc1 Tomas Szepe
2003-12-31 12:12 ` 2.6.1-rc1 Jeff Garzik
2003-12-31 15:00 ` 2.6.1-rc1 [resend] Paolo Ornati
2003-12-31 15:06 ` William Lee Irwin III
2003-12-31 15:19 ` Paolo Ornati
2003-12-31 15:20 ` William Lee Irwin III
2003-12-31 15:45 ` Paolo Ornati
2003-12-31 16:31 ` Ed Sweetman
2003-12-31 18:03 ` Paolo Ornati
2004-01-01 9:12 ` 2.6.1-rc1 Andreas Unterkircher
2004-01-01 18:12 ` 2.6.1-rc1 Paolo Ornati
2004-01-02 4:51 ` 2.6.1-rc1 with JP106 keyboard Go Taniguchi
2004-01-02 5:46 ` Go Taniguchi
2004-01-02 13:20 ` Vojtech Pavlik [this message]
2004-01-02 13:17 ` Vojtech Pavlik
2004-01-02 19:01 ` Go Taniguchi
2004-01-02 20:10 ` Vojtech Pavlik
2004-01-03 5:54 ` Go Taniguchi
2004-01-06 18:33 ` 2.6.1-rc1: SCSI: `TIMEOUT' redefined Adrian Bunk
2004-01-06 22:40 ` [PATCH] " Patrick Mansfield
2004-01-06 22:40 ` Andrew Morton
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=20040102132031.GC395@ucw.cz \
--to=vojtech@suse.cz \
--cc=go@turbolinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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