On Tue, 21 Aug 2001 Andries.Brouwer@cwi.nl wrote:
> > Armed with docs I was able to see just why our code
> > is completely wrong for handling things like the ps/2
> > mouse being removed at runtime.
>
> Yes, or being added, to be more precise. But it will not be
> easy to do it right. So many different ps2-like types of mouse.
> There are heuristics, like the AA 00 that I gave last week or so.
> (But not every ps2-mouse emits this sequence.)
That's what reset probes are for... =) At least in the case of the mouse,
this really isn't the kernel's business. But for the keyboard, it is.
> Also state machines have difficulties. Many types of mouse react
The state machine I'm talking about is for the general keyboard controller
poking code which currently is well sprinkled with udelay()s. I really
don't want my dual 1.2GHz CPUs waiting on a keyboard controller.
-ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:46 EST