From: "John Stoffel" <john@stoffel.org>
To: "Kaz Kylheku" <kkylheku@gmail.com>
Cc: "Chris Friesen" <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: GPL question: using large contiguous memory in proprietary driver.
Date: Wed, 15 Oct 2008 09:21:53 -0400 [thread overview]
Message-ID: <18677.61041.265144.217180@stoffel.org> (raw)
In-Reply-To: <3f43f78b0810141623s4282f9eof87014d2dee17810@mail.gmail.com>
>>>>> "Kaz" == Kaz Kylheku <kkylheku@gmail.com> writes:
Kaz> 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).
Kaz> But thanks to the gracious tolerance of the kernel development
Kaz> community, such drivers are permitted to exist. That is the question:
Kaz> setting aside GPL chapter and verse, could that tolerance extend
Kaz> to allow such a driver to get a piece of boot-time memory, and if so,
Kaz> what mechanism would be tolerated?
Why doesn't your hardware support Scatter Gather Lists instead? Then
you could setup virtual contiguous memory regions to use, but the
underlying physical RAM could be fragmented and you wouldn't care.
Seems like the more sensible solution. Also, more people would be
*happy* to help you in that case, as opposed to the "I need a large
block of contiguous RAM" request which pops up a couple of times a
year on this list and pretty much always gets shot down.
John
next prev parent reply other threads:[~2008-10-15 13:22 UTC|newest]
Thread overview: 14+ 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
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 [this message]
2008-10-14 23:39 ` Kaz Kylheku
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=18677.61041.265144.217180@stoffel.org \
--to=john@stoffel.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox