##CONTINUE##
Perens begins by noting that most legal disputes over the GPL so far have involved devicemakers. He suggests that in many cases, the smaller product companies that create Linux device firmware fail to inform their clients about the ongoing responsibilities of using GPL-licensed code (such as distributing the license with the product, and making source code available on request).
On Perens' to-do list for would-be GPL software users are:
- Build a partnership of your legal organization and engineering
- Legal-engineering reviews need to happen early
- Don't assume binary drivers are safe -- they're untested legally
- Don't look for loopholes to exploit in open source licenses
- Phone vendors should rally around a common GSM baseband modem stack with a shared license. Currently, they spend "billions" to maintain stacks separately, despite the fact that little if any product differentiation occurs within the stack.
- The dual-processor architecture used in most phones allows a clean separation of proprietary code (such as DRM, the GSM stack) and open source software -- even GPL3-licensed software
- Virtualization is another approach to separating proprietary and open source code, even when run on a single processor. However, virtualization systems are "probably too large" for embedded applications, Perens says.
Perens's essay, "Combining GPL and proprietary software," can be found here.
-----------------------------
BY N/A
Source:LinuxDevices.com
Copyright © 1999-2009 Ziff Davis Enterprise Holdings Inc. All Rights Reserved.
0 comments:
Post a Comment