All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] powerpc/p1010rdb: SECURE BOOT- define CONFIG_SYS_RAMBOOT for NAND boot
Date: Mon, 27 Jan 2014 15:22:23 +0100	[thread overview]
Message-ID: <20140127142223.DDF2538033A@gemini.denx.de> (raw)
In-Reply-To: <680c371d651d49a08b33ddd4d01fb3bd@DM2PR03MB415.namprd03.prod.outlook.com>

Dear "aneesh.bansal at freescale.com",

In message <680c371d651d49a08b33ddd4d01fb3bd@DM2PR03MB415.namprd03.prod.outlook.com> you wrote:
> >> In case of secure boot, boot from NAND is ramboot.
> >> It was removed by some other commit. So defining it again.
> >
> >In case of not-secure-boot, it's not ramboot.
> >
> >What user of CONFIG_SYS_RAMBOOT are you concerned about?  Many of them
> >look like this:
> >
> >#elif !defined(CONFIG_SYS_RAMBOOT) && defined(CONFIG_SECURE_BOOT)
> >
> >...which doesn't make sense if secure boot is always considered ramboot.
> >
> >-Scott
> 
> CONFIG_SYS_RAMBOOT is for secure boot from NAND, SPI and SD.

This is a misuse of the variable.  The established meaning does NOT
include booding from standard boot media like NAND, SPI and SD.  It
refers to booting from RAM "directly", after the image has been placed
into RAM by "external" means, say by a JTAG debugger, or by copying it
to a PCI card's memory.

Please avoid such misleading usage.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Time is a drug. Too much of it kills you.
                                      - Terry Pratchett, _Small Gods_

  reply	other threads:[~2014-01-27 14:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  9:25 [U-Boot] [PATCH 1/3] powerpc/p1010rdb: SECURE BOOT- define CONFIG_SYS_RAMBOOT for NAND boot Aneesh Bansal
2014-01-20 22:04 ` Scott Wood
2014-01-27  7:20   ` aneesh.bansal at freescale.com
2014-01-27 14:22     ` Wolfgang Denk [this message]
2014-01-28  4:47       ` aneesh.bansal at freescale.com
2014-01-28  5:35         ` Wolfgang Denk
2014-03-04 17:11           ` York Sun
2014-03-05  5:30             ` aneesh.bansal at freescale.com
2014-03-05 18:00               ` Scott Wood
2014-03-06  9:24                 ` aneesh.bansal at freescale.com
2014-03-07  0:35                   ` York Sun
2014-03-07 18:57                   ` Scott Wood
2014-03-07 19:01                     ` York Sun
2014-03-10  9:14                       ` aneesh.bansal at freescale.com
2014-03-10 15:26                         ` York Sun
2014-03-10 23:58                         ` Scott Wood
2014-03-11 15:53                           ` 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=20140127142223.DDF2538033A@gemini.denx.de \
    --to=wd@denx.de \
    --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.