public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Osamu Tomita <tomita@cinet.co.jp>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Hiroshi Miura <miura@da-cha.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.59] support japanese JP106 keyboard on new console.
Date: Sat, 25 Jan 2003 11:33:24 +0100	[thread overview]
Message-ID: <20030125113324.D28292@ucw.cz> (raw)
In-Reply-To: <3E3171FC.FE9139CE@cinet.co.jp>; from tomita@cinet.co.jp on Sat, Jan 25, 2003 at 02:03:56AM +0900

On Sat, Jan 25, 2003 at 02:03:56AM +0900, Osamu Tomita wrote:
> Please fix atkbd_set2_keycode table in atkbd.c for jp106 keyboard.
> 
> Vojtech Pavlik wrote:
> > 
> > On Fri, Jan 24, 2003 at 12:14:53PM +0900, Hiroshi Miura wrote:
> > 
> > > 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
> > > @@ -309,6 +309,12 @@
> > >       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
> > > @@ -531,6 +537,12 @@
> > >       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

  reply	other threads:[~2003-01-25 10:29 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 [this message]
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               ` Set2 scancodes for Japanese keyboard John Bradford
2003-01-25 17:28           ` [Corrected] " 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=20030125113324.D28292@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miura@da-cha.org \
    --cc=tomita@cinet.co.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