All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] LS1021ATWR: Modify u-boot size for sd secureboot
Date: Mon, 30 Jan 2017 05:09:10 +0000	[thread overview]
Message-ID: <VI1PR04MB14556CADD6B053EBD62264E2984B0@VI1PR04MB1455.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM4PR0401MB17323CF1DFD125D165945EF19A760@AM4PR0401MB1732.eurprd04.prod.outlook.com>

> -----Original Message-----
> From: york sun
> Sent: Friday, January 27, 2017 10:55 PM
> To: Vini Pillai <vinitha.pillai@nxp.com>; Sumit Garg <sumit.garg@nxp.com>
> Cc: u-boot at lists.denx.de; Ruchika Gupta <ruchika.gupta@nxp.com>;
> Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> Subject: Re: [PATCH] LS1021ATWR: Modify u-boot size for sd secureboot
> 
> "Secure boot" is a two-word phrase, not one word.
> 
> On 01/20/2017 01:35 AM, Vinitha Pillai-B57223 wrote:
> > From: Vinitha Pillai <vinitha.pillai@nxp.com>
> >
> > Raw uboot image is used in place of FIT image in secure boot.
> > The maximum allocated size of raw u-boot bin is 1MB in memory map.
> > Hence , CONFIG_SYS_MONITOR_LEN has been modified to 1 MB.
> > The bootscript  (BS_ADDR) and its header (BS_HDR_ADDR) offset on MMC
> have also been modified to accommodate the increase in uboot size.
> 
> Please wrap back at or before 70 characters. Avoid putting extra white space in
> the message.
> 
> >
> > Signed-off-by: Vinitha Pillai-B57223 <vinitha.pillai@nxp.com>
> 
> Sumit,
> 
> This change seems harmless. However I don't have the images setup for
> testing. Please review this patch as the secure boot maintainer.
> 
> York

Reviewed-by: Sumit Garg <sumit.garg@nxp.com>

Vinitha,

Please incorporate York comments.

Sumit

      reply	other threads:[~2017-01-30  5:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 15:32 [U-Boot] [PATCH] LS1021ATWR: Modify u-boot size for sd secureboot Vinitha Pillai-B57223
2017-01-27 17:24 ` york sun
2017-01-30  5:09   ` Sumit Garg [this message]

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=VI1PR04MB14556CADD6B053EBD62264E2984B0@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.