> You misunderstand what it's supposed to do. The idea
> is to put the interface into the same state it's in
> before any driver binds to it. There's no reason for
> that to be anything other than atomic: race-free.
Putting it into that state is no problem, but keeping it
in that state is.
> If there's a race binding to some other driver (one
> more appropriate to the application), that race would
> be present in _all_ binding paths ... there should be
> nothing unique to doing it through usbfs.
That exactly is the problem. That 'state' is not a stable
state. If you want to have an unbound device you need
to protect that device from bindinding. Simple unbinding
is a useless concept.
Could you explain yourself more clearly?
Regards
Oliver
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
