On Wed, 15 Sep 2010, Gadiyar, Anand wrote: > >> Recent BlackBerry devices don't show this hang so I've been working on > >> the assumption that it's a firmware issue on some older BlackBerry > >> devices. This being the case would this possibly be a new unusual device > >> feature flag to add to usb_usual.h for some BlackBerry devices? > > > > Yes, you could do that. But the flag should merely indicate which type > > of reset to try first; it shouldn't be connected with BlackBerrys > > specifically. After all, other types of devices might need the flag > > too. > > > > Just curious - would it be better to instead update the code the way Toby > has done: try a class-specific reset first, and only if that fails then try a > port reset? Is there a problem with this that I'm not seeing? That's how usb-storage was originally written. It didn't work. Generally sending the class-specific reset would only make things worse -- sometimes to the point where a port reset wouldn't be able to recover and it would be necessary to unplug or even power-off the device. Alan Stern -- 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
