From: Vojtech Pavlik <vojtech@suse.cz>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Pete Zaitcev <zaitcev@redhat.com>,
Chris Heath <chris@heathens.co.nz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: i8042 problem
Date: Tue, 12 Aug 2003 22:46:25 +0200 [thread overview]
Message-ID: <20030812204625.GB23011@ucw.cz> (raw)
In-Reply-To: <Pine.GSO.3.96.1030729192558.10528A-100000@delta.ds2.pg.gda.pl>
On Tue, Jul 29, 2003 at 08:29:01PM +0200, Maciej W. Rozycki wrote:
> Nice joke, but I'll answer seriously. No support was provided. Hooking
> a PC/XT keyboard to the 8042, if supported, requires a different setup of
> the command byte and is possibly done by the system firmware. You can
> read the command byte to see which configuration is used.
>
> Wrt polling vs IRQ-driven probing and setup: using IRQ is a natural
> choice as you have to do keyboard detection in the IRQ handler anyway to
> properly support hot plugging of a PC/AT or a PS/2 keyboard.
The only problem there is that it results in a damn complex state
machine. Look at the PS/2 mouse probing and imagine how the state
machine would look.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2003-08-12 20:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 6:11 i8042 problem Pete Zaitcev
2003-07-26 9:36 ` Andries Brouwer
2003-07-27 1:41 ` Chris Heath
2003-07-27 6:06 ` Pete Zaitcev
2003-07-27 10:47 ` Andries Brouwer
2003-07-28 1:55 ` Pete Zaitcev
2003-07-28 11:25 ` Alan Cox
2003-07-28 11:59 ` Andries Brouwer
2003-07-28 14:01 ` Maciej W. Rozycki
2003-07-28 14:54 ` Andries Brouwer
2003-07-28 15:43 ` Maciej W. Rozycki
2003-07-28 15:51 ` Andries Brouwer
2003-07-29 18:29 ` Maciej W. Rozycki
2003-08-12 20:46 ` Vojtech Pavlik [this message]
2003-08-13 13:44 ` Maciej W. Rozycki
2003-07-28 16:07 ` Pete Zaitcev
2003-08-12 20:47 ` Vojtech Pavlik
2003-08-12 20:42 ` Vojtech Pavlik
2003-08-12 23:06 ` Andries Brouwer
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=20030812204625.GB23011@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@heathens.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=zaitcev@redhat.com \
/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).