> > As things stand now, we don't handle resets well. A device can have
> > multiple drivers bound to multiple interfaces; when any one of them
> > requests a reset it will affect all the others but they have no way to
> > know what's going on. Likewise, if a hub is reset it automatically has
> > the effect of resetting all the downstream devices, and the drivers need
> > to know about it.
>
> Again, what's wrong with the current way of dropping everything and
> starting over? I think it's the only sane way, and our existing
> interfaces handle it quite well.
It kills error handling in the storage driver.
Regards
Oliver
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
