All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
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, 10 Mar 2014 08:26:04 -0700	[thread overview]
Message-ID: <531DD98C.9010205@freescale.com> (raw)
In-Reply-To: <8b80270d5e2f4dc88e58326f43f00532@DM2PR03MB415.namprd03.prod.outlook.com>

On 03/10/2014 02:14 AM, Bansal Aneesh-B39320 wrote:
>> -----Original Message-----
>> From: Sun York-R58495
>> Sent: Saturday, March 08, 2014 12:31 AM
>> To: Bansal Aneesh-B39320
>> Cc: Wood Scott-B07421; Wolfgang Denk; u-boot at lists.denx.de; Gupta
>> Ruchika-R66431
>> Subject: Re: [U-Boot] [PATCH 1/3] powerpc/p1010rdb: SECURE BOOT-
>> define CONFIG_SYS_RAMBOOT for NAND boot
>>
>> On 03/07/2014 10:57 AM, Scott Wood wrote:
>>> On Thu, 2014-03-06 at 03:24 -0600, Bansal Aneesh-B39320 wrote:
>>>>> -----Original Message-----
>>>>> From: Wood Scott-B07421
>>>>> Sent: Wednesday, March 05, 2014 11:30 PM
>>>>> To: Bansal Aneesh-B39320
>>>>> Cc: Sun York-R58495; Wolfgang Denk; u-boot at lists.denx.de; Gupta
>>>>> Ruchika-R66431
>>>>> Subject: Re: [U-Boot] [PATCH 1/3] powerpc/p1010rdb: SECURE BOOT-
>>>>> define CONFIG_SYS_RAMBOOT for NAND boot
>>>>>
>>>>> On Tue, 2014-03-04 at 23:30 -0600, Bansal Aneesh-B39320 wrote:
>>>>>> Yes, in case of secure boot from NAND, the DRAM is initialized by
>>>>> the
>>>>>> BootROM and complete u-boot image is copied from NAND to DRAM by
>>>>>> the
>>>>> BootROM.
>>>>>> So, it should be called RAMBOOT.
>>>>>
>>>>> DRAM or SRAM?  Having ROM initialize DDR is a bit scary.
>>>>>
>>>>> -Scott
>>>>>
>>>> It can be either DDR or SRAM. It is not hardcoded in BootROM to
>> initialize DDR.
>>>> This depends on the config words (CF_WORDS) in the CF_HEADER.
>>>> The Boot ROM code parses the config words and programs the
>> addresses
>>>> with data values accordingly. The user may opt to initialize DDR
>> and
>>>> get the image copied onto DDR or configure CPC as SRAM and get the
>> Image copied onto SRAM.
>>>> On 1010,
>>>
>>> P1010?  LS1010?  Something else?
>>>
>>>> the CPC size is not big enough to accommodate the U-boot image.
>>>> So, currently the CF_WORDS are for DDR to be initialized and copy
>> the image on DDR.
>>>
>>> Generally if SPD is present, it should be used to init DDR rather
>> than
>>> using hardcoded values.  If U-Boot doesn't fit in SRAM, you can use
>>> SPL instead of hardcoded init.
>>
>> I agree with Scott on this point. Using hardcoded values totally skip
>> DDR driver. You don't only lose the flexibility of various speeds, you
>> also skip all workarounds implemented in DDR driver.
>>
>> York
> Currently we are following the same approach which was there for SPI and SD on P1010 i.e hardcoded initialization of DDR in platforms like P1010, 9131/9132 using config words.
> 

Understood.

York

  reply	other threads:[~2014-03-10 15:26 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
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 [this message]
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=531DD98C.9010205@freescale.com \
    --to=yorksun@freescale.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.