mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Anonymous User" <anonymouslinuxuser@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Adrian Bunk" <bunk@stusta.de>,
	"Patrick McFarland" <diablod3@gmail.com>,
	"Arjan van de Ven" <arjan@infradead.org>,
	"Grzegorz Kulewski" <kangur@polcom.net>,
	"Stefan Richter" <stefanr@s5r6.in-berlin.de>
Subject: Re: GPL Violation?
Date: Thu, 17 Aug 2006 07:58:01 -0700	[thread overview]
Message-ID: <40d80630608170758h801504boebb92563238d8b06@mail.gmail.com> (raw)
In-Reply-To: <40d80630608162248y498cb970r97a14c582fd663e1@mail.gmail.com>

On 8/16/06, Anonymous User <anonymouslinuxuser@gmail.com> wrote:
> I work for a company that will be developing an embedded Linux based
> consumer electronic device.
>
> I believe that new kernel modules will be written to support I/O
> peripherals and perhaps other things.  I don't know the details right
> now.  What I am trying to do is get an idea of what requirements there
> are to make the source code available under the GPL.
>
> I suspect the company will try to get away with releasing as little as
> possible.  I don't know much about the GPL or Linux kernel internals,
> but I want to encourage the company I work for to give back to the
> community.
>
> I understand that modifications to GPL code must be released under the
> GPL.  So if they tweak a scheduler implementation, this must be
> released.  What if a new driver is written to support a custom piece
> of hardware?  Yes, the driver was written to work with the Linux
> kernel, but it isn't based off any existing piece of code.
>
> I'm posting anonymously because the company probably wouldn't want me
> discussing this at all  :(


Thanks to everyone who has responded to my question so far.

It seems like the two issues that need to be addressed are:
1) Are the kernel modules being developed derived works?  If they are,
they must be released along with the entire kernel source.
2) If they are not derived works, and shipped in a product, does the
fact that they are shipped in a product that uses the linux kernel
require that the new modules be licensed under the GPL?

Yes, I agree that the company I work for should talk to a lawyer.  I
however, am not interested in picking up a big legal tab to satisfy my
curiosity.

  parent reply	other threads:[~2006-08-17 14:58 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17  5:48 Anonymous User
2006-08-17  6:14 ` Arjan van de Ven
2006-08-17  9:38   ` Ben B
2006-08-17 12:02     ` linux-os (Dick Johnson)
2006-08-17 16:11       ` Stefan Richter
2006-08-17 19:21   ` James Courtier-Dutton
2006-08-17 23:26     ` Ian Stirling
     [not found]       ` <20060817193540.dc819396.seanlkml@sympatico.ca>
2006-08-17 23:35         ` Sean
2006-08-18  0:32       ` Alan Cox
2006-08-18  7:23       ` Xavier Bestel
2006-08-18 12:23         ` Ian Stirling
2006-08-18  9:04       ` Helge Hafting
2006-08-17  6:42 ` Patrick McFarland
2006-08-17  6:54   ` Arjan van de Ven
2006-08-17  7:32     ` Patrick McFarland
2006-08-17  8:02       ` Adrian Bunk
2006-08-17  9:03         ` Patrick McFarland
2006-08-18 17:56           ` Adrian Bunk
2006-08-17 12:39         ` Grzegorz Kulewski
2006-08-17 13:41           ` Alan Cox
2006-08-17 13:31             ` Grzegorz Kulewski
2006-08-17 15:52               ` Theodore Tso
2006-08-18  2:03             ` Chase Venters
2006-08-17  8:32   ` Stefan Richter
2006-08-17  9:36     ` Patrick McFarland
2006-08-17 11:25       ` Alan Cox
2006-08-17 11:48         ` Neil Brown
2006-08-17  9:37   ` David Woodhouse
2006-08-17 23:45     ` Ian Stirling
2006-08-18  8:28       ` David Woodhouse
2006-08-18 12:52         ` Ian Stirling
2006-08-18  8:53       ` Bernd Petrovitsch
2006-08-18  9:04         ` David Woodhouse
2006-08-18  9:15           ` Bernd Petrovitsch
2006-08-20 22:05     ` Andrea Arcangeli
2006-08-20 22:20       ` Arjan van de Ven
2006-08-18  9:51   ` David Schwartz
2006-08-18 16:52     ` Alan Cox
2006-08-18 22:42       ` David Schwartz
2006-08-19 10:48         ` David Greaves
2006-08-19 16:29           ` Patrick McFarland
2006-08-19 17:28             ` David Greaves
2006-08-19 11:30         ` Helge Hafting
2006-08-19 15:44           ` Michael Buesch
2006-08-19 23:01           ` David Schwartz
2006-08-20  3:20           ` Chase Venters
2006-08-21  7:58             ` Helge Hafting
2006-08-21 11:27               ` Stefan Richter
2006-08-21 13:06               ` Alan Cox
2006-08-21 14:59               ` Horst H. von Brand
2006-08-17  9:30 ` Alan Cox
2006-08-17  9:29   ` Patrick McFarland
2006-08-17 14:52 ` Helge Hafting
2006-08-17 14:58 ` Anonymous User [this message]
2006-08-17 15:52   ` Stefan Richter
2006-08-17 16:19   ` Michiel de Boer

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=40d80630608170758h801504boebb92563238d8b06@mail.gmail.com \
    --to=anonymouslinuxuser@gmail.com \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=diablod3@gmail.com \
    --cc=kangur@polcom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®