On Sat, 22 Mar 2003, Matthew Dharm wrote: > > As I see it, SCSI commands break down into two basic categories: common > and uncommon. Common things (basic read and write, 36-byte INQUIRY, eject, > etc.) are all fine, but the 'uncommon' things (checking cache type, > 255-byte INQUIRY, etc) cause problems. I'm trying to find a way to choke > off the problematic commands without having to write code to recognize what > is being sent (and choke it off) based on what is in the command bytes. > > I'm open to suggestions.
How about making the SCSI stuff pass a "common" flag (or "required") down with the command? Then, a emulated thing could just decide to punt all commands with an immediate failure if they aren't marked "required". That still _allows_ the driver to implement it if it wants to, unlike your previous approach. Linus ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel