From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH 5/9] ARM: Keystone2: Build secure images for K2
Date: Fri, 24 Feb 2017 06:59:42 -0600 [thread overview]
Message-ID: <20170224125946.7500-6-afd@ti.com> (raw)
In-Reply-To: <20170224125946.7500-1-afd@ti.com>
From: Madan Srinivas <madans@ti.com>
Adds an additional image type needed for supporting secure keystone
devices. The build generates u-boot_HS_MLO which can be used to boot
from all media on secure keystone devices.
Signed-off-by: Madan Srinivas <madans@ti.com>
Signed-off-by: Andrew F. Davis <afd@ti.com>
---
arch/arm/mach-keystone/config.mk | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-keystone/config.mk b/arch/arm/mach-keystone/config.mk
index 9ae1e9ac91..db556ea0a8 100644
--- a/arch/arm/mach-keystone/config.mk
+++ b/arch/arm/mach-keystone/config.mk
@@ -5,9 +5,15 @@
# SPDX-License-Identifier: GPL-2.0+
#
+include $(srctree)/arch/arm/mach-omap2/config_secure.mk
+
ifndef CONFIG_SPL_BUILD
+ifeq ($(CONFIG_TI_SECURE_DEVICE),y)
+ALL-y += u-boot_HS_MLO
+else
ALL-y += MLO
endif
+endif
MKIMAGEFLAGS_u-boot-spl.gph = -A $(ARCH) -T gpimage -C none \
-a $(CONFIG_SPL_TEXT_BASE) -e $(CONFIG_SPL_TEXT_BASE) -n SPL
--
2.11.0
next prev parent reply other threads:[~2017-02-24 12:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 12:59 [U-Boot] [RESEND PATCH 0/9] Add support for secure boot on Keystone2 SoCs Andrew F. Davis
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 1/9] image: Fixes build warning with CONFIG_FIT_IMAGE_POST_PROCESS Andrew F. Davis
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 2/9] arm: mach-keystone: Implements FIT post-processing call for keystone SoCs Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 3/9] arm: mach-omap2: Enable Kconfig support for K2 HS devices Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 4/9] arm: mach-omap2: Add secure image name common to OMAP and keystone Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` Andrew F. Davis [this message]
2017-02-27 15:18 ` [U-Boot] [RESEND PATCH 5/9] ARM: Keystone2: Build secure images for K2 Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 6/9] doc: Updates info on using Keystone2 secure devices Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 7/9] Kconfig: Adds SYS_TEXT_BASE config option for Keystone2 Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 8/9] defconfig: k2e_hs_evm: Add k2e_hs_evm_defconfig Andrew F. Davis
2017-02-27 15:19 ` Tom Rini
2017-02-28 17:47 ` Andrew F. Davis
2017-02-28 17:58 ` Tom Rini
2017-03-03 4:53 ` Simon Glass
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 9/9] defconfig: k2hk_hs_evm: Add k2hk_hs_evm_defconfig Andrew F. Davis
2017-02-27 15:19 ` Tom Rini
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=20170224125946.7500-6-afd@ti.com \
--to=afd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox