support japanese JP106 keyboard on new console.

support japanese JP106 keyboard on new console.

Post by Hiroshi Miur » Sat, 25 Jan 2003 05:20:11



Hi,

After re-writting a console layer, a japanese keyboard is not supported (or degraded).
This patch fixs it.

A USB keyboard driver may have same problem, but I don't have one.

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

        if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
                atkbd->oldset = 2;

+       if (atkbd->id == 0xab02) {
+               printk("atkbd: jp109(106) keyboard found\n");
+               param[0] = atkbd_set;
+               atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
+               return 5;
+       }
 /*
  * For known special keyboards we can go ahead and set the correct set.

        else
                memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

+       if (atkbd->set == 5) {
+               atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
+               atkbd->keycode[0x6a] = 0x7c;  /* Yen, pipe 124*/
+               atkbd->set = 2;
+       }
+
        atkbd->dev.name = atkbd->name;
        atkbd->dev.phys = atkbd->phys;

        input_register_device(&atkbd->dev);

-       printk(KERN_INFO "input: %s on %s\n", atkbd->name, serio->phys);
+       printk(KERN_INFO "input: %s (0x%x) on %s\n", atkbd->name, atkbd->id, serio->phys);
 }

--
Hiroshi Miura  --- http://www.da-cha.org/

Key fingerprint = 9117 9407 5684 FBF1 4063  15B4 401D D077 04AB 8617
-- My hacking life is happy as the day is long

-
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 » Sat, 25 Jan 2003 08:00:11



> After re-writting a console layer, a japanese keyboard is not supported (or degraded).
> This patch fixs it.

This patch doesn't work, all normal keyboards - not just japanese ones have id of 0xab02.

> A USB keyboard driver may have same problem, but I don't have one.

> --- linux-2.5.59/drivers/input/keyboard/atkbd.c    2002-12-03 07:59:41.000000000 +0900
> +++ edited/linux-2.5.59/drivers/input/keyboard/atkbd.c     2003-01-24 09:13:11.000000000 +0900

>    if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
>            atkbd->oldset = 2;

> +  if (atkbd->id == 0xab02) {
> +          printk("atkbd: jp109(106) keyboard found\n");
> +          param[0] = atkbd_set;
> +          atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
> +          return 5;
> +  }
>  /*
>   * For known special keyboards we can go ahead and set the correct set.
>   * We check for NCD PS/2 Sun, NorthGate OmniKey 101 and

>    else
>            memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

> +  if (atkbd->set == 5) {
> +          atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> +          atkbd->keycode[0x6a] = 0x7c;  /* Yen, pipe 124*/
> +          atkbd->set = 2;
> +  }
> +
>    atkbd->dev.name = atkbd->name;
>    atkbd->dev.phys = atkbd->phys;
>    atkbd->dev.id.bustype = BUS_I8042;

>    input_register_device(&atkbd->dev);

> -  printk(KERN_INFO "input: %s on %s\n", atkbd->name, serio->phys);
> +  printk(KERN_INFO "input: %s (0x%x) on %s\n", atkbd->name, atkbd->id, serio->phys);
>  }

> --
> Hiroshi Miura  --- http://www.da-cha.org/

> Key fingerprint = 9117 9407 5684 FBF1 4063  15B4 401D D077 04AB 8617
> -- My hacking life is happy as the day is long

--
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 Osamu Tomit » Sat, 25 Jan 2003 19:10:13


Please fix atkbd_set2_keycode table in atkbd.c for jp106 keyboard.



> > After re-writting a console layer, a japanese keyboard is not supported (or degraded).
> > This patch fixs it.

> This patch doesn't work, all normal keyboards - not just japanese ones have id of 0xab02.

I agree this point. It's difficult to detect jp106 keyboard automatically.
Many venders use common internal circuits with us keyborad.

> > A USB keyboard driver may have same problem, but I don't have one.

> > --- linux-2.5.59/drivers/input/keyboard/atkbd.c       2002-12-03 07:59:41.000000000 +0900
> > +++ edited/linux-2.5.59/drivers/input/keyboard/atkbd.c        2003-01-24 09:13:11.000000000 +0900

> >       if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
> >               atkbd->oldset = 2;

> > +     if (atkbd->id == 0xab02) {
> > +             printk("atkbd: jp109(106) keyboard found\n");
> > +             param[0] = atkbd_set;
> > +             atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
> > +             return 5;
> > +     }
> >  /*
> >   * For known special keyboards we can go ahead and set the correct set.
> >   * We check for NCD PS/2 Sun, NorthGate OmniKey 101 and

> >       else
> >               memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

> > +     if (atkbd->set == 5) {
> > +             atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> > +             atkbd->keycode[0x6a] = 0x7c;  /* Yen, pipe 124*/

I think he catches good point. Kernel 2.0-2.4 use keycode 124 (0x7c) for scancode 0x6a.
2.5 uses keycode 183. This breaks jp106 keymaps. We cannot type '\' and '|' from jp106
keyboard on 2.5 kernel.
I believe there is no impact by changing keycode 183 to 124.

> > --
> > Hiroshi Miura  --- http://www.da-cha.org/

> --
> Vojtech Pavlik
> SuSE Labs

Regard,
Osamu Tomita
-
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 Osamu Tomit » Sat, 25 Jan 2003 19:20:12


I have a question.


> Hi,

> After re-writting a console layer, a japanese keyboard is not supported (or degraded).
> This patch fixs it.

> A USB keyboard driver may have same problem, but I don't have one.

> --- linux-2.5.59/drivers/input/keyboard/atkbd.c 2002-12-03 07:59:41.000000000 +0900
> +++ edited/linux-2.5.59/drivers/input/keyboard/atkbd.c  2003-01-24 09:13:11.000000000 +0900

>         if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
>                 atkbd->oldset = 2;

> +       if (atkbd->id == 0xab02) {
> +               printk("atkbd: jp109(106) keyboard found\n");
> +               param[0] = atkbd_set;
> +               atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
> +               return 5;
> +       }
>  /*
>   * For known special keyboards we can go ahead and set the correct set.
>   * We check for NCD PS/2 Sun, NorthGate OmniKey 101 and

>         else
>                 memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

> +       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.

Regard,
Osamu Tomita
-
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 12:50:07



> Please fix atkbd_set2_keycode table in atkbd.c for jp106 keyboard.



> > > After re-writting a console layer, a japanese keyboard is not supported (or degraded).
> > > This patch fixs it.

> > This patch doesn't work, all normal keyboards - not just japanese ones have id of 0xab02.
> I agree this point. It's difficult to detect jp106 keyboard automatically.
> Many venders use common internal circuits with us keyborad.

> > > A USB keyboard driver may have same problem, but I don't have one.

> > > --- linux-2.5.59/drivers/input/keyboard/atkbd.c       2002-12-03 07:59:41.000000000 +0900
> > > +++ edited/linux-2.5.59/drivers/input/keyboard/atkbd.c        2003-01-24 09:13:11.000000000 +0900

> > >       if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
> > >               atkbd->oldset = 2;

> > > +     if (atkbd->id == 0xab02) {
> > > +             printk("atkbd: jp109(106) keyboard found\n");
> > > +             param[0] = atkbd_set;
> > > +             atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
> > > +             return 5;
> > > +     }
> > >  /*
> > >   * For known special keyboards we can go ahead and set the correct set.
> > >   * We check for NCD PS/2 Sun, NorthGate OmniKey 101 and

> > >       else
> > >               memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

> > > +     if (atkbd->set == 5) {
> > > +             atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> > > +             atkbd->keycode[0x6a] = 0x7c;  /* Yen, pipe 124*/
> I think he catches good point. Kernel 2.0-2.4 use keycode 124 (0x7c) for scancode 0x6a.
> 2.5 uses keycode 183. This breaks jp106 keymaps. We cannot type '\' and '|' from jp106
> keyboard on 2.5 kernel.
> I believe there is no impact by changing keycode 183 to 124.

Well, it's not so easy. Fortunately KEY_KPCOMMA can be relatively easily
moved elsewhere, however keys 181 to 198 are 'international and language
keys', defined the same way as USB/HID spec (please take a look at it).
Having a single one of them remapped elsewhere doesn't look so nice.

--
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 13:00:11


> > > > --- linux-2.5.59/drivers/input/keyboard/atkbd.c       2002-12-03 07:59:41.000000000 +0900
> > > > +++ edited/linux-2.5.59/drivers/input/keyboard/atkbd.c        2003-01-24 09:13:11.000000000 +0900

> > > >       if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
> > > >               atkbd->oldset = 2;

