The most correct solution here is to subclass IOBlockStorageDevice.
IOBlockStorageDevice serves as a template for developers to "fill in"
with the specifics of their transport, whether it be RAM, ATA, SCSI,
USB, disk images, etc. We made IOBlockStorageDevice an abstract class
for exactly this reason.
actually I looked at this sample, but was under the impression that
even though it creates a RAM drive, it's purpose is quite different.
For my RAM drive I'm not dealing with SCSI at all, so it seems not
correct to use this example as base. It seems to introduce
complexity to me (having to deal with SCSI stuff) and to the system
as all read/write requests will be packaged as SCSI CDBs.
Overriding something at a much higher level like IOMedia, as Tony
suggested, is probably best suited for my needs.
Thanks
Regards
Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
