Enlightening, thanks. Do we therefore want a distinct US_FL_FIX_INQUIRY flag for 2.5/2.6, so that 2.4 needing a blank-rewrite doesn't force 2.5/2.6 to have one as well? I think I hear Matt D saying op x12 Inquiry other than the -x "12 0 0 0 24 0" -i x24 of Windows is now rare in 2.5/2.6 ... I'm not clear on why that means two-mode passthru isn't the best solution for 2.5/2.6 of usb/storage as it is for 2.4/2.5/2.6 of ide-scsi? I do personally speak from a history of writing SG-based apps that prefer raw data. Pat LaVarre -----Original Message----- From: Matthew Dharm [mailto:[EMAIL PROTECTED]] Sent: Mon 12/30/2002 11:14 AM To: Pat LaVarre Cc: Alan Stern; Jason Bowman; [EMAIL PROTECTED]; USB Storage List Subject: Re: [usb-storage] Re: [linux-usb-devel] Fuji FinePix F401 - patch The two-mode passthru is probably the best solution for 2.4 -- that's what ide-scsi does (SCSI emulation for IDE/ATAPI devices). Anything that comes from the SG interface is not rewritten. Of course, I fixed this for 2.5/2.6 by just changing the INQUIRY behavior to start with an op x12 for x24 bytes. In general, we don't want to blanket-rewrite data whenever possible. There are several SG-based apps (cdrecord most notably) which insist on wanting the raw data. Matt ^){([8bAzE&z y!yޞm)rbn^elqz{.n+azV+֭ilqzlX)ߣbn^