> > > > +     if (atkbd->id == 0xab02) {
> > > > +             printk("atkbd: jp109(106) keyboard found\n");
> > > > +             param[0] = atkbd_set;
> > > > +             atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
> > > > +             return 5;
> > > > +     }
> > > >  /*
> > > >   * For known special keyboards we can go ahead and set the correct set.
> > > >   * We check for NCD PS/2 Sun, NorthGate OmniKey 101 and

> > > >       else
> > > >               memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

> > > > +     if (atkbd->set == 5) {
> > > > +             atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> > > > +             atkbd->keycode[0x6a] = 0x7c;  /* Yen, pipe 124*/
> > I think he catches good point. Kernel 2.0-2.4 use keycode 124 (0x7c) for scancode 0x6a.
> > 2.5 uses keycode 183. This breaks jp106 keymaps. We cannot type '\' and '|' from jp106
> > keyboard on 2.5 kernel.
> > I believe there is no impact by changing keycode 183 to 124.

> Well, it's not so easy. Fortunately KEY_KPCOMMA can be relatively easily
> moved elsewhere, however keys 181 to 198 are 'international and language
> keys', defined the same way as USB/HID spec (please take a look at it).
> Having a single one of them remapped elsewhere doesn't look so nice.

The keymapping on my Japanese keyboard changes quite a bit when it's
set up to use set 3, instead of the default set 2.  I've temporarily
switched back to using set 2, until I've got time to set it up
properly, but the language keys don't function in set 2, (they
generate the same scancode as the space bar).

Let me know if I can provide any extra info from this keyboard - it's
an IBM 5576 Keyboard-2, part number 94X1110.

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 » Sun, 26 Jan 2003 13:10:07



> > > > > --- linux-2.5.59/drivers/input/keyboard/atkbd.c       2002-12-03 07:59:41.000000000 +0900
> > > > > +++ edited/linux-2.5.59/drivers/input/keyboard/atkbd.c        2003-01-24 09:13:11.000000000 +0900

> > > > >       if (atkbd_command(atkbd, &atkbd->oldset, ATKBD_CMD_GSCANSET))
> > > > >               atkbd->oldset = 2;

> > > > > +     if (atkbd->id == 0xab02) {
> > > > > +             printk("atkbd: jp109(106) keyboard found\n");
> > > > > +             param[0] = atkbd_set;
> > > > > +             atkbd_command(atkbd, param, ATKBD_CMD_SSCANSET);
> > > > > +             return 5;
> > > > > +     }
> > > > >  /*
> > > > >   * For known special keyboards we can go ahead and set the correct set.
> > > > >   * We check for NCD PS/2 Sun, NorthGate OmniKey 101 and

> > > > >       else
> > > > >               memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));

> > > > > +     if (atkbd->set == 5) {
> > > > > +             atkbd->keycode[0x13] = 0x70;  /* Hiragana/Katakana */
> > > > > +             atkbd->keycode[0x6a] = 0x7c;  /* Yen, pipe 124*/
> > > I think he catches good point. Kernel 2.0-2.4 use keycode 124 (0x7c) for scancode 0x6a.
> > > 2.5 uses keycode 183. This breaks jp106 keymaps. We cannot type '\' and '|' from jp106
> > > keyboard on 2.5 kernel.
> > > I believe there is no impact by changing keycode 183 to 124.

> > Well, it's not so easy. Fortunately KEY_KPCOMMA can be relatively easily
> > moved elsewhere, however keys 181 to 198 are 'international and language
> > keys', defined the same way as USB/HID spec (please take a look at it).
> > Having a single one of them remapped elsewhere doesn't look so nice.

> The keymapping on my Japanese keyboard changes quite a bit when it's
> set up to use set 3, instead of the default set 2.  I've temporarily
> switched back to using set 2, until I've got time to set it up
> properly, but the language keys don't function in set 2, (they
> generate the same scancode as the space bar).

> Let me know if I can provide any extra info from this keyboard - it's
> an IBM 5576 Keyboard-2, part number 94X1110.

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.

--
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 15:20:06


Quote:> > The keymapping on my Japanese keyboard changes quite a bit when it's
> > set up to use set 3, instead of the default set 2.  I've temporarily
> > switched back to using set 2, until I've got time to set it up
> > properly, but the language keys don't function in set 2, (they
> > generate the same scancode as the space bar).

> > Let me know if I can provide any extra info from this keyboard - it's
> > an IBM 5576 Keyboard-2, part number 94X1110.

> 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.

OK, half way through writing it down, I've realised what is happening
- in set 2, the keyboard seems to be emulating another keyboard
layout, (but apparently not a US or UK one).

For example, ; and : are on different keys.  Shift ; gives + and shift
: gives *

The keycodes generated, though, show up as follows:

