mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: RE: MODULE_LICENSE usage
Date: Mon, 6 Aug 2007 08:22:48 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKOEOJFOAC.davids@webmaster.com> (raw)
In-Reply-To: <b4e196fa0708060053x65f0b1d3m50c62206cb65e016@mail.gmail.com>


> I'm working on a driver for an ADSL modem which requires the use of a
> binary library from the chipset manufacturer.  All my source code is
> GPL, so that others are free to distribute and modify the driver.
> After asking the FSF for advice and working through their FAQ, I've
> given permission for the binary library file to be used with the GPL
> source code and be re-distributed with it.
>
> I would like to know if I'm permitted to use
> MODULE_LICENSE("GPL") in my module.

I don't see any reason you cannot include the line 'MODULE_LICENSE("GPL")'
in the source code for your module so long as that source code is not a
derivative work of the binary. Whether or not you can distribute the
resulting binary is, however, a complex legal question.

> Additionally, I'm unsure of what is the meaning of
>
> "GPL and additional rights"     [GNU Public License v2 rights and more]
>
> Is it correct to say that my driver is licensed under GPL with
> additional rights to use the binary library file?

No. The "additional right" to use the binary library file is not a right
under which your driver is licensed, so there are no additional rights to
your driver. The binary library itself is offered under rights much less
than the GPL.

What exactly is the license under which the binary is offered? If it's "may
be used with your driver" then you may have some interesting GPL issues when
people want to modify your driver and continue to use the binary firmware
with it.

Does this "binary library" actually run on the host computer? Or is it
firmware that runs on the modem only? Does it actually link in to the
driver?

DS



  parent reply	other threads:[~2007-08-06 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06  7:53 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 [this message]
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
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=MDEHLPKNGKAHNMBLJOLKOEOJFOAC.davids@webmaster.com \
    --to=davids@webmaster.com \
    --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

all inboxes | Powered by JetHome®