On Wed, 14 Feb 2007 [EMAIL PROTECTED] wrote: > It seems to me that ehci-hcd itself should perhaps retry a transaction > immediately--at least a couple of times--if it gets QTD_STS_MMF. If > that is wrong for some reason, it might be nice if there was some way > for hid-core (et al?) to know what's going on so it could opt to > resubmit the URB right away--or at least not reset the device so > hastily--if this is the cause of the URB failure... -EPROTO covers > several other errors, too.
I don't see any point in returning an error code that means "The HC messed up on this URB, please resubmit it". For one thing, you'd have to change every single USB driver to make them recognize the new code. Far better to have the HCD handle things all by itself. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel