From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] how does board_init_f() -> board_init_r?
Date: Tue, 16 Feb 2016 09:41:36 -0700 [thread overview]
Message-ID: <56C35140.1000009@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ2Q1Gh+5ZqJFeMp+_1TSqSSpypXoMNQ1g_h7myUkmOFSA@mail.gmail.com>
On 02/16/2016 09:01 AM, Simon Glass wrote:
> +Stephen who will know more
>
> Hi,
>
> On 13 February 2016 at 18:52, quantumlight <peter.feifan.chen@gmail.com> wrote:
>> I am trying to modify the bootloader code for NVIDIA's jetson board.
>>
>> So I am looking at crt0.S. It seems that two builds happen, one with
>> CONFIG_SPL_BUILD and one without. So you end up with two file, u-boot.bin
>> and spl/u-boot-spl.bin.
>
> SPL is built with ARMv4t
> U-Boot proper is built with ARMv7
>
> That's why SPL is used on Tegra. The SPL does not actually load
> U-Boot. In fact both are bundle together and loaded at the same time.
> SPL simply jumps to U-Boot when needed.
There's some more background on this topic at:
ftp://download.nvidia.com/tegra-public-appnotes/index.html
In particular, see the "Tegra Boot Flow" link/document.
next prev parent reply other threads:[~2016-02-16 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 1:52 [U-Boot] how does board_init_f() -> board_init_r? quantumlight
2016-02-16 16:01 ` Simon Glass
2016-02-16 16:41 ` Stephen Warren [this message]
2016-02-17 7:19 ` Peter Chen
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=56C35140.1000009@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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