From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/3] ppc/p1_p2_RDB: DDR Relocation supportfor NAND/SD/eSPI Boot
Date: Fri, 09 Oct 2009 14:36:16 -0500 [thread overview]
Message-ID: <4ACF90B0.9030702@freescale.com> (raw)
In-Reply-To: <F2F605B667B24B489C904986E0D60A08FF6454@zin33exm23.fsl.freescale.net>
Dudhat Dipen-B09055 wrote:
>
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Friday, October 09, 2009 11:48 PM
> To: Dudhat Dipen-B09055
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] [PATCH v3 3/3] ppc/p1_p2_RDB: DDR Relocation
> supportfor NAND/SD/eSPI Boot
>
> On Fri, Oct 09, 2009 at 11:12:04PM +0530, Dipen Dudhat wrote:
>> DDR support to boot from NAND/eSDHC/eSPI on P1 & P2 RDB platforms.
>> Specifically this support needed when L2 Cache size is less than 512K.
>
> If you're going to use this for eSDHC and eSPI, why is it sitting under
> nand_spl?
>
> To initialize DDR and create LAW in 4K nand_spl code.
> Basically this patch adds support of DDR for NAND/eSDHC/eSPI boot on top
> of L2 cache support on P1 and P2 RDB Platforms.
>
> So do I need to split this patch in two parts?? For NAND and
> eSDHC/eSPI??
My point is that the DDR stuff is not specific to NAND, it applies to several
different boot mechanisms. So just put it the normal board directory.
-Scott
next prev parent reply other threads:[~2009-10-09 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 17:42 [U-Boot] [PATCH v3 3/3] ppc/p1_p2_RDB: DDR Relocation support for NAND/SD/eSPI Boot Dipen Dudhat
2009-10-09 18:17 ` Scott Wood
2009-10-09 19:18 ` [U-Boot] [PATCH v3 3/3] ppc/p1_p2_RDB: DDR Relocation supportfor " Dudhat Dipen-B09055
2009-10-09 19:36 ` Scott Wood [this message]
2009-10-09 18:20 ` [U-Boot] [PATCH v3 3/3] ppc/p1_p2_RDB: DDR Relocation support for " Kumar Gala
2009-10-09 20:19 ` Dudhat Dipen-B09055
2009-10-09 20:54 ` Kumar Gala
2009-10-12 6:31 ` Dudhat Dipen-B09055
2009-10-12 15:42 ` Kim Phillips
2009-10-13 15:22 ` Kumar Gala
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=4ACF90B0.9030702@freescale.com \
--to=scottwood@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox