From: Andries Brouwer <aebr@win.tue.nl>
To: Pavel Machek <pavel@ucw.cz>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Four function buttons on DELL Latitude X200
Date: Thu, 12 Dec 2002 02:01:16 +0100 [thread overview]
Message-ID: <20021212010116.GA10297@win.tue.nl> (raw)
In-Reply-To: <20021210213444.GA451@elf.ucw.cz>
On Tue, Dec 10, 2002 at 10:34:44PM +0100, Pavel Machek wrote:
> > The PC only has so many possible keycodes (with E0 and E1 it's still
> > in the sub-300 range.) It won't fit within 128, but I would really
> > like an algorithmic mapping from scancodes to keycodes so we don't
> > continue to have this problem.
> >
> > For example, using a 16-bit keycode model:
> >
> >
> > Scancode Keycode (binary)
> > mxxxxxxx m0000000 0xxxxxxx
> > E0 mxxxxxxx m0000000 1xxxxxxx
> > E1 mxxxxxxx yyyyyyyy mxxxxxxx yyyyyyyy
> >
> > m = make/break bit
>
> Well, nothing prevents keyboard manufacturers from using 0xe2 as a
> prefix, too. I think there are really *weird* keyboards out there.
>
> Pavel
Indeed. See, for example,
http://www.win.tue.nl/~aeb/linux/kbd/scancodes-2.html#ss2.18
for a keyboard that uses 0x80 as a prefix.
next prev parent reply other threads:[~2002-12-12 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 23:35 PATCH: Four function buttons on DELL Latitude X200 Pavel Janík
2002-12-09 0:19 ` Bernd Eckenfels
2002-12-09 19:33 ` H. Peter Anvin
2002-12-10 21:34 ` Pavel Machek
2002-12-11 22:41 ` H. Peter Anvin
2002-12-13 16:22 ` Jan-Benedict Glaw
2002-12-12 1:01 ` Andries Brouwer [this message]
2002-12-12 8:43 ` Vojtech Pavlik
2002-12-12 11:48 ` James H. Cloos Jr.
2002-12-12 11:51 ` Vojtech Pavlik
2002-12-12 12:17 ` James H. Cloos Jr.
2002-12-12 12:20 ` Vojtech Pavlik
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=20021212010116.GA10297@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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