On Monday, June 20, 2011 08:35:40 PM matt mooney wrote: > Okay, let me clarify to make sure I understand. The userspace utility should > write to unbind, which it is currently not doing, and should also continue > writing to an attribute of the device, which is to be unbound from the driver, > in order to initiate a reprobe? > > That is: > > (1) read some attribute of the device and save it (in this case > bConfigurationValue) This is optional. The configuration is maintained unless you change it explicitly. > (2) write to the necessary attribute of the driver and then to unbind Yes > (3) write the attribute read in (1) back to the device, which is now unbound and > without a driver, to initiate the reprobe. Well, no. To reprobe you write to "bind" which is an attribute of the driver and in fact in the same directory as "unbind" Regards Oliver -- 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
