From: Vojtech Pavlik <vojtech@suse.cz>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: David Monro <davidm@amberdata.demon.co.uk>,
John Bradford <john@grabjohn.com>,
linux-kernel@vger.kernel.org
Subject: Re: handling an oddball PS/2 keyboard (w/ patch)
Date: Fri, 16 Jan 2004 11:41:30 +0100 [thread overview]
Message-ID: <20040116104130.GA6431@ucw.cz> (raw)
In-Reply-To: <20031226235843.GA15973@win.tue.nl>
On Sat, Dec 27, 2003 at 12:58:43AM +0100, Andries Brouwer wrote:
> On Fri, Dec 26, 2003 at 11:22:10AM +0100, Vojtech Pavlik wrote:
>
> > This is intentional. Set 3 was never meant to be translated.
>
> In fact it is just the opposite. Set 3 was designed to be translated.
> Look at the translated codes:
> Q (10), W (11), E (12), R (13), T (14), Y (15), U (16), I (17), O (18), P (19).
> Completely regular.
> Now look at the untranslated codes:
> Q (15), W (1d), E (24), R (2d), T (2c), Y (35), U (3c), I (43), O (44), P (4d).
> Messy.
Not at all. If you draw the whole keyboard, you can see the underlying
matrix of the Set3 codes.
And most importantly, there are more than a few set3 keyboards which have
scancodes which cannot be translated safely (either > 0x80 or codes like
0x7e).
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-01-16 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 2:49 handling an oddball PS/2 keyboard David Monro
2003-12-25 6:39 ` Andries Brouwer
2003-12-25 13:16 ` John Bradford
2003-12-25 15:10 ` David Monro
2003-12-25 15:21 ` John Bradford
2003-12-26 2:04 ` handling an oddball PS/2 keyboard (w/ patch) David Monro
2003-12-26 10:22 ` Vojtech Pavlik
2003-12-26 23:58 ` Andries Brouwer
2004-01-16 10:41 ` Vojtech Pavlik [this message]
2003-12-25 15:08 ` handling an oddball PS/2 keyboard David Monro
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=20040116104130.GA6431@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=davidm@amberdata.demon.co.uk \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
/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.