On Thu, 2017-08-24 at 17:24 -0700, Greg KH wrote: > On Thu, Aug 24, 2017 at 02:05:22PM +0200, Massimo Burcheri wrote: > > From lsusb -vv: > > > > Bus 004 Device 005: ID 174c:5106 ASMedia Technology Inc. ASM1051 SATA 3Gb/s > > bridge > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 3.00 > > bDeviceClass 0 > > bDeviceSubClass 0 > > bDeviceProtocol 0 > > bMaxPacketSize0 9 > > idVendor 0x174c ASMedia Technology Inc. > > idProduct 0x5106 ASM1051 SATA 3Gb/s bridge > > The product id matches that of the ASM1051, so why would the kernel > ignore what the firmware told it? > > What is the product id that you think this device should be reporting > instead? For sure the device chip has written ASM1153 on it and that is exactly matching the information I got from the manufacturer service: techsupport-de@xxxxxxxxxxxxxxxxxx I'm not sure why the idProduct reports something different. Is there any other obvious difference between this and a real ASM1051? How can we proceed here? For testing could we force it to be detected as ASM1153 to see if UAS is working? Would there be any benefit of reading out the device with the native Windows drivers? At least with these UAS was claimed to be supported, haven't tested yet. Best regards, Massimo
Attachment:
signature.asc
Description: This is a digitally signed message part
