[lkml]   [2001]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: BUG: pc_keyb.c
    From Tue Aug 21 00:48:32 2001

> But the present code does not guarantee such a delay at all.
> For example, kbd_write_cmd() does
> kb_wait();
> outb(...);
> kb_wait();
> where the second kb_wait reads the status very quickly after the first.

Thats wrong by the spec. I dug out my docs - there is a required 1mS (not
2 tho) delay for keyboard port accesses.

Since there are various keyboard and mouse paths that can lead to
register access, it seems that we must either prefix each access
by a wait, or otherwise we must remember at what time we last did
a read.

Something else is that on some ancient (MCA) systems a delay is required
between finding the ready bit and actually reading the data
(Frank van Gilluwe, p. 273: wait 7 us).

On the other hand, 1 ms is a very long time these days; it is a bit
surprising that modern hardware should need delays in that order of
magnitude; maybe the problem is elsewhere and the mdelay(2) happens
to change the timing and avoid the problem.

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 12:57    [W:0.049 / U:0.736 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site