On Tue, 21 Aug 2001, Stephen Satchell wrote:
> This MAY be a kernel issue depending on where I locate the mouse
> initialization code. If it is in the kernel, then there will need
> to be a patch to allow the mouse to be re-initialized into the mode
> everyone expects.
[Funny - we just discussed this last week.]
The kernel has nothing to do with reinitializing the mouse: X has to do
that.
[Indeed. Or gpm.]
I plan to submit a
patch that replaces much of the existing pc keyboard/mouse code with state
machine driven code that doesn't block interrupts out for long periods of
time, as well as fixing a few of the lockup issues the current driver has.
Have you written the patch already?
There are interesting difficulties here.
Andries
-
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/