READ_CAPACITY_16 does not have anything to do in blacklisting via
quirks the device to usb-storage
I have checked it in 4.9.86 and it is not quirked to usb-storage:
/* Reported by Oliver Neukum <oneukum@xxxxxxxx> */
UNUSUAL_DEV( 0x174c, 0x55aa, 0x0100, 0x0100,
"ASMedia",
"AS2105",
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NEEDS_CAP16),
2018-03-21 17:09 GMT+01:00 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>:
> On Wed, Mar 21, 2018 at 03:39:06PM +0000, Mike Lothian wrote:
>> Hi
>>
>> I'm running kernel 4.9.86 on my router
>>
>> I have to:
>>
>> echo 174c:55aa:u > /sys/module/usb_storage/parameters/quirks
>>
>> To get it to work correctly
>>
>> I'm attaching the output of lsusb -v
>>
>> 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")
>
>> 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 :(
>
> thanks,
>
> greg k-h
> --
> 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
--
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
