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: vojtech@suse.cz, tomita@cinet.co.jpmiura@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 13:10:36 +0000 (GMT)	[thread overview]
Message-ID: <200301251310.h0PDAaai000191@darkstar.example.net> (raw)
In-Reply-To: <20030125120113.B28830@ucw.cz> from "Vojtech Pavlik" at Jan 25, 2003 12:01:13 PM

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

Likewise, if I press right-shift and @ to get ` the keyboard actually
sends a release 54 as soon as I press @, even though I'm still holding
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.

  reply	other threads:[~2003-01-25 13:00 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 [this message]
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=200301251310.h0PDAaai000191@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=tomita@cinet.co.jpmiura \
    --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