|
NDAsNDAsPosted Oct 7, 2007 0:32 UTC (Sun) by man_ls (subscriber, #15091)In reply to: NDAs by addw Parent article: Linux driver project gets a full-time leader The documentation necessary to build a device driver may be mixed with other things, not relevant to how the device works. For example, you might have electronics schematics, competition comparisons, or even future plans for the device. And the company might not want to devote the time needed to separate it. An NDA might specify that the developer may not divulge any information not relevant to the device driver.
(Log in to post comments)
NDAs Posted Oct 13, 2007 12:03 UTC (Sat) by Duncan (guest, #6647) [Link] That future plans clause is the one I've seen mentioned before in thisregard. In several hardware product areas (particularly embedded, think cell phones and some of the individual components they contain), the public lifetime of a product isn't much more than six months. This is far too short a time to get a full driver written, start to finish, and by the time it's out and stable, the product itself has long disappeared and been replaced by new generations, perhaps not entirely different, but enough different so adapting the drivers to match, then testing them, takes yet another hardware generation, and the driver never /can/ catch up with the software, even given reasonably decent support during 100% of the public life of the product. That's especially the case considering the kernel release cycle itself is 2-3 months, so even if development started immediately and went without a hitch, it could be half the product's publicly available life cycle before drivers are available in a released kernel!
Enter these NDAs and developers willing to sign them; willing to work
Duncan
|
Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds
Powered by Rackspace Managed Hosting.