DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=KvfoyeDH5PeRZCShAy3DmLK9SdDKWsAowPjFLDfNpNkncNqTHjfv9TmadK+7TdN84G
         Py9ppvNJtvJp5CqFJ3PtVr7b727G13Ql/KfXGWRiuy1hfUxy+eW/lp+pvWhsRHzkJ73D
         ODLeOjGbKnHGywW/q4IVP8e4I4YkTZ8O/CPUc=
Message-ID: <3f43f78b0810141623s4282f9eof87014d2dee17810@mail.gmail.com>
Date: Tue, 14 Oct 2008 16:23:37 -0700
From: "Kaz Kylheku" <kkylheku@gmail.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Subject: Re: GPL question: using large contiguous memory in proprietary driver.
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <48F5193B.1010601@nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3f43f78b0810141456r159d71e7h9763e50e7dbc0c51@mail.gmail.com>
	 <48F5193B.1010601@nortel.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 938
Lines: 19

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. That is the question:
setting aside GPL chapter and verse, could that tolerance extend
to allow such a driver to get a piece of boot-time memory, and if so,
what mechanism would be tolerated?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/