On Wednesday 06 September 2006 11:40 am, Joerg Schilling wrote: > Alan, from my understanding you may do this because porting a GPLd driver > to Solaris does neither: > > - cause the Solaris kernel project to include GPLd code as long as the > driver is not essential for running the Solaris kernel. > > Note that the Solaris kernnel is not a monolithic piece of code and > that nobody did e.g. claimed a problem for running GPLd code > on DOS or on the ATARI where no MMU causes the code to run in different > contexts. > > nor: > > - make the Solaris kernel a "derived work" from the GPLd driver. It is > rather the other way. > > If the GPLd driver may be called a separate project/work, I would recommend > to GPL all code that is needed for the port and then just use the driver on > OpenSolaris.
If you have a CDDL device driver that is written, that can't be taken to Linux, AFAIK. GPL driver coming back to Solaris can't do as it is being used by the kernel. I'm not sure I understand what you're pointing out. Yes, we can have code that co-exists from userland, but I'm looking at the big picture. -- Alan DuBoff - Sun Microsystems Solaris x86 Engineering - IHV/OEM Group _______________________________________________ opensolaris-discuss mailing list [email protected]
