FYI PS/2 Mouse problems -- userland issue
From: Ben LaHaise <[email protected]>
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
Quoted 5 lines · On Tue, 21 Aug 2001 [email protected] wrote:
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.
Nothing in a usable state. It needs a few days of work, but the general design is done. Having high resolution timers would help, but it's not essential. Most of the work was in tracking down all the docs for the keyboard and ps/2 mouse ports to get an overview of what the code was trying to coax the hardware into doing. 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.
-ben