All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Monro <davidm@amberdata.demon.co.uk>
To: John Bradford <john@grabjohn.com>
Cc: Andries Brouwer <aebr@win.tue.nl>,
	linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: handling an oddball PS/2 keyboard
Date: Thu, 25 Dec 2003 15:10:43 +0000	[thread overview]
Message-ID: <3FEAFDF3.80008@amberdata.demon.co.uk> (raw)
In-Reply-To: <200312251316.hBPDG7LT000163@81-2-122-30.bradfords.org.uk>

John Bradford wrote:
>>I suppose Vojtech will have no objections to using this ID
>>to skip the tests for e0 and e1 as protocol (escape) scancodes.
> 
> 
> There might be no need for such a workaround - a lot of PS/2 devices
> which were not intended for PCs work fine in set 3, particularly if
> the device they were intended to work with uses set 3 natively, where
> this conflict with protocol scancodes problem doesn't exist.  If the
> keyboard works in set 3, add 0xab85 to the list of keyboards to force
> set 3 for, (and maybe also add the ID for my keyboard while we're at
> it :-) ).

I will definitely explore this possibility. Whats the ID of your 
keyboard? (and what is it?)

Cheers,

	David

> 
> John.



  reply	other threads:[~2003-12-25 15:10 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 [this message]
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   ` 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=3FEAFDF3.80008@amberdata.demon.co.uk \
    --to=davidm@amberdata.demon.co.uk \
    --cc=aebr@win.tue.nl \
    --cc=john@grabjohn.com \
    --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.