On Tue, 13 Jun 2006, David Brownell wrote:
> On Tuesday 13 June 2006 11:08 am, Alan Stern wrote:
> > > > This works okay with external hubs that are polled only 4 times per
> > > > second
> > > > and with edge-triggered status interrupts (like UHCI and, I assume,
> > > > EHCI).
> > > > But wit
On Tuesday 13 June 2006 11:08 am, Alan Stern wrote:
> > > This works okay with external hubs that are polled only 4 times per second
> > > and with edge-triggered status interrupts (like UHCI and, I assume,
> > > EHCI).
> > > But with level-triggered interrupts it will fail badly. Khubd will
>
On Tue, 13 Jun 2006, David Brownell wrote:
> On Monday 05 June 2006 12:54 pm, Alan Stern wrote:
> > Dave:
> >
> > I just realized there is another problem connected with level-triggered
> > root-hub status interrupts. It probably hasn't affected your tests but
> > the potential is there.
> >
>
On Monday 05 June 2006 12:54 pm, Alan Stern wrote:
> Dave:
>
> I just realized there is another problem connected with level-triggered
> root-hub status interrupts. It probably hasn't affected your tests but
> the potential is there.
>
> Two routines in the hub driver can cause port-change event
Dave:
I just realized there is another problem connected with level-triggered
root-hub status interrupts. It probably hasn't affected your tests but
the potential is there.
Two routines in the hub driver can cause port-change events to occur
outside the scope of khubd: usb_reset_device and usb_
