From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL support and secondary image size
Date: Fri, 04 Nov 2011 07:41:45 +0530 [thread overview]
Message-ID: <4EB349E1.7010907@ti.com> (raw)
In-Reply-To: <4EB31D2A.3070107@freescale.com>
Hi Jon,
On Friday 04 November 2011 04:30 AM, Scott Wood wrote:
> On 11/03/2011 05:20 PM, jonsmirl at gmail.com wrote:
Looks like I am not seeing some mails in this thread. I didn't get your
first mail, neither Tom Rini's mails.
>> My primary SPL image needs the size of the secondary image built into
>> it. How do I access that size while building the primary SPL image?
For OMAP we find this run-time by loading u-boot.img instead of
u-boot.bin. u-boot.img has a 64 byte header with all necessary
information such as size, load address, image type etc. The OMAP SPL
can in fact load any image that has a standard u-boot header(mkimage
header), including a uImage. This scheme was suggested by Wolfgang.
>
> Does it need to be exact? Usually we just hardcode something that
> should be big enough.
>
> -Scott
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2011-11-04 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 22:20 [U-Boot] SPL support and secondary image size jonsmirl at gmail.com
2011-11-03 23:00 ` Scott Wood
[not found] ` <CAKON4OwiW0tq+yvZkiEWwAyUiryYxN5bOFe49QqtFmhDKq=c_Q@mail.gmail.com>
2011-11-03 23:09 ` jonsmirl at gmail.com
2011-11-03 23:27 ` jonsmirl at gmail.com
[not found] ` <CA+M6bX=0itMjmC4gm7oEuLdyWjmex99=8iok5289tWdBLBGGaA@mail.gmail.com>
2011-11-04 1:53 ` jonsmirl at gmail.com
2011-11-04 2:11 ` Aneesh V [this message]
2011-11-04 2:53 ` jonsmirl at gmail.com
2011-11-04 15:16 ` jonsmirl at gmail.com
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=4EB349E1.7010907@ti.com \
--to=aneesh@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox