mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Tue, 6 May 2003 23:31:27 +0100	[thread overview]
Message-ID: <20030506223127.GD6284@mail.jlokier.co.uk> (raw)
In-Reply-To: <1052250792.1983.160.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote:
> > What if this new-fangled other kernel is open source, but BSD license
> > instead?  Would that also anger the kernel developers?  (As I suspect
> > a closed-source binary kernel would, even if one could get away with it).
> 
> Then the combined result would be a GPL'd product. You can do that now.
> Add BSD code to GPL and the result comes out GPL.

I disagree - as Pavel said, "if it's running in your kernel's
userspace", the GPL applies only to the thing running in that
"userspace", not to the whole combined machine.

> > Then, you can (a) rewrite everything, using the knowledge you gained
> > from reading the various open source drivers, or (b) just use those
> > drivers, and save a lot of effort.
> 
> The GPL says "you can use them if your final new result is GPL", the BSD
> world says "Hey go do it, just say thanks". Its probably a lot simpler
> to use the FreeBSD code if you don't want a GPL result.

I understand the licensing in unambiguous causes, and I'm not trying
to find loopholes in awkward corners.  I'm just observing that, as
closed-source binary modules are de facto accepted (with some funky
rules about which interfaces they can use), the same in reverse
_ought_ to be accepted to the same degree: Linux (and other) GPL'd
modules as satellites around a non-GPL kernel.

> For myself I'd be willing to discuss relicensing code in some cases but
> there is little that has a single author. 

Thanks.

-- Jamie


  reply	other threads:[~2003-05-06 22:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 16:42 Jamie Lokier
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54   ` Jamie Lokier
2003-05-06 19:28     ` Jean-Marc Lienher
2003-05-06 19:53     ` Alan Cox
2003-05-06 22:31       ` Jamie Lokier [this message]
2003-05-06 21:38         ` Alan Cox
2003-05-08 21:36     ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55   ` Jamie Lokier
2003-05-06 22:21     ` David Schwartz
2003-05-07  8:21     ` Eric W. Biederman
2003-05-07 14:25       ` Valdis.Kletnieks
2003-05-07 14:31         ` Jamie Lokier
2003-05-07 15:50           ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18   ` Jamie Lokier
2003-05-06 21:31     ` Alan Cox
2003-05-06 22:48       ` Jamie Lokier
2003-05-07 12:20         ` Alan Cox
2003-05-07 14:26           ` Jamie Lokier
2003-05-07 15:18             ` Pavel Machek
2003-05-08 11:11 ` Krzysztof Halasa
     [not found] <20030506165014$3d57@gated-at.bofh.it>
     [not found] ` <20030506193019$0d29@gated-at.bofh.it>
     [not found]   ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07  1:17     ` Tony 'Nicoya' Mantler
     [not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman
2003-05-09  1:23 Jean Tourrilhes
2003-05-13  9:08 Dean McEwan

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=20030506223127.GD6284@mail.jlokier.co.uk \
    --to=jamie@shareable.org \
    --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

all inboxes | Powered by JetHome®