Hi Greg, I've received a number of bug-reports from users related to uas on ASM1051 chipset using devices. After some searching around I've managed to get myself an ASM1051 device. As a result I've spend the last 4 days trying to get the ASM1051 chipset to work. After some initial success which makes it work with most disks I've laying around (patch 1), I hit problems with one disk where it just would not work. To makes matters worse the ASM1051 chipset shares its usb-id with older versions of the ASM1053, which works fine with all disks. So I've come up with a patch which disables uas on all ASM1051 devices and on some ASM1053 devices. Both the need to blacklist and the actual blacklisting code are less then satisfactory, esp. after 4 days of work. But this is the best I can come up with :| It seems that older uas-bridge chips and xhci controllers streams support are suffering from quite a few hw bugs, and that blacklisting is the best we can do. Regards, Hans -- 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
