All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/9] spl: atf: add support for LOAD_IMAGE_V2
Date: Fri, 20 Nov 2020 11:14:14 +0100	[thread overview]
Message-ID: <d406c3bd-3245-a913-842c-9cca6f1ac7a2@xilinx.com> (raw)
In-Reply-To: <20201118164602.22518-1-michael@walle.cc>

Hi,

On 18. 11. 20 17:45, Michael Walle wrote:
> Newer TF-A versions provide a new image loading protocol. This is used on
> (newer?) NXP's SoCs. Normally, the bootflow is bl1 -> bl2 -> bl31 ->
> u-boot. With this series it is possible that U-Boot SPL loads the bl31
> directly and thus replacing bl1 and bl2 from the TF-A.
> 
> This was tested on the Kontron sl28 board using NXPs bl31 and the upstream
> version of the OP-TEE Trusted OS.

I still have some questions about this.

As I see from TFA previous image format has been removed in 2018 by

commit ed51b51f7a9163a7fc48289c5ed97a3fe4fe504f
Author:     Roberto Vargas <roberto.vargas@arm.com>
AuthorDate: Mon Sep 24 17:20:48 2018 +0100
Commit:     Antonio Nino Diaz <antonio.ninodiaz@arm.com>
CommitDate: Fri Sep 28 15:31:52 2018 +0100

    Remove build option LOAD_IMAGE_V2

    The code of LOAD_IMAGE_V2=0 has been removed.

    Change-Id: Iea03e5bebb90c66889bdb23f85c07d0c9717fffe
    Co-authored-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
    Signed-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>


On Xilinx ZynqMP I use SPL->bl31 loading but not using that TFA
structure because xilinx is using own format.

But I am curious if V2 was removed in 2018 who is really using previous
one and also if current implemenation is origin or also not full v2.

And these patches are not breaking boot on zynqmp that's why not big
deal for me.

Thanks,
Michal

  parent reply	other threads:[~2020-11-20 10:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 16:45 [PATCH v2 0/9] spl: atf: add support for LOAD_IMAGE_V2 Michael Walle
2020-11-18 16:45 ` [PATCH v2 1/9] treewide: use CONFIG_IS_ENABLED() for ARMV8_SEC_FIRMWARE_SUPPORT Michael Walle
2020-12-07 22:19   ` Tom Rini
2020-11-18 16:45 ` [PATCH v2 2/9] spl: atf: move storage for bl31_params into function Michael Walle
2020-12-07 22:19   ` Tom Rini
2020-11-18 16:45 ` [PATCH v2 3/9] spl: atf: provide a bl2_plat_get_bl31_params_default() Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-11-18 16:45 ` [PATCH v2 4/9] spl: atf: remove helper structure from common header Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-11-18 16:45 ` [PATCH v2 5/9] spl: atf: add support for LOAD_IMAGE_V2 Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-11-18 16:45 ` [PATCH v2 6/9] armv8: layerscape: don't initialize GIC in SPL Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-11-18 16:46 ` [PATCH v2 7/9] board: sl28: remove u-boot from loadable DT node Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-12-07 22:20   ` Tom Rini
2020-11-18 16:46 ` [PATCH v2 8/9] board: sl28: add ATF support (bl31) Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-11-18 16:46 ` [PATCH v2 9/9] board: sl28: add OP-TEE Trusted OS support (bl32) Michael Walle
2020-12-07 22:20   ` Tom Rini
2020-11-20 10:14 ` Michal Simek [this message]
2020-11-20 10:48   ` [PATCH v2 0/9] spl: atf: add support for LOAD_IMAGE_V2 Michael Walle
2020-11-20 11:15     ` Michal Simek
2020-11-20 11:27       ` Michael Walle
2020-11-20 13:16         ` Michal Simek
2020-11-20 13:25           ` Michael Walle
2020-11-20 13:35             ` Michal Simek
2020-11-20 13:48               ` Michael Walle
2020-11-20 14:42               ` Tom Rini
2020-11-20 12:48     ` Michael Walle

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=d406c3bd-3245-a913-842c-9cca6f1ac7a2@xilinx.com \
    --to=michal.simek@xilinx.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.