From: Sumit Garg <sumit.garg@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/7] SECURE_BOOT: Enable chain of trust on LS1012A platform
Date: Wed, 29 Mar 2017 17:01:44 +0000 [thread overview]
Message-ID: <VI1PR04MB1455A60AC48D1F7EFBB64A0F98350@VI1PR04MB1455.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR0401MB268732E7D8891D0FDBD3280A9A350@VI1PR0401MB2687.eurprd04.prod.outlook.com>
> -----Original Message-----
> From: york sun
> Sent: Wednesday, March 29, 2017 10:20 PM
> To: Sumit Garg <sumit.garg@nxp.com>; u-boot at lists.denx.de
> Cc: Ruchika Gupta <ruchika.gupta@nxp.com>; Prabhakar Kushwaha
> <prabhakar.kushwaha@nxp.com>; Vini Pillai <vinitha.pillai@nxp.com>
> Subject: Re: [PATCH 6/7] SECURE_BOOT: Enable chain of trust on LS1012A
> platform
>
> On 03/23/2017 01:19 AM, Sumit Garg wrote:
> > From: Vinitha Pillai-B57223 <vinitha.pillai@nxp.com>
> >
> > Define bootscript and its header addresses for QSPI target Also add
> > PPA header address in Kconfig
> >
> > Signed-off-by: Vinitha Pillai <vinitha.pillai@nxp.com>
> > Signed-off-by: Sumit Garg <sumit.garg@nxp.com>
> > ---
> > arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 1 +
> > arch/arm/include/asm/arch-fsl-layerscape/config.h | 7 ++++++-
> > arch/arm/include/asm/fsl_secure_boot.h | 3 +++
> > 3 files changed, 10 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> > b/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> > index fbb6642..03bc9ea 100644
> > --- a/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> > +++ b/arch/arm/cpu/armv8/fsl-layerscape/Kconfig
> > @@ -160,6 +160,7 @@ config SYS_LS_PPA_ESBC_ADDR
> > depends on FSL_LS_PPA && CHAIN_OF_TRUST
> > default 0x600c0000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1043A
> > default 0x40740000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1046A
> > + default 0x40480000 if SYS_LS_PPA_FW_IN_XIP && ARCH_LS1012A
>
> This one has another different offset. Why?
>
> York
This is due to difference in memory map for LS1012A and LS1046A in SDK.
Sumit
next prev parent reply other threads:[~2017-03-29 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 8:18 [U-Boot] [PATCH 0/7] Add LS1046 and LS1012 secure boot targets Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 1/7] SECURE BOOT: Add header address of PPA in kconfig Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 2/7] LS1043ARDB: Enable PPA in Secure boot defconfig Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 3/7] SECURE_BOOT: Enable chain of trust on LS1046A platform Sumit Garg
2017-03-29 16:45 ` [U-Boot] [u-boot-release] " york sun
2017-03-29 17:00 ` Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 4/7] LS1046AQDS: Add NOR Secure Boot Target Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 5/7] LS1046ARDB: Add QSPI Secure Boot target Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 6/7] SECURE_BOOT: Enable chain of trust on LS1012A platform Sumit Garg
2017-03-29 16:50 ` york sun
2017-03-29 17:01 ` Sumit Garg [this message]
2017-03-29 17:03 ` york sun
2017-03-29 17:06 ` Sumit Garg
2017-03-23 8:18 ` [U-Boot] [PATCH 7/7] LS1012ARDB: Add QSPI Secure Boot target Sumit Garg
2017-04-18 15:36 ` [U-Boot] [PATCH 0/7] Add LS1046 and LS1012 secure boot targets York Sun
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=VI1PR04MB1455A60AC48D1F7EFBB64A0F98350@VI1PR04MB1455.eurprd04.prod.outlook.com \
--to=sumit.garg@nxp.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.