support japanese JP106 keyboard on new console.

support japanese JP106 keyboard on new console.

Post by Vojtech Pavli » Sun, 26 Jan 2003 19:50:05





> > > Some got missed off the first time:

> > What kernel this is tested with? What method used? These don't look like
> > Set2 codes AT ALL.

> The kernel is 2.4.20.  The keycode is the output from showkey, and the
> make and break codes are the output from showkey -s.

> Should I have used I8042_DEBUG_IO instead?  :-/

With 2.5, yes, that'd be much better. And yet better it'd be if you'd
have used the "i8042_direct=1" kernel option, and for set3 the
"atkbd_set=3" option.

I'm sorry to tell you after you wrote it all down, but these are set1
scancodes you see.

--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by John Bradfor » Sun, 26 Jan 2003 19:50:08


Quote:> > > What kernel this is tested with? What method used? These don't look like
> > > Set2 codes AT ALL.

> > The kernel is 2.4.20.  The keycode is the output from showkey, and the
> > make and break codes are the output from showkey -s.

> > Should I have used I8042_DEBUG_IO instead?  :-/

> With 2.5, yes, that'd be much better. And yet better it'd be if you'd
> have used the "i8042_direct=1" kernel option, and for set3 the
> "atkbd_set=3" option.

> I'm sorry to tell you after you wrote it all down, but these are set1
> scancodes you see.

I should have realised anyway - I remember now it translates
everything to set 1.

Oh dear, well, it might take a while - I packed my serial terminal
away yesterday, because a wire needs to be soldered on it :-), (which
explains why I was writing it all down :-) )

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by Andries Brouwe » Sun, 26 Jan 2003 21:50:09



> I'm sorry to tell you after you wrote it all down, but these are set1
> scancodes you see.

What about "translated set2" ?

So far I have not yet seen cases where the translation was nonstandard.
That is, for all keyboards I have looked at or received reports on
the table given in
        http://www.win.tue.nl/~aeb/linux/kbd/scancodes-4.html#kscancodes
described the conversion from set2 to set1.

So, given the translated set2 codes, also the original set2 codes are
known with high probability. (The translation is almost 1-1.)

Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by Vojtech Pavli » Sun, 26 Jan 2003 22:00:16



> > I'm sorry to tell you after you wrote it all down, but these are set1
> > scancodes you see.

> What about "translated set2" ?

Correct.

Quote:> So far I have not yet seen cases where the translation was nonstandard.
> That is, for all keyboards I have looked at or received reports on
> the table given in
>    http://www.win.tue.nl/~aeb/linux/kbd/scancodes-4.html#kscancodes
> described the conversion from set2 to set1.

> So, given the translated set2 codes, also the original set2 codes are
> known with high probability. (The translation is almost 1-1.)

Correct. Given set of not translated set2 codes, the translated set2
codes are created much easier, hence the not translated set2 codes offer
better value.

And, translated set3 just plain doesn't make sense.

--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by John Bradfor » Tue, 28 Jan 2003 18:40:13


> > > What kernel this is tested with? What method used? These don't look like
> > > Set2 codes AT ALL.

> > The kernel is 2.4.20.  The keycode is the output from showkey, and the
> > make and break codes are the output from showkey -s.

> > Should I have used I8042_DEBUG_IO instead?  :-/

> With 2.5, yes, that'd be much better. And yet better it'd be if you'd
> have used the "i8042_direct=1" kernel option, and for set3 the
> "atkbd_set=3" option.

> I'm sorry to tell you after you wrote it all down, but these are set1
> scancodes you see.

Here are the set 3 scancodes for my Japanese keyboard.

If the set 2 codes are still of interest, I can do those as well, but
set 3 seems to be a much more useful mode, because there is a direct
mapping of keys to scancodes, instead of the more complicated
similated shift key codes that set 2 produces.

ESC                             08 F0 08
F1                              07 F0 07
F2                              0F F0 0F
F3                              17 F0 17
F4                              1F F0 1F
F5                              27 F0 27
F6                              2F F0 2F
F7                              37 F0 37
F8                              3F F0 3F
F9                              47 F0 47
F10                             4F F0 4F
F11                             56 F0 56
F12                             5E F0 5E

HANKAKU/ZENKAKU                 0E F0 0E
1                               16 F0 16
2                               1E F0 1E
3                               26 F0 26
4                               25 F0 25
5                               2E F0 2E
6                               36 F0 36
7                               3D F0 3D
8                               3E F0 3E
9                               46 F0 46
0                               45 F0 45
-                               4E F0 4E
^                               55 F0 55
YEN                             13 F0 13
BACKSPACE                       66 F0 66

