Lennart Augustsson wrote:
> The EHCI driver lacks support for interrupt isochronous transfers.
> Interrupt transfers are not difficult, it's just not done.

What does this mean? Certain devices not working, devices
randomly locking, or kernel panic?

> There might also be some issues with the data toggle, I never
> managed to test if that works properly under all conditions.

What effect would have an incorrectly cleared/pending data toggle?
 
> The meaty part to implement is the support for USB 2.0 hubs.
> They are quite compolicated since the need to be able to do
> "transaction translation", i.e., converting to/from USB 2 and USB 1.
> So the hub driver needs to handle and schedule these things.

I somehow thought this is done by the hardware. Why would
the driver need to be involved?
 
Jaromir
-- 
Jaromir Dolecek <jdolecek@NetBSD.org>            http://www.NetBSD.cz/
-=- We should be mindful of the potential goal, but as the Buddhist -=-
-=- masters say, ``You may notice during meditation that you        -=-
-=- sometimes levitate or glow.   Do not let this distract you.''   -=-