From: "Kaz Kylheku" <kkylheku@gmail.com>
To: "Alexey Dobriyan" <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL question: using large contiguous memory in proprietary driver.
Date: Tue, 14 Oct 2008 16:18:50 -0700 [thread overview]
Message-ID: <3f43f78b0810141618s64dbeeeew82b41f100890bb5f@mail.gmail.com> (raw)
In-Reply-To: <20081014221018.GA1498@x200.localdomain>
On Tue, Oct 14, 2008 at 3:10 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> On Tue, Oct 14, 2008 at 02:56:40PM -0700, Kaz Kylheku wrote:
>> Would it be okay to have a mechanism like this:
>> Suppose that on the kernel command line, you could
>> request a boot-time memory allocation and give it a name.
>> For instance, the parameter:
>>
>> boot_alloc=foo,8192K
>>
>> would create an 8192 kilobyte allocation, and associate it
>> with the string "foo". A non-GPL function would be provided to
>> find the address of this memory, using the string "foo"
>> as the key. The proprietary driver would document the
>> requirement that it needs a memory region of at least
>> 8192K, under the name "foo".
>>
>> Help! :)
>
> Since the code to reserve memory and code to find by name won't be
> accepted, the question is rather pointless.
Suppose that this problem is being solved by people who maintain
their own OS distribution, based around a customized Linux kernel,
targetting a very specific piece of hardware, manufactured by
them.
So there is no situation in which users of a mainstream
distribution would be asked to patched their kernels to
be able to use this driver. Their kernels would already
come that way from this distribution.
The driver in question is specific to the hardware, and uses code
licensed from the vendor of some chips that are used on the
embedded system, so the developers don't have the option of
open-sourcing it, however attractive that might be.
next prev parent reply other threads:[~2008-10-14 23:20 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 [this message]
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
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=3f43f78b0810141618s64dbeeeew82b41f100890bb5f@mail.gmail.com \
--to=kkylheku@gmail.com \
--cc=adobriyan@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
all inboxes | Powered by JetHome®