public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jamie Lokier <jamie@shareable.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Thu, 8 May 2003 23:36:02 +0200	[thread overview]
Message-ID: <20030508213601.GC4466@elf.ucw.cz> (raw)
In-Reply-To: <20030506185433.GA6023@mail.jlokier.co.uk>

Hi!

> > > So, as dynamic loading is ok between parts of Linux and binary-only
> > > code, that seems to imply we could build a totally different kind of
> > > binary-only kernel which was able to make use of all the Linux kernel
> > > modules.  We could even modularise parts of the kernel which aren't
> > > modular now, so that we could take advantage of even more parts of Linux.
> > 
> > You want a legal list - you really do. Its all about derived works and
> > thats an area where even some lawyers will only hunt in packs 8)
> 
> Alan, you're right of course - from a legal standpoint.  But I'm not
> interested in how it pans out in a strict legal interpretation.
> 
> What I'm interested in is how the kernel developers and driver authors
> would treat something like that.  Binary modules haven't had the full
> lawyer treatment AFAIK, but a sort of community viewpoint regarding
> what is and is not acceptable, to the community, is fairly clear on
> this list.
> 
> So I was wondering what is the community viewpoint when it's the
> core kernel that is a non-GPL binary, rather than the modules.
> 
> What if this new-fangled other kernel is open source, but BSD
> license

If you took vicam driver and made it ran under Windows XP, it would be
okay. (It uses defined interface after all). I do not see why vicam
driver under "your own os" would be different.

								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  parent reply	other threads:[~2003-05-08 22:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 16:42 Using GPL'd Linux drivers with non-GPL, binary-only kernel 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
2003-05-06 21:38         ` Alan Cox
2003-05-08 21:36     ` Pavel Machek [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=20030508213601.GC4466@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jamie@shareable.org \
    --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