This assumes there *is* documentation.
Posted Oct 9, 2006 23:11 UTC (Mon) by pizza
Parent article: Device drivers and non-disclosure agreements
For documentation to be released, there has to be documentation in the first place. It is fairly common that there is no "programming document" to be released. The internal docs may take the form of a series of web pages, comments in their source code, or other such things.
Producing (useful) documentation takes a lot of time, effort, and money, and when it comes down to it, not many people actually want to be able to hack the hardware directly -- they generally want something higher-level instead.
It's also a question of support. For chips intended to be designed into custom products, there's a lot of documentation, as that helps you sell more chips. But will having open specs help Intel (for example) sell more wireless modules? nope -- but an open driver might.
There are arguments to be made on both sides of the NDA fence, and no simple answer.
to post comments)