All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <york.sun@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3][v3] arm: ls1043ardb: Add NAND secure boot target
Date: Thu, 13 Apr 2017 08:07:08 -0700	[thread overview]
Message-ID: <fdc83ad4-c74d-a753-4548-70ac6c064336@nxp.com> (raw)
In-Reply-To: <DB6PR04MB2951C984CCA235551173FAC1E5020@DB6PR04MB2951.eurprd04.prod.outlook.com>

On 04/13/2017 04:14 AM, Ruchika Gupta wrote:
>> -----Original Message-----
>> From: York Sun [mailto:york.sun at nxp.com]
>> Sent: Wednesday, April 12, 2017 9:00 PM
>> To: Ruchika Gupta <ruchika.gupta@nxp.com>; u-boot at lists.denx.de
>> Cc: Vini Pillai <vinitha.pillai@nxp.com>; Sumit Garg <sumit.garg@nxp.com>
>> Subject: Re: [PATCH 2/3][v3] arm: ls1043ardb: Add NAND secure boot target
>>
>> On 04/04/2017 10:37 AM, Ruchika Gupta wrote:
>>> Add NAND secure boot target for ls1043ardb.
>>>
>>> - Change the u-boot size defined by a macro for copying the main
>>>   U-Boot by SPL to also include the u-boot Secure Boot header size as
>>>   header is appended to u-boot image. So header will also be copied from SD
>> to DDR.
>>> - MACRO for CONFIG_BOOTSCRIPT_COPY_RAM is enabled to copy Bootscript
>> from NAND to
>>
>> Please send another patch to move this macro to Kconfig.
> Shall we send this Kconfig addition as a separate patch?

Yes, as a clean up patch.

York

      reply	other threads:[~2017-04-13 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 22:42 [U-Boot] [PATCH 2/3][v3] arm: ls1043ardb: Add NAND secure boot target Ruchika Gupta
2017-04-04 22:42 ` [U-Boot] [PATCH 3/3][v4] arm: ls1046ardb: Add SD " Ruchika Gupta
2017-04-12 15:30 ` [U-Boot] [PATCH 2/3][v3] arm: ls1043ardb: Add NAND " York Sun
2017-04-13 11:14   ` Ruchika Gupta
2017-04-13 15:07     ` York Sun [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=fdc83ad4-c74d-a753-4548-70ac6c064336@nxp.com \
    --to=york.sun@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.