Am Mittwoch, 1. Juni 2005 22:29 schrieb Alan Stern:
> I'm not sure what more you would need beyond checking that dev.driver_data
> != NULL. If the device was physically disconnected then there's no
> problem -- once your driver's disconnect routine runs no other driver is
> allowed to bind to the interface, so dev.driver_data will certainly be
> NULL. Conversely, if the device remained physically connected but your
> driver was unbound and then rebound, the dev.driver_data value would refer
> to the current instance of your private data. There won't be any pointers
> to stale data.
You cannot assume that _your_ driver is bound. Somebody might have kicked
it off the interface precisely to make sure it is not.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
