Is there a bug in the USB code for 2.4.18-14 for SCSI/BULK? I have written to the list a couple of times before, but was slightly off in what the issue was. I have a TOSHIBA/DVD-ROM SD-R5002, packaged by Melco. The DVD-ROM is attached to a Melco Inc. USB2-IDE Bridge.
When scan_scsis_single from drivers/scsi/scsi_scan.c does the inquiry, the first byte in the request_buffer is 0x13, which is an unknown device. The rest of the request_buffer is also corrupted. But, when dvdrecord scans with libscg, the scsi inquiries show the proper results with a device of 0x05 and the proper Vendor/Product strings. The differences between scsi_mod and scg behavior seem to be: 1) scg does a test unit ready before the inquiry, but scsi_mod does not 2) scg requests 36 bytes and then 96 bytes, but scsi_mod requests 255 bytes I hacked scsi_scan.c so that the inquiry only requests 254 bytes, and now the scsi inquiry from scsi_mod also returns the correct results. Is there a bug in my device? or is there a bug in the usb-storage code? What is the best way to fix/patch this? I am happy to do testing and send logs/configuration/etc. as needed. Thank you, Aaron Sterr ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
