On Wed, 29 Jan 2003, Janne Pikkarainen wrote: > >> +UNUSUAL_DEV( 0x0a16, 0x9989, 0x0100, 0x0100, > >> + "IBM", > >> + "IBM USB Memory Key", > >> + US_SC_SCSI, US_PR_BULK, NULL, > >> + US_FL_FIX_INQUIRY ), > > > >> bInterfaceClass 8 Mass Storage > >> bInterfaceSubClass 6 SCSI > >> bInterfaceProtocol 80 Bulk (Zip) > > > > Something does not quite compute. What does the entry do which > > the generic code does not? I see the US_FL_FIX_INQUIRY only. > > Can US_FL_FIX_INQUIRY cure timeouts? May it be better to fix > > something in the generic code instead of ballooning the > > unusual_devs.h? > > I have no idea whatsoever, I'm not a kernel guru, but for me it seems that > US_FL_FIX_INQUIRY does cure at least the timeout that happens with the > memory stick. I rebooted back to unpatched kernel and this is what happens > with the memory stick:
These questions should be directed to Matt Dharm, maintainer for the usb-storage driver. US_FL_FIX_INQUIRY causes the driver not to send INQUIRY commands to the device but to fake a reply instead. Some devices don't respond properly to INQUIRYs and cause a timeout, hence the need for this kludge. I believe the current plan is to phase out this flag; the driver will automatically be able to detect and fix these problems. Alan Stern ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
