> > usb-storage: Command READ DISC INFORMATION (10 bytes) > > usb-storage: 51 00 00 00 00 00 00 00 24 00 00 00 > > usb-storage: Bulk command S 0x43425355 T 0xac Trg 0 LUN 0 L 36 F 128 CL 12 > > usb-storage: Bulk command transfer result=0 > > usb-storage: usb_stor_transfer_partial(): xfer 36 bytes > > usb-storage: usb_stor_bulk_msg() returned 0 xferred 34/36 > ^^^^^ This appears > to be the firmware deficiency. Unit promised 36 bytes, while only 34 were > available for transfer...
Minor clarificaiton. Note that 34 is actually "politically" correct value according to MMC specification. Specification says that size of returned data structure should be 32+8*N. This doesn't include 2 byte header which essentially contains the length of structure. In other words compliant reply from unit should be 2+32+8*N bytes large, or 34 when N=0. The firmware most likely erroneously accounts header twice... A. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
