On Thu, 1 Apr 2010, Matthew Dharm wrote: > On Thu, Apr 01, 2010 at 02:23:37PM -0700, Paul Zimmerman wrote: > > If it was a whole new driver, would there be any difficulty with attaching > > to either a BOT device or a UAS device, depending on the device's subclass > > code? Would the correct mass-storage driver get invoked somehow? > > It looks like it. Based on the patch, UAS devices have a different > subclass code. Each driver advertises a specific list of descriptor codes > and/or VID/PID that it accepts. > > Currently, usb-storage does not advertise the UAS code. The new UAS driver > would, and thus would get loaded. We can only hope that the vendors who design UAS interface chips will invest enough resources to avoid all the bugs that have plagued usb-storage. In fact, we could even hope that nobody would bother to implement UAS for anything less than USB-3.0. The additional cost of going to SuperSpeed might be enough to justify the added expenses of fixing the firmware bugs. But I wouldn't bet on either of these... Alan Stern -- 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
