Paulo Marques writes:
About the legal aspects of all this, they have been discussed extensively in the past. It is not about "hey this is just a simple hook", it is all about the derived work concept. This driver does absolutely nothing outside the kernel. It's only purpose is to attach itself to the kernel and to provide the images from the camera to userspace using the kernel ABI's. So you can not say it is not a derived work at all.
(note: the following is not legal advice)
I think you'll find that this is not supported by the copyright law, at least in the United States and in any sane country.
Richard Stallman and The SCO Group might like your interpretation, at least when it serves them, but that doesn't make it the law.
You're completely missing the point. I never said that the pwcx driver copies code from the kernel, and in doing so infringes copyright law.
What I'm saying is that the kernel is distributed with a license that allows you certain rights, and that extending the kernel functionality through closed source drivers is not one of those rights.
What protectable elements of the kernel have been included within the driver? I don't see any. Like we say to SCO, where are the lines of code? Remember, nobody is distributing a kernel with this driver linked in. Merely loading the driver is obviously fair use of the kernel.
(BTW, something which is required for operation is not protectable. See the Sega v. Accolade case. Thus, mere usage of header files won't do. You couldn't even use the C header files on any UNIX system if that were the case. Let's not be silly.)
You're being silly, I've never said anything about header files, nor copied lines of code.
Is it "non-literal copying" that concerns you? Heh. OK. Name the jurisdiction you like, and describe the copyright infringement test accepted by the courts in that jurisdiction.
For example, the US 10th Circuit uses the "abstraction, filtration, comparison" test. The US 9th Circuit uses the "Analytic Dissection" test. There are others. I don't know of any such test under which the closed-source part of the driver could be considered to be a derived work of the Linux kernel. I can hardly imagine one that would make the driver derived without also making Linux derived from UNIX!
So anyway... where are the lines of code?
It is a derived work, not a "copied" work. The point is:
>>This driver does absolutely >>nothing outside the kernel. It's only purpose is to >>attach itself to the kernel and to provide the images >>from the camera to userspace using the kernel ABI's.
In the case of a nvidia driver (for instance) one can argue that the driver was written for another well known closed source operating system, and was latter ported to Linux, so that we can not honestly say that it is a derived work.
Anyway, this is all a big gray area, with darker and lighter tones of gray. So you only get a definite answer in front of a judge.
This whole discussion has been beaten to death in the past. I really don't want to go through that again. Although I have not been directly involved in the past discussion, the traffic in LKML is high enough that it doesn't need another one of those threads...
-- Paulo Marques - www.grupopie.com
To err is human, but to really foul things up requires a computer. Farmers' Almanac, 1978
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
