From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: 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, 29 Jul 2003 20:29:01 +0200 (MET DST) [thread overview]
Message-ID: <Pine.GSO.3.96.1030729192558.10528A-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <20030728155118.GA1761@win.tue.nl>
On Mon, 28 Jul 2003, Andries Brouwer wrote:
> > > > Well, are timeouts needed at all?
> > >
> > > Yes. We send a command to the keyboard. It may react, or it may not.
> >
> > But we need not wait for that actively. If we are unsure about a result
> > of a command, then we may send a command in question followed with an echo
> > request. This assures an IRQ will finally arrive and if no command
> > response arrives before an echo response, then the keyboard ignored the
> > command. I used this approach many years ago to differ between PS/2
> > keyboards (which respond with 0xfa,0xab,0x83 to a request for ID) and
> > genuine PC/AT ones (which respond with lone 0xfa). It worked.
>
> And what did you do for XT? :-)
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.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-07-29 18:31 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 [this message]
2003-08-12 20:46 ` Vojtech Pavlik
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=Pine.GSO.3.96.1030729192558.10528A-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@heathens.co.nz \
--cc=linux-kernel@vger.kernel.org \
--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).