On Fri, 20 Jun 2003, Linus Torvalds wrote:
>
> Are you sure that your devices don't just handle READ_6 and SENSE_6 ok?
I'm pretty sure your devices just handle it.
Because adding some debugging code seems to clearly show that when you
moved the setting of "use_10_for_XX" to the scanning phase, you moved it
to _after_ it tries to actually identify the drive. And since it uses mode
sense and "read" to identify the drive status, those commands now won't
work, and the result is crap.
I see:
hub 1-0:0: new USB device on port 4, assigned address 3
usb-storage: USB Mass Storage device detected
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: SanDisk Model: SDCFB-256 Rev: 0811
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 501760 512-byte hdwr sectors (257 MB)
use_10_for_ms clear? Fix it! /* force mode sense 10 */
sda: Write Protect is off
sda: Mode Sense: 06 00 00 00
SCSI device sda: drive cache: write through
sda:use_10_for_rw clear?? Fix it! /* force read 10 */
sda1
Setting use_10 to 1 0 !
Setting use_10 to 1 1 !!
Ie note how the "setting use_10" messages (which are from scsi_scan) come
after we have already tried to use the flags.
Why don't we just initialize both to 1 when we create the device? We
should not wait until scanning.
Linus
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
