Hello!
I would like to know more about the architecture of io-cam.so, devb-, and
cam-.so
The description in the System Architecture Guide is good, as well as the
Utilities Reference which describes how to invoke the devb-* drivers and
pass options to cam-disk.so, cam-cd.so, etc.
However, I would like to write my own devb-*.so to support a special purpose
HBA (host bus adapter). As well, I would like to write a devb-changer.so
for jukeboxes, and possibly a cam-passthru.so for pass-through operation.
Is QSSL planning to release any info like they did with the DDK for the
network and other drivers?
What is(are) the entry point(s) that a devb-* driver provides to io-cam.so ?
What are the data structures that are passed?
Any help would be greatly appreciated.
Alain Achkar
AFAIK, QNX is going to change block I/O architecture with next release,
which is supposedly due this fall. Which is why this part of system does not
have any DDK or even published interface.
In the new architecture (again, AFAIK) io-blk will be executable and
devb-xxx will be DLLs, very much like io-net/io-audio/io-graphics scheme.
Supposedly it will provide FreeBSD-style CAM interface with passthru and
will also have public DDK.
They were very reluctant to release information about current architecture
this far, I suspect you will have to wait unless you have an immediate
business case (and then you should be calling your sales rep, not talking
here).
“Alain Achkar” <aachkar@storagequest.com> wrote in message
news:9joalm$7d8$1@inn.qnx.com…
Hello!
I would like to know more about the architecture of io-cam.so, devb-, and
cam-.so
The description in the System Architecture Guide is good, as well as the
Utilities Reference which describes how to invoke the devb-* drivers and
pass options to cam-disk.so, cam-cd.so, etc.
However, I would like to write my own devb-*.so to support a special
purpose
HBA (host bus adapter). As well, I would like to write a devb-changer.so
for jukeboxes, and possibly a cam-passthru.so for pass-through operation.
Is QSSL planning to release any info like they did with the DDK for the
network and other drivers?
What is(are) the entry point(s) that a devb-* driver provides to io-cam.so
?
What are the data structures that are passed?
Any help would be greatly appreciated.
Alain Achkar