From: Matthew Dharm <[EMAIL PROTECTED]>
If it provides multiple LUNs, then it must be using the 'standard'
interfaces. If that's the case, none of the 'standard' class drivers use
the us->extra pointer.
I'm confused.
I have several devices here that read smart media.
All of them need a PBA-LBA translation table.
All of them use more than one lun, for example because
they also read compact flash cards.
So, I don't know about your 'standard', but the us->extra pointer
is really needed.
Also elsewhere us->extra is needed. For example, it is quite
usual to fake a reply to certain SCSI commands. A later
REQUEST_SENSE must then not go to the device, even when the device
can handle the REQUEST_SENSE command, but must give the reply
suitable for the earlier fake command reply. Failure to do so
produces stalls. Where does one keep the fake sense codes to
return in case someone asks for them? Really the info struct
at us->extra is the only reasonable place.
Andries
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
