From: Andries Brouwer <email@example.com>
To: Alan Cox <firstname.lastname@example.org>
Cc: Pete Zaitcev <email@example.com>,
Chris Heath <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>
Subject: Re: i8042 problem
Date: Mon, 28 Jul 2003 13:59:24 +0200 [thread overview]
Message-ID: <20030728115924.GB1706@win.tue.nl> (raw)
On Mon, Jul 28, 2003 at 12:25:05PM +0100, Alan Cox wrote:
> On Llu, 2003-07-28 at 02:55, Pete Zaitcev wrote:
> > > Date: Sun, 27 Jul 2003 12:47:26 +0200
> > > From: Andries Brouwer <firstname.lastname@example.org>
> > > So the culprit is the failing of atkbd_probe().
> > > It does a ATKBD_CMD_GETID, but gets no answer, then a
> > > ATKBD_CMD_SETLEDS, and that command fails.
> > I see the light now. Somehow I imagined that atkbd code does not call
> > the ->open for the port. Now it all falls into place. Everything works
> > with a bigger timeout.
> Unfortunately with this change several people still report failures
Ach. One bug fixed and the Linux kernel is still not perfect?
What a pity.
[But yes, as I also said to someone else: on i386 one has a working
keyboard after bootup. No initialization and no probing required.
The new keyboard code uses a lot of knowledge about common keyboards
and keyboard controllers. It works in most cases. But already the
linux-kernel readers see a long stream of problems. I am afraid of
the effect on a million Linux users.]
[[On the other hand, as I wrote somewhere else, this is a great way
to learn a lot about very obscure keyboards.]]
next prev parent reply other threads:[~2003-07-28 11:44 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 [this message]
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
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).