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
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
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
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
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
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
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
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
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
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
; > There's been some speculation that the PS/2 mouse problem could be due to
> > high interrupt latency for non-fast interrupt handlers (especially ones
> > not MPSAFE) in 5.x. I think it would make a lot of sense for us to push
> > Giant off both the PS/2 mouse and s
Robert Watson wrote:
There's been some speculation that the PS/2 mouse problem could be due to
high interrupt latency for non-fast interrupt handlers (especially ones
not MPSAFE) in 5.x. I think it would make a lot of sense for us to push
Giant off both the PS/2 mouse and syscons inte
12 matches
Mail list logo