TAB                             0D F0 0D
Q                               15 F0 15
W                               1D F0 1D
E                               24 F0 24
R                               2D F0 2D
T                               2C F0 2C
Y                               35 F0 35
U                               3C F0 3C
I                               43 F0 43
O                               44 F0 44
P                               4D F0 4D
@                               54 F0 54
[                               5B F0 5B

A                               1C F0 1C
S                               1B F0 1B
D                               23 F0 23
F                               2B F0 2B
G                               34 F0 34
H                               33 F0 33
J                               3B F0 3B
K                               42 F0 42
L                               4B F0 4B
;                               4C F0 4C
:                               52 F0 52
]                               53 F0 53
ENTER                           5A F0 5A

LEFT SHIFT                      12 F0 12
Z                               1A F0 1A
X                               22 F0 22
C                               21 F0 21
V                               2A F0 2A
B                               32 F0 32
N                               31 F0 31
M                               3A F0 3A
,                               41 F0 41
.                               49 F0 49
/                               4A F0 4A
\                               5C F0 5C
RIGHT SHIFT                     59 F0 59

LEFT CONTROL                    11 F0 11
KANJI/KANAKANA                  19 F0 19
MUHENKAN                        85 F0 85
SPACE                           29 F0 29
ZENKOHO/HENKAN (JIKOHO)/ZENKOHO 86 F0 86
HIRAGANA                        87 F0 87
ZENMEN KI                       39 F0 39
RIGHT CONTROL                   58 F0 58

PAGE/SYSRQ                      57 F0 57
SCROLL LOCK
5F <-
ED ->
FA <-
00 ->
FA <-
F0 <-
5F <-
SHIFT-SCROLL LOCK (NUMLOCK)     5F F0 5F
PAUSE/BREAK                     62 F0 62

INSERT                          67 F0 67
HOME                            6E F0 6E
PAGE UP                         6F F0 6F
DELETE                          64 F0 64
END                             65 F0 65
PAGE DOWN                       6D F0 6D

CURSOR UP                       63 F0 63
CURSOR DOWN                     60 F0 60
CURSOR LEFT                     61 F0 61
CURSOR RIGHT                    69 F0 69

KEYPAD *                        7E F0 7E
KEYPAD /                        77 F0 77
KEYPAD ,
76 <-
ED ->
FA <-
00 ->
FA <-
F0 <-
76 <-
KEYPAD -                        84 F0 84
KEYPAD +                        7C F0 7C
KEYPAD ENTER                    79 F0 79
KEYPAD .                        71 F0 71
KEYPAD 0                        70 F0 70
KEYPAD 1                        69 F0 69
KEYPAD 2                        72 F0 72
KEYPAD 3                        7A F0 7A
KEYPAD 4                        6B F0 6B
KEYPAD 5                        73 F0 73
KEYPAD 6                        74 F0 74
KEYPAD 7                        6C F0 6C
KEYPAD 8                        75 F0 75
KEYPAD 9                        7D F0 7D

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by Hiroshi Miur » Mon, 03 Feb 2003 04:50:06


Hi, Mr. Tomita,

In message "Re: [PATCH 2.5.59] support japanese JP106 keyboard on new console."

Quote:> I have a question.

