public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH: Four function buttons on DELL Latitude X200
Date: Tue, 10 Dec 2002 22:34:44 +0100	[thread overview]
Message-ID: <20021210213444.GA451@elf.ucw.cz> (raw)
In-Reply-To: <at2r5v$fib$1@cesium.transmeta.com>

Hi!

> > In article <m3d6ocjd81.fsf@Janik.cz> you wrote:
> > > this patch add support for four functions key on DELL Latitude X200.
> > 
> > we need a more generic appoach to handle those key codes for various
> > extensions. I think a pure software reconfiguration of the keymaps or a
> > daemon trakcing the raw codes is fine. Perhaps we can make something like a
> > hook into the kernel where all untrapped function keys are send to in raw
> > format?
> > 
> 
> 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
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?

  reply	other threads:[~2002-12-11 22:32 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 [this message]
2002-12-11 22:41       ` H. Peter Anvin
2002-12-13 16:22         ` Jan-Benedict Glaw
2002-12-12  1:01       ` Andries Brouwer
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=20021210213444.GA451@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox