From: Andries Brouwer <aebr@win.tue.nl>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
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: Mon, 28 Jul 2003 17:51:18 +0200 [thread overview]
Message-ID: <20030728155118.GA1761@win.tue.nl> (raw)
In-Reply-To: <Pine.GSO.3.96.1030728173054.15233C-100000@delta.ds2.pg.gda.pl>
On Mon, Jul 28, 2003 at 05:43:51PM +0200, Maciej W. Rozycki wrote:
> 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? :-)
next prev parent reply other threads:[~2003-07-28 15:36 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 [this message]
2003-07-29 18:29 ` Maciej W. Rozycki
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=20030728155118.GA1761@win.tue.nl \
--to=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 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.