> > +       if (atkbd->set == 5) {
> > +               atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> I'm interesting in the reason to use keycode 0x70 for 'Hiragana/Katakana' key.
> Please clarify.

This is answer for your question.

I have two point of view about this.
these are my try and error process.

First, I press Katakana_Hiragana key on console with 2.4.19, it warns

keyboard: unrecognized scancode (70) - ignored

Two, in a  2.4.20's pc_keyb.c,  there is a comment,
/*
 * The keycodes below are randomly located in 89-95,112-118,120-127.
 * They could be thrown away (and all occurrences below replaced by 0),
 * but that would force many users to use the `setkeycodes' utility, where
 * they needed not before. It does not matter that there are duplicates, as
 * long as no duplication occurs for any single keyboard.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^            
 */

Hiragana_Katakana was not defined before and I want to define a  keycode point.
When I saw 2.4.20 pc_keyb.c source, I found all keycode below 127 was used,
then there is no room. But the comment tell me I can use 120-123, 125-127 with
Japanese keyboard because these are not used on JP89/109 keyboards.
(124 is, as you know, Yen key)  THese are defined for a latin keyboards.
So I use 120.

How do you think about it?

--
Hiroshi Miura

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by Vojtech Pavli » Mon, 03 Feb 2003 10:30:07



> Hi, Mr. Tomita,

> In message "Re: [PATCH 2.5.59] support japanese JP106 keyboard on new console."

> > I have a question.

> > > +       if (atkbd->set == 5) {
> > > +               atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> > I'm interesting in the reason to use keycode 0x70 for 'Hiragana/Katakana' key.
> > Please clarify.

> This is answer for your question.

> I have two point of view about this.
> these are my try and error process.

> First, I press Katakana_Hiragana key on console with 2.4.19, it warns

> keyboard: unrecognized scancode (70) - ignored

> Two, in a  2.4.20's pc_keyb.c,  there is a comment,
> /*
>  * The keycodes below are randomly located in 89-95,112-118,120-127.
>  * They could be thrown away (and all occurrences below replaced by 0),
>  * but that would force many users to use the `setkeycodes' utility, where
>  * they needed not before. It does not matter that there are duplicates, as
>  * long as no duplication occurs for any single keyboard.
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^            
>  */

> Hiragana_Katakana was not defined before and I want to define a  keycode point.
> When I saw 2.4.20 pc_keyb.c source, I found all keycode below 127 was used,
> then there is no room. But the comment tell me I can use 120-123, 125-127 with
> Japanese keyboard because these are not used on JP89/109 keyboards.
> (124 is, as you know, Yen key)  THese are defined for a latin keyboards.
> So I use 120.

> How do you think about it?

In 2.4 you can, in 2.5 the 'as long as no duplication occurs for any
single keyboard' is not valid anymore, and the keycode for
hiragana/katakana is defined to be 183 I think.

--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by John Bradfor » Mon, 03 Feb 2003 12:50:04


Quote:> > Hiragana_Katakana was not defined before and I want to define a
> > keycode point.
> > When I saw 2.4.20 pc_keyb.c source, I found all keycode below 127
> > was used, then there is no room. But the comment tell me I can use
> > 120-123, 125-127 with Japanese keyboard because these are not used
> > on JP89/109 keyboards.
> > (124 is, as you know, Yen key)  THese are defined for a latin
> > keyboards.  So I use 120.

> > How do you think about it?

> In 2.4 you can, in 2.5 the 'as long as no duplication occurs for any
> single keyboard' is not valid anymore, and the keycode for
> hiragana/katakana is defined to be 183 I think.

We assigned 182 to hiragana/katakana for set 3 in 2.5, and left 183
undefined.  Should we change the 2.5 keycode to 183?

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by Vojtech Pavli » Mon, 03 Feb 2003 12:50:07



> > > Hiragana_Katakana was not defined before and I want to define a
> > > keycode point.
> > > When I saw 2.4.20 pc_keyb.c source, I found all keycode below 127
> > > was used, then there is no room. But the comment tell me I can use
> > > 120-123, 125-127 with Japanese keyboard because these are not used
> > > on JP89/109 keyboards.
> > > (124 is, as you know, Yen key)  THese are defined for a latin
> > > keyboards.  So I use 120.

> > > How do you think about it?

> > In 2.4 you can, in 2.5 the 'as long as no duplication occurs for any
> > single keyboard' is not valid anymore, and the keycode for
> > hiragana/katakana is defined to be 183 I think.

> We assigned 182 to hiragana/katakana for set 3 in 2.5, and left 183
> undefined.  Should we change the 2.5 keycode to 183?

No - just bad memory on my side, it might as well be 183. ;)

--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

support japanese JP106 keyboard on new console.

Post by Hiroshi Miur » Thu, 06 Feb 2003 06:00:15


In message "Re: [PATCH 2.5.59] support japanese JP106 keyboard on new console."

Quote:> In 2.4 you can, in 2.5 the 'as long as no duplication occurs for any
> single keyboard' is not valid anymore, and the keycode for
> hiragana/katakana is defined to be 183 I think.

I can understand the rule of  international and language keys in 2.5.
I think hiragana/katakana is defined to be '182'.
The keycode 183 is a yen/pipe key.

--- linux-2.5.59/drivers/input/keyboard/atkbd.c 2002-12-03 07:59:41.000000000 +0900

 static unsigned char atkbd_set2_keycode[512] = {
          0, 67, 65, 63, 61, 59, 60, 88,  0, 68, 66, 64, 62, 15, 41, 85,
-         0, 56, 42,  0, 29, 16,  2, 89,  0,  0, 44, 31, 30, 17,  3, 90,
+         0, 56, 42,182, 29, 16,  2, 89,  0,  0, 44, 31, 30, 17,  3, 90,
          0, 46, 45, 32, 18,  5,  4, 91,  0, 57, 47, 33, 20, 19,  6,  0,
          0, 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,
--
Hiroshi Miura

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/