From: Arnd Bergmann <arnd@arndb.de>
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, 1 Nov 2006 17:48:31 +0100 [thread overview]
Message-ID: <200611011748.31781.arnd@arndb.de> (raw)
In-Reply-To: <4547E720.4080505@gmail.com>
On Wednesday 01 November 2006 01:15, Jiri Slaby wrote:
> is preferred to have firmware in kernel binary (and go through array of chars)
> or userspace (and load it through standard kernel api)?
If you control the whole system, the ideal way is to have the system
firmware or boot loader come with the firmware blob and avoid worrying
about it in linux entirely. E.g. if you are using Open Firmware, you
can have the binary image as a property of the device in your device
tree, where Linux then goes looking for it.
Arnd <><
prev parent reply other threads:[~2006-11-01 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 0:15 preferred way of fw loading 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
2006-11-01 12:07 ` Alan Cox
2006-11-01 16:48 ` Arnd Bergmann [this message]
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=200611011748.31781.arnd@arndb.de \
--to=arnd@arndb.de \
--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