From: Arjan van de Ven <arjan@infradead.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
R.E.Wolff@BitWizard.nl
Subject: Re: preferred way of fw loading
Date: Wed, 01 Nov 2006 09:17:18 +0100 [thread overview]
Message-ID: <1162369038.3044.80.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4547E720.4080505@gmail.com>
On Wed, 2006-11-01 at 01:15 +0100, Jiri Slaby wrote:
> Hello,
>
> is preferred to have firmware in kernel binary (and go through array of chars)
> or userspace (and load it through standard kernel api)?
generally the preferred way is for you to use request_firmware() API
which causes userspace to upload it to you via standard mechanisms.
This avoids kernel size bloat if it's not needed (by only having the
firmware in memory that is really really needed) and also avoids the
entire question of "can it be done within GPL" (not saying it can or
cannot, but usually if someone asks its a huge flamewar and this just
sidesteps the entire issue)
next prev parent reply other threads:[~2006-11-01 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 0:15 Jiri Slaby
2006-11-01 7:29 ` Rogier Wolff
2006-11-01 18:28 ` Jiri Slaby
2006-11-01 8:17 ` Arjan van de Ven [this message]
2006-11-01 12:07 ` Alan Cox
2006-11-01 16:48 ` Arnd Bergmann
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=1162369038.3044.80.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=R.E.Wolff@BitWizard.nl \
--cc=jirislaby@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®