Hi, On 06/15/2012 08:20 PM, Alan Stern wrote:
As we can see from recent bug reports, a lot of USB mass-storage devices cannot handle READ CAPACITY(16) commands properly. They send back garbage and are unusable as a result. Should we go ahead and set a flag on all these devices, telling the sd driver to try READ CAPACITY(10) first? That's a lot easier than adding more and more entries to unusual_devs.h.
That certainly sound reasonable to me. Note that the 071b:3203 really needs the US_FL_NO_READ_CAPACITY_16 flag though, as it wrongly reports a capacity of -1 when there is no sd card in its slot, and in response to that the kernel tries READ CAPACITY(16) and things go downhill from there... 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
