On Tue, Apr 01, 2003 at 09:50:54AM -0500, Alan Stern wrote: > > + us->transport_reset(us); > > srb->result = DID_ABORT << 16; > > return; > > } > > You shouldn't use that patch; it's not correct. The driver isn't supposed > to reset the device after an abort, only after an error (and an abort > doesn't count as an error).
The interesting thing is that in 2.5.x this same condition does trigger a reset, and the device then works. There seems to be some difference in definition of "abort" between 2.4.x and 2.5.x, though. > Based on the kernel log you posted earlier, it looks like your problem may > stem from the use of a START-STOP command. The patch below removes that > command; it's a backport from 2.5. Try installing this and let us know if > it helps. I will try this evening and let you know. -- John ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
