From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] QE firmware/microcode handling
Date: Thu, 20 Sep 2012 17:16:13 +0200 [thread overview]
Message-ID: <20120920151613.AC396203A17@gemini.denx.de> (raw)
In-Reply-To: <505AE6C3.5080708@keymile.com>
Dear Gerlando Falauto,
In message <505AE6C3.5080708@keymile.com> you wrote:
>
> following up Timur's patch on QE microcode:
>
> http://marc.info/?l=u-boot&m=132197537730440&w=2
>
> I was wondering, would it make any sense to *embed* QE's firmware within
> u-boot image itself?
It's a matter of taste/requirements/system design.
> Not quite sure whether this has ever been done for similar purposes, but
> to me it looks way more convenient to have a single image file to be
> flashed, rather than reserving room (e.g. within the same NOR flash
> where u-boot lies) for it.
A similar situation is with the persistent copy of the environment -
it might be "embedded" within the U-Boot image (actually even with
U-Boot code before and after it), it may be prepended or appended, or
it may be completely separate. All options make sense for certain
configurations, and none for others.
Having a single file may be an advantage, or a disadvantage. You
cannot tell in advance without knowing the exact specifications of the
hardware and the requirements for the software design.
So the most flexible way is actually to make no assumptions about the
location, and handle it in a board-specific way if needed (say, through
a board specific linker script, or some scripts).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"One planet is all you get."
next prev parent reply other threads:[~2012-09-20 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 9:49 [U-Boot] QE firmware/microcode handling Gerlando Falauto
2012-09-20 15:16 ` Wolfgang Denk [this message]
2012-09-20 15:22 ` Timur Tabi
2012-09-20 18:24 ` Scott Wood
2012-09-20 21:28 ` Timur Tabi
2012-09-21 1:55 ` McClintock Matthew-B29882
2012-09-21 8:32 ` [U-Boot] [PATCH] SBx81CFC960: embed Fman microcode in the bootloader judge.packham at gmail.com
2012-09-21 11:32 ` Tabi Timur-B04825
2012-09-21 15:58 ` Wolfgang Denk
2012-09-21 16:30 ` Timur Tabi
2012-09-22 9:44 ` Chris Packham
2012-09-24 14:25 ` Timur Tabi
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=20120920151613.AC396203A17@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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