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 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? 2018-03-16 15:53 GMT+01:00 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > 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 the firmware, maybe just the capability >> My question was more to see if there is already something in the >> USB-STORAGE that allow it or if we may endup in another "quirks" for >> addressing these problem > > It's not just a question of binding the uas driver to the device. The > driver has to know which USB endpoints to use for sending/receiving > data and status, and that information is contained in the missing > firmware. > > Without those values, even if you could somehow bind the driver to the > device, the driver wouldn't be able to communicate with it. > >> Honestly, with all the concern I can have about Orico, if they advice >> the device as UASP capable and the chipset support it, I think it >> should really support it in the end > > How do you know that the chipset supports UAS? > >> The device is this one: http://www.orico.cc/goods.php?id=6538 >> Is it possible that the USB host (in my case it is a modern Intel USB >> 3.1 controller from an Atom embedded PC) play a role in this? > > That is possible. Maybe the chipset supports UAS only when it runs at > USB-2 high speed (480 Mb/s) but not at USB-3 SuperSpeed (5 Gb/s). > >> I have another Orico multy bay, older, same JMS567 chipset that show >> up as UASP capable > > 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
