Hi,
On Fri, Sep 26, 2014 at 11:15:03AM -0500, Felipe Balbi wrote:
> On Fri, Sep 26, 2014 at 12:06:00PM -0400, Alan Stern wrote:
> > > Any hints will be appreciated.
> >
> > We could implement READ CAPACITY(16) if necessary. But since we don't
> > implement READ(16) or WRITE(16), it seems rather
On Fri, Sep 26, 2014 at 12:06:00PM -0400, Alan Stern wrote:
> > Any hints will be appreciated.
>
> We could implement READ CAPACITY(16) if necessary. But since we don't
> implement READ(16) or WRITE(16), it seems rather pointless.
>
> Are you certain you are interpreting the USBCV output correc
On Fri, 26 Sep 2014, Felipe Balbi wrote:
> Hi Alan,
>
> it seems like newer versions of USB20CV will fail us on the MSC tests
> unless we support READ_CAPACITY(16).
How is that possible? The USB Mass-Storage Class spec doesn't require
the device to support any particular set of SCSI commands.
Hi Alan,
it seems like newer versions of USB20CV will fail us on the MSC tests
unless we support READ_CAPACITY(16).
There is one detail though, looking at the sniffer, CBW comes as:
55 53 42 43 43 59 45 4C 00 00 00 00 00 00 0A 2F 00 00
00 00 00 00 00 80 00 00 00 00 00 00 00
so SCSI cmd opcode i
