From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: ddstreet@us.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: ps2 keyboard filter hook
Date: Fri, 15 Jun 2001 16:24:13 -0400 [thread overview]
Message-ID: <3B2A6EED.86A318F3@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10106151345510.25518-200000@ddstreet.raleigh.ibm.com>
ddstreet@us.ibm.com wrote:
> In order to use these keyboards, a the standard PS/2 driver needs to behave a
> bit differently; thus attached is a modifcation to the PS/2 driver which allows
> other drivers to register with the PS/2 driver as 'filters'. There is a
> arbitrary max number of 'filters' set to 1, which is a compile-time define.
> The registered drivers are called (in order of registration) for every scancode,
> and they may change or consume the scancode (or allow it to pass). Also the
> 'filters' are given a function to send an variable-sized buffer to the keyboard
> output port; this function is synchronized using a semaphore which also
> coordinates with pckbd_leds().
Didn't we just conclude a discussion here on linux-kernel, which said
that patches which simply add hooks allowing proprietary extensions are
not accepted into the kernel?
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-15 20:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 20:03 ps2 keyboard filter hook ddstreet
2001-06-15 20:24 ` Jeff Garzik [this message]
2001-06-15 20:35 ` Alan Cox
2001-06-16 14:13 ` Michael Rothwell
[not found] <OF08385BE5.529A6C1C-ON85256A6C.0070A351@raleigh.ibm.com>
2001-06-15 21:03 ` Dan Streetman
2001-06-16 4:50 ` Mike A. Harris
[not found] <OF6CD0EC09.7E779796-ON85256A6C.007426B5@raleigh.ibm.com>
2001-06-15 21:30 ` Dan Streetman
2001-06-15 21:44 ` Vojtech Pavlik
[not found] <OF7CA123EC.2D473DAE-ON85256A6C.00782D85@raleigh.ibm.com>
2001-06-15 22:14 ` Dan Streetman
2001-06-15 22:21 ` Vojtech Pavlik
2001-06-16 12:53 Andries.Brouwer
2001-06-16 13:38 ` Christoph Hellwig
2001-06-16 16:00 Andries.Brouwer
2001-06-18 16:42 Dan Streetman
2001-06-28 15:40 Dan Streetman
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=3B2A6EED.86A318F3@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ddstreet@us.ibm.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;
as well as URLs for NNTP newsgroup(s).