All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Handley <Dan.Handley@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] spl: add support to booting with ATF
Date: Wed, 5 Apr 2017 08:25:03 +0000	[thread overview]
Message-ID: <HE1PR0801MB16767AA9221F7161F41607ECFD0A0@HE1PR0801MB1676.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAK7LNAQyVvSSnEe0n-nQyC02v+5m4_ZX+FvAngtJQdPYYUmR6g@mail.gmail.com>

Hi

> -----Original Message-----
> From: Masahiro Yamada [mailto:yamada.masahiro at socionext.com]
> Sent: 05 April 2017 06:36
>
> 2017-04-05 14:05 GMT+09:00 Kever Yang <kever.yang@rock-chips.com>:
> > 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
>
>
> SCP-BL30 ?
>
>
> Dan,
>
> I see BL30 in old documents, but this was deprecated, right?
>
Yes, the BL30 terminology was deprecated in favour of SCP_BL2. See:
https://github.com/ARM-software/arm-trusted-firmware/wiki/ARM-Trusted-Firmware-Image-Terminology#scp-ram-firmware-scp_bl2-previously-bl3-0

However, given this is an optional image, it might be worth removing the reference altogether.

Also, I notice this latest patch still uses bl31_params_t rather than the more recent bl_params_t.

Regards

Dan.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2017-04-05  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  5:05 [U-Boot] [PATCH v3 0/1] arm64: enable SPL with ATF support Kever Yang
2017-04-05  5:05 ` [U-Boot] [PATCH v3] spl: add support to booting with ATF Kever Yang
2017-04-05  5:35   ` Masahiro Yamada
2017-04-05  8:25     ` Dan Handley [this message]
2017-05-05  3:07       ` Kever Yang
2017-04-05 16:40   ` Masahiro Yamada
2017-05-05  3:33     ` Kever Yang

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=HE1PR0801MB16767AA9221F7161F41607ECFD0A0@HE1PR0801MB1676.eurprd08.prod.outlook.com \
    --to=dan.handley@arm.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.