Am Montag, 20. Juni 2011, 01:18:09 schrieb matt mooney: > Hi, > > This pertains to usbip, but it is really a general usb question. > > So the userspace utility writes to an attribute to identify the device to be > unbound and allow the driver to change its interal state; then, (in what I > believe to be a hack) the utility writes to an attribute of the device in > question to get the usbcore to reprobe the device and issue a disconnect. The driver is disconected as soon as you write to "unbind" > I noticed that writing to the usbip driver's unbind attribute leaves the device > unbound, which is obviously not a good thing. This is absolutely necessary to guarantee user space that it may speak to a device through usbfs without any interference by a driver. In addition we may want to kick drivers off a device while they are not needed. > So how should this be properly handled? It is quite properly handled. Regards Oliver -- - - - SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany - - - -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
