So in summary Orico is lying about this particular enclosure
2018-03-16 16:20 GMT+01:00 Alan Stern :
> On Fri, 16 Mar 2018, Menion wrote:
>
>> Hi Alan&Greg
>> Yes, sorry, I thought it was simpler. I confirm that also the 4
>> endpoints required for UAS operation are missing, so everything is
>> co
On Fri, 16 Mar 2018, Menion wrote:
> Hi Alan&Greg
> Yes, sorry, I thought it was simpler. I confirm that also the 4
> endpoints required for UAS operation are missing, so everything is
> coherent to say "no UASP sorry"
> From the VID:PID you can see that the chipset is a JMS567, which does
> suppo
Hi Alan&Greg
Yes, sorry, I thought it was simpler. I confirm that also the 4
endpoints required for UAS operation are missing, so everything is
coherent to say "no UASP sorry"
>From the VID:PID you can see that the chipset is a JMS567, which does
support UASP: http://www.jmicron.com/PDF/brief/jms56
On Fri, 16 Mar 2018, Menion wrote:
> Hi Greg
> Yes Orico is a kind of crap, but it is not so easy to find those kind
> of devices.
> My concern is that we may see one of this crappy implementation of
> device, such that it actually supports perfectly UASP but they
> "forgot" to set something in th
sSupported 0x000e
>> Device can operate at Full Speed (12Mbps)
>> Device can operate at High Speed (480Mbps)
>> Device can operate at SuperSpeed (5Gbps)
>> bFunctionalitySupport 1
>> Lowest fully-functional device speed is Full Speed (1
e at High Speed (480Mbps)
> Device can operate at SuperSpeed (5Gbps)
> bFunctionalitySupport 1
> Lowest fully-functional device speed is Full Speed (12Mbps)
> bU1DevExitLat 10 micro seconds
> bU2DevExitLat 32 micro seconds
> Device Status:
cibly bind a
device to UAS?
Bye
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
