From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Info on NAND-SPL
Date: Tue, 01 Mar 2011 11:23:51 +0530 [thread overview]
Message-ID: <4D6C89EF.3060305@ti.com> (raw)
In-Reply-To: <96382.60182.qm@web95116.mail.in2.yahoo.com>
Hello Hatim,
On Saturday 26 February 2011 05:04 PM, Hatim Ali wrote:
> Hello,
>
> I was trying to understand how NAND-SPL works. What I could understand after seeing the code is that
> 1) NAND-SPL is a standalone application which will load the U-boot in the main memory.
> 2) After doing the clock and DRAM initialization it will relocate itself in the DRAM.
> 3) Then it will copy the u-boot from the nand into the RAM and execute the u-boot.
>
> If my understanding is proper, then I have one doubt
> 1) Since the nand_spl is making use of the same Start.S and lowlevel_init.S, the u-boot code will also perform relocation? So is it not a overhead doing relocation twice?
As Albert mentioned in another mail, image copying and relocation can
be suppressed by using your linked address as the target address when
you call relocate_code.
This is easier to achieve in SPL because we have a custom and simpler
board_init_f. This is much more difficult to achieve in regular U-Boot
because the target address is calculated at run-time in board_init_f
and also depends on the U-Boot size.
>
> Also is there any similar implementation for MMC-SPL?
You might want to have a look at the series I posted yesterday for
OMAP4. Please note that relocation and image copying has been
suppressed in this SPL.
Br,
Aneesh
prev parent reply other threads:[~2011-03-01 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 11:34 [U-Boot] Info on NAND-SPL Hatim Ali
2011-02-27 18:11 ` Wolfgang Denk
2011-02-28 11:43 ` Albert ARIBAUD
2011-03-07 22:02 ` Scott Wood
2011-03-01 5:53 ` Aneesh V [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=4D6C89EF.3060305@ti.com \
--to=aneesh@ti.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