From: Andries Brouwer <aebr@win.tue.nl>
To: John Bradford <john@grabjohn.com>
Cc: ndiamond@wta.att.ne.jp, cs@tequila.co.jp, linux-kernel@vger.kernel.org
Subject: Re: Japanese keyboards broken in 2.6
Date: Fri, 25 Jul 2003 18:09:53 +0200 [thread overview]
Message-ID: <20030725160953.GD606@win.tue.nl> (raw)
In-Reply-To: <200307251601.h6PG1etD001373@81-2-122-30.bradfords.org.uk>
On Fri, Jul 25, 2003 at 05:01:40PM +0100, John Bradford wrote:
> > 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.
>
> Doesn't AT-set3 usually have a closer one to one mapping of keys?
Sorry - I am unable to make sense of your question.
Below some remarks, maybe related.
Some remarks on scancode sets live on
http://www.win.tue.nl/~aeb/linux/kbd/scancodes-7.html
Not all keyboards support all scancode sets. For example,
my MyCom laptop only supports scancode Set 2, and its keyboard
does not react at all when in mode 1 or 3.
The normal, default mode is translated scancode set 2.
Putting keyboards in other modes is asking for trouble.
Andries
next prev parent reply other threads:[~2003-07-25 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 16:01 Japanese keyboards broken in 2.6 John Bradford
2003-07-25 16:09 ` Andries Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 16:39 John Bradford
2003-07-25 9:27 John Bradford
[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-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
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=20030725160953.GD606@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=cs@tequila.co.jp \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.