All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/5] 85xx: add boot from NAND/eSDHC/eSPI support
Date: Fri, 11 Sep 2009 13:06:22 -0500	[thread overview]
Message-ID: <4AAA919E.8040002@freescale.com> (raw)
In-Reply-To: <1252639077-29277-1-git-send-email-Mingkai.hu@freescale.com>

Mingkai Hu wrote:
> The MPC8536E is capable of booting form NAND/eSDHC/eSPI, this patch
> implements these three bootup methods in a unified way - all of these
> use the general cpu/mpc85xx/start.S, and load the main image to L2SRAM
> which lets us use the SPD to initialize the SDRAM.
> 
> For all three bootup methods, the bootup process can be divided into two
> stages: the first stage will initialize the corresponding controller,
> configure the L2SRAM, then copy the second stage image to L2SRAM and
> jump to it. The second stage image is just like the general U-Boot image
> to configure all the hardware and boot up to U-Boot command line.
> 
> When boot from NAND, the eLBC controller will first load the first stage
> image to internal 4K RAM buffer because it's also stored on the NAND
> flash. The first stage image, also call 4K NADN loader, will initialize

s/NADN/NAND/ here...

> +#ifdef CONFIG_NADN_SPL
>  static void tlbsx (const volatile unsigned *addr)

And more importantly, here.

-Scott

  parent reply	other threads:[~2009-09-11 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11  3:17 [U-Boot] [PATCH v2 1/5] 85xx: add boot from NAND/eSDHC/eSPI support Mingkai Hu
2009-09-11 13:37 ` Wolfgang Denk
2009-09-14  2:33   ` Hu Mingkai-B21284
2009-09-11 18:06 ` Scott Wood [this message]
2009-09-11 18:07   ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2009-09-11  2:53 [U-Boot] [PATCH v2 0/5] Add " Mingkai Hu
2009-09-11  2:53 ` [U-Boot] [PATCH v2 1/5] 85xx: add " Mingkai Hu
2009-09-11  3:12   ` Kumar Gala
2009-09-11  3:20     ` Hu Mingkai-B21284

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=4AAA919E.8040002@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 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.