>>>>> "Kaz" == Kaz Kylheku <kkylheku@gmail.com> writes:

Kaz> On Tue, Oct 14, 2008 at 3:12 PM, Chris Friesen <cfriesen@nortel.com> wrote:
quoted text
>> 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
--
unsubscribe notice
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/