Messages in this thread | | | Date | Wed, 5 Jul 2000 04:18:20 +0200 | From | "Andi Kleen" <> | Subject | Re: PS/2 mouse latency was Re: [linux-audio-dev] Re: [DATAPOINT] kernels and latencies |
| |
On Wed, Jul 05, 2000 at 12:14:09PM +1000, Andrew Morton wrote: > [ pruned Cc: list ] > > Richard Gooch wrote: > > > > Which leads to my other question: can we "ignore" the interrupt > > (i.e. just update a flag somewhere) for later processing in a process > > context? > > > > Or can we block the interrupt? And hope no-one else is sharing it... > > > > Or do you have some other scheme in mind? > > How important is this anyway? Does the PS/2 mouse get written to > regularly, or just at initialisation/reconfiguration time? > > In fact, what's the point in writing to a mouse? Does it make it move > across your desk?
The PS/2 mouse interface has an incestuous relation to the keyboard controller; they use the same registers. Keyboard controller is writen to regularly in the keyboard interrupt when you press a key. Both have to be serialized.
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |