From: "David Schwartz" <davids@webmaster.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: RE: MODULE_LICENSE usage
Date: Tue, 7 Aug 2007 11:22:50 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAEGLFPAC.davids@webmaster.com> (raw)
In-Reply-To: <20070807161755.28e50234@the-village.bc.nu>
> > My company has been given documentation and the library source under
> > the terms of an NDA with the chipset manufacturer. We are permitted
> > to compile the library and distribute the resultant binary blob, but
> > not release the source to the library.
> >
> > The binary blob is linked into the driver we have written. We don't
> > distribute this compiled module, customers are given the driver source
> > and the library blob, which they compile themselves.
> So you distribute a kernel derived work without following the GPL. I hope
> you've discussed that with your legal team in depth.
What "kernel derived work" would that be?
All he distributes is the binary blob and the source code to his driver. He
hasn't given sufficient information to establish that either of those is a
"kernel derived work". It's certainly possibly that they might be and
sensible to caution him that he's breaking the rules if they are, but you
can't establish that he's not following the GPL.
Of course, he would have a definitely problem if he, or anyone else,
distributed the resulting binary.
DS
next prev parent reply other threads:[~2007-08-07 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 7:53 MODULE_LICENSE usage Nathan Williams
2007-08-06 8:21 ` Jan Engelhardt
2007-08-06 8:24 ` Alan Cox
2007-08-06 10:41 ` Remy Bohmer
2007-08-06 12:25 ` Krzysztof Halasa
2007-08-06 15:22 ` David Schwartz
2007-08-07 3:29 ` Nathan Williams
2007-08-07 7:17 ` Arnd Bergmann
2007-08-07 15:17 ` Alan Cox
2007-08-07 18:22 ` David Schwartz [this message]
2007-08-07 18:22 ` David Schwartz
2007-08-07 19:20 ` Krzysztof Halasa
2007-08-07 20:02 ` Alan Cox
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=MDEHLPKNGKAHNMBLJOLKAEGLFPAC.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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