archive mirror
 help / color / mirror / Atom feed
From: "john smith" <>
Subject: Re: Kernel modul licensing issues
Date: Mon, 1 Dec 2003 01:27:58 +0100 (MET)	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 2808 bytes --]

Hi Manfred

Thanks for your reply.

You wrote:
> Wrong mailing list.
> You must find a lawyer, and he'll answer your questions.

Of course, the company I'm working for will contact their
lawyers before releasing anything for linux. The reason
because I'm asking here is to get an idea of your attitude
regarding binary kernel modules in this specific scenario
and your interpretation of the GPL in my case.
I'd be glad if we can support linux but if it's not possible
due to unclear legal interpretations of the GPL we certainly

> 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.

Thanks for this information. I guess we can live without rcu.

> 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.

Well, the algorithm has been developped totally independent from
linux. It also works under other OS's without any adjustments apart
from alloc and locking stuff.

The fact that it receives kernel data as input IMO does not make it
tightly coupled to the linux kernel since the algorithm does not even
know or care what it receives as input (at least as far as kernel data
is concerned). It basically considers kernel data: char[]

> "Derived work" is a legal term, your lawyer might be able to figure out 
> if your combination is a derived work.

As you stated later the interpretation differs from country to country
and though I'm no lawyer (and haven't talked to one myself yet regarding
this issue) I very much doubt that the interpretation is that clear even
for a "fixed" country.

> 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.

Well, the same holds for the algorithm module since it simply does not
need any kernel support apart from alloc and locking (as I already 
stated). Only the frontend is different from OS to OS.

I'd appreciate it very much if you and others contribute their opinion
to this topic. Basically, I believe that if we're not allowed to release
the algorithm as binary kernel module then you'd surely find a
reason why nvidia and others in fact also infringe the GPL.



Neu bei GMX: Preissenkung für MMS-Versand und FreeMMS!

Ideal für alle, die gerne MMS verschicken:
25 FreeMMS/Monat mit GMX TopMail.

+++ GMX - die erste Adresse für Mail, Message, More! +++

             reply	other threads:[~2003-12-01  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  0:27 john smith [this message]
2003-12-01  0:57 ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2003-12-01 10:58 john smith
2003-11-30 13:23 Manfred Spraul
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Kernel modul licensing issues' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).