On Sun, Feb 10, 2008 at 11:00:33PM +0100, Peter Rasmussen wrote: > Is it possible to distinguish such a failure from a bad implementation > of a device's USB stack? > If it is, it would be great to also be told in some way that doesn't > require me to know USB so intimately.
Not really. You can make an educated guess based on the aggregate
information, but there is no solid way to tell the difference.
In this case, I find a bad cable unlikely. The cable would have to be
flakey only during the data phase of a command.
> E.g.: Connection Error: You seem to have a bad cable
> Registration Error: There are problems with registering the
> device. It may have a bad XYZ command processing
There are some messages like that for errors that generally only happen
with bad cables. This is not one of those.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
G: Let me guess, you started on the 'net with AOL, right?
C: WOW! d00d! U r leet!
-- Greg and Customer
User Friendly, 2/12/1999
pgpiuyb8UysVC.pgp
Description: PGP signature
