From: "Kaz Kylheku" <kkylheku@gmail.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL question: using large contiguous memory in proprietary driver.
Date: Tue, 14 Oct 2008 16:39:42 -0700 [thread overview]
Message-ID: <3f43f78b0810141639w4ec50a08tdc847b16ebcea5be@mail.gmail.com> (raw)
In-Reply-To: <48F5193B.1010601@nortel.com>
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).
One more thing. Here is another question.
Suppose that this proprietary driver can be moved entirely into user
space. It still needs the contiguous buffer, but it can
map it using mmap, given the address.
Can this proprietary user-space application read the address
of this buffer from a custom /proc entry?
Or does this dependency make it a derived work of the kernel?
next prev parent reply other threads:[~2008-10-14 23:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 21:56 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
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 [this message]
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=3f43f78b0810141639w4ec50a08tdc847b16ebcea5be@mail.gmail.com \
--to=kkylheku@gmail.com \
--cc=cfriesen@nortel.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®