Re: the PS/2 mouse problem

2003-11-11 Thread Morten Johansen
Scott Long wrote: Bruce Evans wrote: On Sat, 8 Nov 2003, Morten Johansen wrote: Scott Long wrote: Bruce Evans wrote: [... possibly too much trimmed] The problem here is that the keyboard controller driver tries to be too smart. If it detects that the hardware FIFO is full, it'll drain it in

Re: the PS/2 mouse problem

2003-11-11 Thread Scott Long
Bruce Evans wrote: On Sat, 8 Nov 2003, Morten Johansen wrote: Scott Long wrote: Bruce Evans wrote: [... possibly too much trimmed] The problem here is that the keyboard controller driver tries to be too smart. If it detects that the hardware FIFO is full, it'll drain it into a per-softc, per-fu

Re: the PS/2 mouse problem

2003-11-10 Thread Morten Johansen
Bruce Evans wrote: On Sat, 8 Nov 2003, Morten Johansen wrote: Scott Long wrote: Bruce Evans wrote: [... possibly too much trimmed] The problem here is that the keyboard controller driver tries to be too smart. If it detects that the hardware FIFO is full, it'll drain it into a per-softc, per-fu

Re: the PS/2 mouse problem

2003-11-10 Thread Bruce Evans
On Sat, 8 Nov 2003, Morten Johansen wrote: > Scott Long wrote: > > Bruce Evans wrote: > >>[... possibly too much trimmed] > > The problem here is that the keyboard controller driver tries to be too > > smart. If it detects that the hardware FIFO is full, it'll drain it into > > a per-softc, per-fu

Re: the PS/2 mouse problem

2003-11-09 Thread Alex Wilkinson
On Wed, Nov 05, 2003 at 08:33:58PM -0700, Scott Long wrote: One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to do. Basically just use t

Re: the PS/2 mouse problem

2003-11-08 Thread Morten Johansen
Scott Long wrote: Bruce Evans wrote: On Fri, 7 Nov 2003, Morten Johansen wrote: Morten Johansen wrote: Scott Long wrote: One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to

Re: the PS/2 mouse problem

2003-11-08 Thread Scott Long
Bruce Evans wrote: On Fri, 7 Nov 2003, Morten Johansen wrote: Morten Johansen wrote: Scott Long wrote: One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to do. Basically just

Re: the PS/2 mouse problem

2003-11-07 Thread Bruce Evans
On Fri, 7 Nov 2003, Morten Johansen wrote: > Morten Johansen wrote: > > Scott Long wrote: > > > >> One thought that I had was to make psmintr() be INTR_FAST. I need to > >> stare at the code some more to fully understand it, but it looks like it > >> wouldn't be all that hard to do. Basically ju

Re: the PS/2 mouse problem

2003-11-07 Thread Scott Long
Morten Johansen wrote: Morten Johansen wrote: Scott Long wrote: One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to do. Basically just use the interrupt handler to pull all of

Re: the PS/2 mouse problem

2003-11-06 Thread Morten Johansen
Morten Johansen wrote: Scott Long wrote: One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to do. Basically just use the interrupt handler to pull all of the data out of the har

Re: the PS/2 mouse problem

2003-11-05 Thread Scott Long
One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to do. Basically just use the interrupt handler to pull all of the data out of the hardware and into a ring buffer in memory, an