From: Andre Renaud <andre@bluewatersys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] cpu/arm926ejs/start.S question
Date: Fri, 08 Jul 2011 10:40:51 +1200 [thread overview]
Message-ID: <4E1635F3.7090109@bluewatersys.com> (raw)
In-Reply-To: <CAPnjgZ03k8gEPRCWR5zwM7zUQPOYRzRimZrkHccxU6EO-DVv0w@mail.gmail.com>
Hi Simon,
> We have a similar thing with Tegra, and have built something into the
> USB download script which prepends the needed data. In this case it
> needs to be signed so it isn't possible to just include it in the U-Boot
> source, anyway.
>
> I suppose
>
> cat preload.bin u-boot.bin >u-boot.out
I can't think of a particularly good reason why that wouldn't work. It
is nice to use the U-Boot build system to take care of it though, and
there is less chance of someone accidentally flashing the original
u-boot.bin, rather than u-boot.out. I also take advantage of some
information available in the linker in my 'preload.bin', (such as image
size, boot address etc...).
I guess its a question of which is less horrible - maintaining a preload
outside of u-boot, and having a build process which combines them, or
the dodgy #include that I suggested. I'm in favour of the #include,
partly because I've already done it & got it working, but also because
it makes the build system less complex, so less chance of someone making
a mistake. I'm sure I'd feel differently if I'd thought of the
preload.bin first however.
Regards,
Andre
next prev parent reply other threads:[~2011-07-07 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 21:38 [U-Boot] cpu/arm926ejs/start.S question Andre Renaud
2011-07-07 22:34 ` Simon Glass
2011-07-07 22:40 ` Andre Renaud [this message]
2011-07-08 0:54 ` Fabio Estevam
2011-07-08 1:20 ` Andre Renaud
2011-07-08 1:38 ` Fabio Estevam
2011-07-08 1:42 ` Andre Renaud
2011-07-08 6:13 ` Stefano Babic
2011-07-11 4:59 ` Andre Renaud
2011-07-11 15:00 ` Fabio Estevam
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=4E1635F3.7090109@bluewatersys.com \
--to=andre@bluewatersys.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.