From: "Chris Friesen" <cfriesen@nortel.com>
To: Kaz Kylheku <kkylheku@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL question: using large contiguous memory in proprietary driver.
Date: Tue, 14 Oct 2008 20:21:12 -0600 [thread overview]
Message-ID: <48F55398.10005@nortel.com> (raw)
In-Reply-To: <3f43f78b0810141623s4282f9eof87014d2dee17810@mail.gmail.com>
Kaz Kylheku wrote:
> On Tue, Oct 14, 2008 at 3:12 PM, Chris Friesen <cfriesen@nortel.com>
> wrote:
>
>> Kaz Kylheku wrote:
>>
>>
>>> I have the following question. Suppose that some proprietary
>>> driver (otherwise completely clean, based only on non-GPL
>>> symbols)
>>
>> The fact that it's not using GPL symbols does not actually mean
>> that the driver is not a derivative work of the kernel (and thus
>> subject to the GPL).
>
>
> But thanks to the gracious tolerance of the kernel development
> community, such drivers are permitted to exist.
If you're thinking of something like the Nvidia driver, the binary
portion of that driver is cross-platform and is not a derivative work of
the kernel.
If you sit down and write a new driver for linux, is is arguable that it
is in fact a derivative work of the kernel and is thus subject to the GPL.
This may of course vary based on location, but I strongly suggest that
you consult suitable legal advice before proceeding.
Chris
next prev parent reply other threads:[~2008-10-15 2:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 21:56 GPL question: using large contiguous memory in proprietary driver Kaz Kylheku
2008-10-14 22:05 ` Peter Zijlstra
2008-10-14 22:10 ` Alexey Dobriyan
2008-10-14 23:18 ` Kaz Kylheku
2008-10-14 22:12 ` Chris Friesen
2008-10-14 23:23 ` Kaz Kylheku
2008-10-15 2:21 ` Chris Friesen [this message]
2008-10-15 5:23 ` David Newall
2008-10-15 5:30 ` Adrian Bunk
2008-10-15 9:05 ` Alan Cox
2008-10-15 13:21 ` John Stoffel
2008-10-14 23:39 ` Kaz Kylheku
2008-10-15 11:26 ` Nick Piggin
2008-10-15 11:26 ` Nick Piggin
2008-10-15 13:54 ` Mark Hounschell
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=48F55398.10005@nortel.com \
--to=cfriesen@nortel.com \
--cc=kkylheku@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.