From: David Monro <davidm@amberdata.demon.co.uk>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: handling an oddball PS/2 keyboard
Date: Thu, 25 Dec 2003 15:08:38 +0000 [thread overview]
Message-ID: <3FEAFD76.8010703@amberdata.demon.co.uk> (raw)
In-Reply-To: <20031225063936.GA15560@win.tue.nl>
Andries Brouwer wrote:
> On Thu, Dec 25, 2003 at 02:49:40AM +0000, David Monro wrote:
>
>
>>I have a slightly odd PS/2 keyboard which I'm not quite sure of the best
[..]
>
> Interesting. I rearranged my scancode data page a bit and added
> your info - see http://www.win.tue.nl/~aeb/linux/kbd/scancodes-6.html
> Are your scancodes identical to those reported by Benjamin Carter?
Almost precisely! The only differences I can see are probably a result
of his being a japanese one; the physical layout is a little different
and I have PF1-PF4 above the numeric keypad rather than the japanese
compose keys. I'll send you a more detailed description for your page.
>
>>So.. could I get a bunch of people to have a look in
>>/proc/bus/input/devices, and see what the 'Version' field for their
[..]
>
>
> Yours is the second report I see for ID 0xab85.
[..]
Hmm. I've seen those extended 122 key IBM keyboards, although I _think_
most of the ones I've seen have been the APL variant. I may know someone
who has one, so I'll see if I can get hold of it to test.
Cheers,
David
prev parent reply other threads:[~2003-12-25 15:08 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
2003-12-25 15:08 ` David Monro [this message]
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=3FEAFD76.8010703@amberdata.demon.co.uk \
--to=davidm@amberdata.demon.co.uk \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.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 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.