Looking at the code, there's clear potential.
Just to make sure I understand, the idea of this code is to serve as an
interface between the USB-storage driver and a device-specific reader?
So that any SmartMedia reader only has to implement the various commands
in the ssfdc_info?
If that is the case, then we need to try to make this work. It would
definitely save development effort and kernel size.
Now, what about things like MODE_SENSE, INQUIRY, and
ALLOW_MEDIUM_REMOVAL? Those need to be dummied up on the SDDR. Do any
other devices implement these? If so, these should be made into API's as
well.
Re-reading the mapping:
That's a problem. I'm not familiar enough with the way SCSI works to
know how to tell it that the media changed. And if it knows that the
media changed, will it get the capacity again? If no-one knows the
answer to this off-hand, I'll read the source and find out.
--Rob
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
