Am Mittwoch, 15. September 2010, 17:29:32 schrieb Gadiyar, Anand: > >> > Perhaps a better question is why the Blackberry fails to respond to the > >> > TEST UNIT READY command in the first place. > >> 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? Windows does not use it. Chances are that there are devices in the wild that crash unrecoverably when confronted with it. Therefore we should use it only as a last resort unless we have specific knowledge we can use it. 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
