All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas, Madan <madans@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/7] arm: omap-common: adds secure image name common to, OMAP and keystone
Date: Thu, 8 Sep 2016 23:01:01 -0400	[thread overview]
Message-ID: <57D225ED.4000103@ti.com> (raw)

As K2 can directly boot u-boot, add u-boot_HS_MLO as the
secure image while booting secure K2 devicesr, for all
boot modes other than SPI flash.

Signed-off-by: Madan Srinivas <madans@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>

---

Changes in v3: None
Changes in v2:
- Adds a new name for the signed output image in config_secure.mk
   to keep it in line with the image name used by non-secure keystone
   devices.

  arch/arm/cpu/armv7/omap-common/config_secure.mk | 6 ++++++
  1 file changed, 6 insertions(+)

diff --git a/arch/arm/cpu/armv7/omap-common/config_secure.mk 
b/arch/arm/cpu/armv7/omap-common/config_secure.mk
index 1122439..0ece3f8 100644
--- a/arch/arm/cpu/armv7/omap-common/config_secure.mk
+++ b/arch/arm/cpu/armv7/omap-common/config_secure.mk
@@ -76,6 +76,12 @@ u-boot-spl_HS_ISSW: $(obj)/u-boot-spl.bin
  u-boot-spl_HS_SPI_X-LOADER: $(obj)/u-boot-spl.bin
  	$(call if_changed,mkomapsecimg)

+# For supporting single stage boot on keystone, the image is a full u-boot
+# file, not an SPL. This will work for all boot devices, other than SPI
+# flash
+u-boot_HS_MLO: $(obj)/u-boot.bin
+	$(call if_changed,mkomapsecimg)
+
  # For supporting single stage XiP QSPI on AM43xx, the image is a full 
u-boot
  # file, not an SPL. In this case the mkomapsecimg command looks for a
  # u-boot-HS_* prefix
-- 
2.7.4

                 reply	other threads:[~2016-09-09  3:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=57D225ED.4000103@ti.com \
    --to=madans@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 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.