> Implementation of USB Attached SCSI Protocol per UASP Specification > (Rev.1, July 9, 2008). Below is the list of the enhancements made to > the usb-storage driver. This is an incredibly old version of the draft review document. 1) You should be using the spec document T10/2095-D, "UAS", and 2) you should be using the latest revision, revision 4, dated March 9, 2010. > Limitations: > > - Considered that the endpoint descriptors are received from the device > side in the following order: > - Command endpoint descriptor. > - Bulk in endpoint descriptor. > - Bulk out endpoint descriptor. > - Status endpoint descriptor. Please don't rely on this order. See above. The pipe descriptors are defined in the UAS spec. > - The max number of streams are not retrieved through the superspeed > endpoint companion descriptor and are fixed to 2 streams per > endpoint. A UAS driver must not assume this. > - Device supported LUNs are assumed to be 1. A UAS driver has nothing to do with the number of LUNs. A UAS driver is LUN agnostic, being a SCSI protocol implementation over a transport, USB in this case. > - Concurrent processing of SCSI commands is not yet tested due to due > to some device limitations. The driver is currently set to process > only 1 command at a time. Which device? What device is this? A UAS driver is command number agnostic for the same reasons as outlined above. > - Abort task, Reset nexus task management functions, as well as some > error conditions and recovery situations are not yet tested. Those should be initiated only by the SCSI layer, transported over the UAS protocol to the I_T_(_L) nexus. Thanks, Luben -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
