linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: "Norman Diamond" <ndiamond@wta.att.ne.jp>
Cc: "Clemens Schwaighofer" <cs@tequila.co.jp>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Japanese keyboards broken in 2.6
Date: Fri, 25 Jul 2003 17:42:28 +0200	[thread overview]
Message-ID: <20030725154228.GC606@win.tue.nl> (raw)
In-Reply-To: <0e0101c35297$cb1890f0$4fee4ca5@DIAMONDLX60>

On Fri, Jul 25, 2003 at 07:30:04PM +0900, Norman Diamond wrote:

> > setkeycodes 0x6a 124 1>&2 in your rc.local, local.start or whatever.
> > works fine for me for alle 2.5x kernels
> 
> There must be a ton of odd stuff going on.  "showkey" used to say that the
> scan code is 0x7d not 0x6a, but now it displays weird stuff.  As previously
> mentioned, "getkeycodes" displays a table which seems far removed from
> reality.  But the patch from junkio@cox.net worked (but "showkey" and
> "getkeycodes" still produce weird output).

Yes.

I am a little bit unhappy with the state of the kbd code
(but have not yet decided whether I want to attempt to fix something).

One aspect of the matter is that raw mode no longer is raw.
The keyboard sends codes and the input layer translates that into
the codes the input layer thinks the keyboard should have sent.
Then, when one wants the raw codes, a reverse translation is used,
but since the mapping is not one-to-one the reverse translation
does not produce what the keyboard sent to start with.

In particular this means that showkey is no longer useful under 2.5
if one wants to investigate the scancodes a keyboard sends.

Andries


[PS - Some ioctls are broken. Recompiling kernel and loadkeys/dumpkeys
with larger structures works for private use, but the kernel ABI must
not change, so for actual kernel patches one needs new ioctl numbers.]


  reply	other threads:[~2003-07-25 15:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 13:56 Norman Diamond
2003-07-22 15:29 ` Andries Brouwer
2003-07-23 13:14   ` Norman Diamond
2003-07-23 13:38   ` OGAWA Hirofumi
2003-07-24 11:16     ` Hiroshi Miura
2003-07-24 14:26       ` OGAWA Hirofumi
2003-07-25  7:49 ` Clemens Schwaighofer
2003-07-25 10:30   ` Norman Diamond
2003-07-25 15:42     ` Andries Brouwer [this message]
     [not found] <fa.jnbj30u.1g6me0g@ifi.uio.no>
     [not found] ` <fa.d9tgtm5.1m7agi1@ifi.uio.no>
2003-07-25  1:00   ` junkio
2003-07-25  4:16     ` OGAWA Hirofumi
2003-07-25  9:27 John Bradford
2003-07-25 16:01 John Bradford
2003-07-25 16:09 ` Andries Brouwer
2003-07-25 16:39 John Bradford

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=20030725154228.GC606@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=cs@tequila.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    --subject='Re: Japanese keyboards broken in 2.6' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).