> Also if the binary only chunk of code is neccessary to make the open
> source bit work then its a derivative work as I understand the
> situation,
The issue is not whether the userspace daemon is a derivative work of any
GPL'd work and therefore must be covered. The issue is whether the kernel
driver and the userspace program are one work or two. If neither is any use
without the other, and the two were designed together, it seems implausible
to argue that they are two works.
A boundary that consists of an API that allows the work on either side to
be interchanged with others and the other work still operate substantially
the same can certainly divide two works. That's why a C program that uses
the standard library can be a separate work from the standard library. Any C
program works with that library, and the library works with any C program.
A boundary custom designed for these two programs, and which is not
intended to allow either program to be replaced with another, would not seem
to do the job.
DS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]