From: Manfred Spraul <manfred@colorfullife.com>
To: "john smith" <john.smith77@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel modul licensing issues
Date: Sun, 30 Nov 2003 14:23:49 +0100 [thread overview]
Message-ID: <3FC9EF65.8040807@colorfullife.com> (raw)
John wrote:
>I have some licensing issues with the linux GPL and the implications
>on a project which incorporates partial non-GPL code which I want
>to release as linux kernel module.
>
>
Wrong mailing list.
You must find a lawyer, and he'll answer your questions.
>I have implemented a proprietary algorithm in user space which I'm not
>allowed to release under the GPL. From a _technical_ point of view I
>could compile the code as kernel module which offers a certain API.
>Note that the kernel module would have only very limited dependency
>on the kernel, i.e. apart from memory allocation functions (kmalloc,
>kfree, vmalloc, vfree) and potentially some "locks" (spinlock, big
>reader lock or rcu) the code is totally independent from the kernel.
>
RCU is a patented algorithm - mention that to your lawyer. Your creation
must not be derived from the kernel (because creating derived works is
an exclusive right of the copyright owner, and you don't have and won't
get a permission), and it must not infringe the RCU patents.
>As far as the interaction with the algorithm API is concerned the
>frontend submits kernel data structures to the algorithm module _but_
>since the algorithm has no declaration of kernel structures it does
>neither use nor modify the kernel data. It's just stored and returned
>to the user via certain API functions.
>
You have written an algorithm module that is tightly coupled to the
Linux kernel, and you think it's not derived from the kernel, correct?
As a non-lawyer, it'd say that's wrong.
"Derived work" is a legal term, your lawyer might be able to figure out
if your combination is a derived work.
The drivers that are more or less accepted as not-derived run on
multiple operating systems - e.g. the nvidia ethernet driver uses the
same source code for Windows and Linux, and nvlib.o works on Linux and
FreeBSD.
--
Manfred
P.S.: You might need a team of lawyers: the definition of derived work
differs from country to country.
next reply other threads:[~2003-11-30 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 13:23 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 10:58 Kernel modul licensing issues john smith
2003-12-01 0:27 john smith
2003-12-01 0:57 ` Valdis.Kletnieks
2003-11-30 12:30 john smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FC9EF65.8040807@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=john.smith77@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).