; - 39
shift ; (+) - 13
: - 42, 39, release 39, release 42
shift : (*) - 9

So, if I press : on it's own, the keyboard actually simulates pressing
shift and ;



down right-shift, then sends 41, release 41, then 54

I suspect set 3 will producde a more direct mapping of a single
keycode for each key, but we shall see...

I'll send along the complete list when I've finished it, (it's taking
ages :-) ).

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 » Sun, 26 Jan 2003 15:20:08



> > > The keymapping on my Japanese keyboard changes quite a bit when it's
> > > set up to use set 3, instead of the default set 2.  I've temporarily
> > > switched back to using set 2, until I've got time to set it up
> > > properly, but the language keys don't function in set 2, (they
> > > generate the same scancode as the space bar).

> > > Let me know if I can provide any extra info from this keyboard - it's
> > > an IBM 5576 Keyboard-2, part number 94X1110.

> > 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.

> OK, half way through writing it down, I've realised what is happening
> - in set 2, the keyboard seems to be emulating another keyboard
> layout, (but apparently not a US or UK one).

> For example, ; and : are on different keys.  Shift ; gives + and shift
> : gives *

> The keycodes generated, though, show up as follows:

> ; - 39
> shift ; (+) - 13
> : - 42, 39, release 39, release 42
> shift : (*) - 9

> So, if I press : on it's own, the keyboard actually simulates pressing
> shift and ;



> down right-shift, then sends 41, release 41, then 54

Yeah, I've seen this before on some weird keyboards. We need to make
sure we understand properly decode what the keyboard is pretending to be
- no need to really detect what keys were pressed in reality and what
the keyboard just wants us to think are pressed.

Quote:> I suspect set 3 will producde a more direct mapping of a single
> keycode for each key, but we shall see...

I hope so.

Quote:> I'll send along the complete list when I've finished it, (it's taking
> ages :-) ).

--
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 Vojtech Pavli » Sun, 26 Jan 2003 17:50:04



> > Well, it's not so easy. Fortunately KEY_KPCOMMA can be relatively easily
> > moved elsewhere, however keys 181 to 198 are 'international and language
> > keys', defined the same way as USB/HID spec (please take a look at it).
> > Having a single one of them remapped elsewhere doesn't look so nice.

> > --
> > Vojtech Pavlik
> > SuSE Labs
> Thanks. I see. Keycode in the kernel should be unified.

Definitely. And cast in stone and never changed again.

Quote:> I'll use newer kbd utility (kbd-1.08) and rewrite keymap like below.
>  keycode 124 = backslash   bar     #Compatibility for 2.4 (for a while)
>  keycode 183 = backslash   bar

Yes, that'd be great.

Quote:> BTW. I've extracted japanese keyboard specification from OADG's documents.
> About OADG, please visit http://www.oadg.org/.
> I attach those files. Usefull?

Yes, I'm sure they'll be.

--
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:30:11


Quote:> > > 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


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

-
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:30:18


Some got missed off the first time:

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


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

-
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 19:40:07



> 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.

> 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


> 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

--
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:40:11



> > 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?  :-/

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/

 
 
 

1. URGENT HELP: Japanese user wants mail and staroffice in Japanese(Kanji)

A Japanese customer needs to open Office (Word) documents and exchange
email in Japanese characters (I understand it is Kanji).

I noticed that RH 7.2 comes with several packages related to Japanese
support but I don't know where/how to start.

RH72 would be installed in English [to make my tech-support life
easier :-) ], and then the user would read/send email in Japanese or
use Staroffice to read Word docs in Kanji characters.

I need help about where to start; basic and detailed info will be
appreciated, since I'm not familiar with the issues involved.

Redhat linux will be highly preferred since it standardized in this
environment. If there is a good solution with another linux distro,
please send info too.

Replies can be posted to the newsgroups directly or sent to my email
address.

Thanks.

2. Soap Box Speech: Monopoly and protectism, regards to the Microsoft settlement.

3. Japanese ftp sites (was Re: Japanese editor for LinuX)

4. FS:Sun Ultra 1/170E Creator 3D Complete System ..

5. Problem with japanese Keyboard key \ (yen key) on 2.5.68

6. GCC/Malloc bug? Help!

7. Japanese and English keyboard on 4.1.3?

8. numlock key

9. Japanese keyboards and linux

10. RedHat 5.0, Japanese Keyboard

11. japanese keyboards

12. Japanese Powerbook Keyboard

13. Japanese on Linux *Console*