On Tue, 23 Aug 2005, David Brownell wrote:
Considering that _only_ the last byte of that response was garbage,
and the others looked just fine, there's no reason to think this is
anything other than some kind of peripheral bug.
There is indeed such a reason. Craig reported that the device
On Tue, 23 Aug 2005, craig qu wrote:
The log shows everything worked okay (if you ignore
the problem of the
illegal status codes) until the computer tried to do
a 127 KB write. Some
devices don't like to transfer more than 120 KB at a
time, maybe that's
the problem you're seeing
I saw an entry in your log where the status was
0xcd. It was for the
second READ_10 command.
You are right. It happens from time to time especially
when read the partition table and mount the device.
However, md5sum a file will give the correct result
always.
Or maybe something fishy
len=0xd actual length=0x0 status=0xff7d
I don't know what those messages are supposed to
mean. Are those status
values the error codes from your HCD? What does
0xff7d = -131 =
-EUNRECOVERABLE mean?
Those messages were printed out in function
usb_stor_bulk_msg by myself. status
On Tue, 23 Aug 2005, craig qu wrote:
len=0xd actual length=0x0 status=0xff7d
I don't know what those messages are supposed to
mean. Are those status
values the error codes from your HCD? What does
0xff7d = -131 =
-EUNRECOVERABLE mean?
Those messages were printed out
On Tue, 23 Aug 2005, craig qu wrote:
Alan,
I dumpped out those 13-byte long packets and found out
that most of the status byte is 0x00, 0x08 and 0x80. I
treated 0x08 and 0x80 as valid status as a work
around, then I am able to read the partition table,
mount the device and copy a small
Alan,
Why is status set to -131 instead of -ECONNRESET?
ECONNRESET is defined as 131 in linux-2.4.30 mips
tree.
EUNRECOVERABLE isn't defined.
The log shows everything worked okay (if you ignore
the problem of the
illegal status codes) until the computer tried to do
a 127 KB write.
On Mon, 22 Aug 2005, craig qu wrote:
Alan,
Yes, I did plugged the storage device into a pc and I
am pretty sure the device works just fine. Also I have
tried with different devices.
Just tried one more time(didnot change any code)and
this time the partition table got recognized. Then,
On Fri, 19 Aug 2005, craig qu wrote:
Hello all,
I am working on a mips based SOC which has usb 2.0
core integrated in. After taking care of memory
mapping and other issues, host controller and usb
device are able to be recognized. However, I got some
SCSI errors so that partition
Hello all,
I am working on a mips based SOC which has usb 2.0
core integrated in. After taking care of memory
mapping and other issues, host controller and usb
device are able to be recognized. However, I got some
SCSI errors so that partition table of the device
cannot be read.
I have
10 matches
Mail list logo
