From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,v4] spl: add support to booting with ATF
Date: Mon, 15 May 2017 19:18:18 -0400 [thread overview]
Message-ID: <20170515231818.GF5701@bill-the-cat> (raw)
In-Reply-To: <1493956072-11281-1-git-send-email-kever.yang@rock-chips.com>
On Fri, May 05, 2017 at 11:47:45AM +0800, Kever Yang wrote:
> ATF(ARM Trusted Firmware) is used by ARM arch64 SoCs, find more infomation
> about ATF at: https://github.com/ARM-software/arm-trusted-firmware
>
> SPL is considered as BL2 in ATF terminology, it needs to load other parts
> of ATF binary like BL31, BL32, SCP-BL30, and BL33(U-Boot). And needs to
> prepare the parameter for BL31 which including entry and image information
> for all other images. Then the SPL handle PC to BL31 with the parameter,
> the BL31 will do the rest of work and at last get into U-Boot(BL33).
>
> This patch needs work with patches from Andre for SPL support multi
> binary in FIT.
>
> The entry point of bl31 and bl33 are still using hard code because we
> still can not get them from the FIT image information.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
> Acked-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170515/9a863b7f/attachment.sig>
prev parent reply other threads:[~2017-05-15 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 3:47 [U-Boot] [PATCH v4] spl: add support to booting with ATF Kever Yang
2017-05-05 15:41 ` Heiko Stuebner
2017-05-14 9:32 ` Simon Glass
2017-05-14 13:47 ` Tom Rini
2017-05-15 23:18 ` Tom Rini [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=20170515231818.GF5701@bill-the-cat \
--to=trini@konsulko.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