So in summary Orico is lying about this particular enclosure 2018-03-16 16:20 GMT+01:00 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > 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 >> support UASP: http://www.jmicron.com/PDF/brief/jms567.pdf >> As mentioned, I have another enclosure (not the same hardware model of >> this one) with exactly the same chipset (even the VID:PID is > > The VID and PID are determined by the firmware, not by the chipset. > >> identical) that show up as UASP capable when attached to the same Atom >> embedded PC USB 3.1 port >> For sure the firmware of the two devices is different >> To recap: the capabilities are shown by the device itself, it is not >> possible that the USB host itself takes the decision to "filter" out >> some capabilities, right? > > Right. The USB host does not filter anything; it just passes data > between the computer and the device. > > Alan Stern > -- 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
