[lkml]   [2003]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: i8042 problem
On Mon, 28 Jul 2003, Andries Brouwer wrote:

> On Mon, Jul 28, 2003 at 12:25:05PM +0100, Alan Cox wrote:
> > On Llu, 2003-07-28 at 02:55, Pete Zaitcev wrote:
> > >
> > > 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.]

Well, are timeouts needed at all, except for a single initial command to
see if a device is there? I would imagine the keyboard to be initialized
using an interrupt-driven state machine.

+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+ e-mail:, PGP key available +

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:47    [W:0.111 / U:2.996 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site