This whole open source move brings up an interesting question. I
know from discussions that some drivers include code that puts QNX
under an NDA. An example is the EIDE driver. This may sound
strange, but apparently QNX had to put in specific patches to make
certain drives work reliably. I wonder how they will handle this?
They could provide a “clean” version, but this would not
really be open source and transparent. On the other hand, they
can’t really violate their NDA.
This whole open source move brings up an interesting question. I
know from discussions that some drivers include code that puts QNX
under an NDA. An example is the EIDE driver. This may sound
strange, but apparently QNX had to put in specific patches to make
certain drives work reliably. I wonder how they will handle this?
They could provide a “clean” version, but this would not
really be open source and transparent. On the other hand, they
can’t really violate their NDA.
I believe the plan is to provide binary blobs (object files) for source
that is covered under an NDA. The idea being that you can still build
the source we can release and link with the pieces that we can’t to
build your final binaries.
I wonder how they will handle this?
They could provide a “clean” version, but this would not
really be open source and transparent. On the other hand, they
can’t really violate their NDA.
Where possible, especially where the NDA is “old”, we’d like to go back
to the people holding the NDA and see if we can agree to end/reduce it.
Something that was “critical business secret” a few years ago, may be
“unimportant trivia” now. Don’t know how successful that will be, though.