mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* help: use of third party kernel modules: license issue?
@ 2003-06-06 23:57 J C
  2003-06-07  0:53 ` Alan Cox
  0 siblings, 1 reply; 2+ messages in thread
From: J C @ 2003-06-06 23:57 UTC (permalink / raw)
  To: linux-kernel

How does the Linux GPL license apply to third party, binary modules in
a case where our custom core kernel code uses proprietary, third
party, "binary only" module interfaces?

My company is developing a telecoms product using Embedded Linux. We
are modifying core kernel components to implement some of our
product's features. We aren't using kernel modules for our own code --
we know and accept that our source code changes must be made available
under the terms of the Linux license.

Our problem is that we'd like to use a particular network processor
that comes with a closed-source kernel module from the chip
vendor. The kernel module provides a sophisticated set of API
functions for configuring and using the chip. The vendor intends the
kernel module to be used as a "chip driver API", exporting a bunch of
API functions for use by customer code. However, we (the customer)
would like to call those API functions directly from our own core
kernel modifications. The chip vendor, however, expected its customers
to implement their drivers in their own binary only, custom kernel
modules. Are we putting the "binary only" license of the third party
module at risk if we call its functions from our core kernel
modifications?

We can argue that the chip vendor's binary only module is not a
"derived work" of our modifications -- we just use the published API
of the binary module.

I've seen several statements saying that it is specifically not
allowed to make open-source core kernel changes in order to use a
proprietary, closed-source kernel module. In this particular case, it
might look like this is what we're doing since we call functions of
the binary kernel module from our open-source core kernel
modifications. But we are not making our core kernel code changes in
order to use the proprietary kernel module; we simply want to use the
chip.

Any comments on where we stand on this?

Thanks

JC

_________________________________________________________________
Find a cheaper internet access deal - choose one to suit you. 
http://www.msn.co.uk/internetaccess


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: help: use of third party kernel modules: license issue?
  2003-06-06 23:57 help: use of third party kernel modules: license issue? J C
@ 2003-06-07  0:53 ` Alan Cox
  0 siblings, 0 replies; 2+ messages in thread
From: Alan Cox @ 2003-06-07  0:53 UTC (permalink / raw)
  To: J C; +Cc: Linux Kernel Mailing List

On Sad, 2003-06-07 at 00:57, J C wrote:
> How does the Linux GPL license apply to third party, binary modules in
> a case where our custom core kernel code uses proprietary, third
> party, "binary only" module interfaces?

Linux the kernel is subject to the GPL license. The GPL license is 
absolutely clear what it applies to, which is any derivative work.

So the question you need to answer is "Is this a derivative work". For
user space its easy and to be clear the kernel explicitly clarifies it
doesn't regard user space as that. For kernel changes its a hard
question and you need to ask someone who studies the issue - thats not
a programmer (we just think we know ;)) but a lawyer.



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-06-07  0:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-06 23:57 help: use of third party kernel modules: license issue? J C
2003-06-07  0:53 ` Alan Cox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®