public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: vojtech@suse.cz (Vojtech Pavlik)
Cc: linux-kernel@vger.kernel.org
Subject: Set2 scancodes for Japanese keyboard
Date: Sat, 25 Jan 2003 17:20:49 +0000 (GMT)	[thread overview]
Message-ID: <200301251720.h0PHKnL5000974@darkstar.example.net> (raw)
In-Reply-To: <20030125141501.A5266@ucw.cz> from "Vojtech Pavlik" at Jan 25, 2003 02:15:01 PM

> > > If you can provide the complete key -> scancode table for that keyboard,
> > > or at least differences against standard US keyboard for both set 2 and
> > > set 3, that'd be great.

Here are the set 2 ones, I've missed out most of the letter and number
keys, because they all followed the obvious numerical sequence.  I'll
send the set 3 ones separately, (when I've typed them in :-) ).

Key
Keycode
Make scancode
Break scancode

Escape
1
0x01
0x81

F1
59
0x3b
0xbb

F10
68
0x44
0xc4

F11
87
0x57
0xd7

F12
88
0x58
0xd8

Printscreen?, (marked 'page', and something I can't read).
99
0xe0 0x2a 0xe0 0x37
0xe0 0xb7 0xe0 0xaa

Sys Rq, (alt and key above)
84
0x54
0xd4

Scroll lock
70
0x46
0xc6

Numlock, (shift scroll lock)
69
0x45
0xc5

Pause
119
0xe1 0x1d 0x45
0xe1 0x9d 0xc5

Break
101
0xe0 0x46
0xe0 0xc6

Hankaku/Zenkaku
None
0xff
none

1
2
0x02
0x83

0
11
0x0b
0x8b

-
12
0x0c
0x8c

shift -
13
0xb6 0x0d
0x8d 0x36

^
42,7
0x2a 0x07
0x8  0xaa

shift ^
none
0xff
none

yen
none
0xff
none

shift yen ( | )
43
0x2b
0xab

backspace
14
0x0e
0x8e

tab
15
0x0f
0x8f

q
16
0x10
0x90

p
25
0x19
0x99

@
42,3
0x2a 0x03
0x83 0xaa

shift @
release 54, 41, release 41, 54
0xb6 0x29
0xa9 0x36

[
26
0x1a
0x9a

enter
28
0x1c
0x9c

caps lock
58
0x3a
0xba

a
30
0x1e
0xae

l
38
0x26
0xa6

;
39
0x27
0xa7

shift ; ( + )
13
0x0d
0x8d

:
42 39
0x2a 0x27
0xa7 0xaa

shift : ( * )
9
0x09
0x89

]
27
0x1b
0x9b

left shift 42
0x2a
0xaa

z
44
0x2c
0xad

m
50
0x32
0xb2

,
51
0x33
0xb3


  reply	other threads:[~2003-01-25 17:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  3:14 [PATCH 2.5.59] support japanese JP106 keyboard on new console Hiroshi Miura
2003-01-24  5:57 ` Vojtech Pavlik
2003-01-24 17:03   ` Osamu Tomita
2003-01-25 10:33     ` Vojtech Pavlik
2003-01-25 10:51       ` John Bradford
2003-01-25 11:01         ` Vojtech Pavlik
2003-01-25 13:10           ` John Bradford
2003-01-25 13:15             ` Vojtech Pavlik
2003-01-25 17:20               ` John Bradford [this message]
2003-01-25 17:28           ` [Corrected] Set2 scancodes for Japanese keyboard John Bradford
2003-01-25 17:30             ` Vojtech Pavlik
2003-01-25 17:37               ` John Bradford
2003-01-25 17:40                 ` Vojtech Pavlik
2003-01-25 17:46                   ` John Bradford
2003-01-25 19:48                   ` Andries Brouwer
2003-01-25 19:54                     ` Vojtech Pavlik
2003-01-27 16:35                   ` Set3 " John Bradford
2003-01-25 15:29       ` [PATCH 2.5.59] support japanese JP106 keyboard on new console Osamu Tomita
2003-01-25 15:36         ` Vojtech Pavlik
2003-01-24 17:17 ` Osamu Tomita
2003-02-01  1:54   ` Hiroshi Miura
2003-02-02  8:23     ` Vojtech Pavlik
2003-02-02 10:38       ` John Bradford
2003-02-02 10:47         ` Vojtech Pavlik
2003-02-05  3:36       ` Hiroshi Miura

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=200301251720.h0PHKnL5000974@darkstar.example.net \
    --to=john@grabjohn.com \
    --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