Messages in this thread | | | Subject | Re: freed_symbols [Re: People, not GPL [was: Re: Driver Model]] | Date | Mon, 6 Oct 2003 20:28:46 +0200 | From | Pascal Schmidt <> |
| |
On Mon, 06 Oct 2003 03:40:05 +0200, you wrote in linux.kernel:
> A much more obvious example than the SCM one is a device driver or a module. > That's so cut and dried it isn't even open to debate in the eyes of the > law. It's a hard and fast boundary, the GPL can't cross it no matter what > people think or want (on either side).
Huh? How is a driver an independent work under the definition you gave? I can't take the Linux kernel out and insert the driver into another kernel and have it still work. Only the opposite is true - the kernel would run without the driver, and therefore the kernel is not a derived work of the driver and can't be subject to license terms of the driver.
The kernel doesn't have a defined interface for drivers. It changes a lot at least during a development series. A driver is not independent from the kernel running under it because it has to be changed quite often to adapt to the changing internal kernel interfaces.
You can't even change the Linux kernel version you're using and have the same driver still work for you. So by your definition, a driver is at least in part a derived work of the kernel.
Now, if the driver has an internal abstraction layer that seperates the kernel side of things from the real work the driver does, I would agree that only the abstraction layer is a derived work and has to be GPL'd, not the rest of the driver.
Most drivers don't work that way because of the additional overhead.
-- Ciao, Pascal - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |