Am Mittwoch, den 21.03.2018, 17:09 +0100 schrieb Greg KH:
> > I'm guessing it doesn't quite match up with the rules already in place
> > in uas-detect.h
>
> That device has a quirk already as a "normal" usb-storage device.
> Oliver added it back in 2013 with 32c37fc30c52 ("usb-storage: add quirk
> for mandatory READ_CAPACITY_16")
That should cause different symptoms.
> > Looks like it's an ASM1053 that can't do UAS
>
> No, it's not a UAS device, is someone trying to recycle device ids to do
> different things now? That's not good :(
The second interface looks like UAS though. The second interface looks
like UAS though. What exactly does happen when you ennumerate?
Dmesg please.
We may need some exotic logic for these devices.
Regards
Oliver
--
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
