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. I noticed that writing to the usbip driver's unbind attribute leaves the device unbound, which is obviously not a good thing. So how should this be properly handled? Thanks, matt -- 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
