From: Hatim Ali <rvhatim@yahoo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot] Info on NAND-SPL
Date: Sat, 26 Feb 2011 17:04:05 +0530 (IST) [thread overview]
Message-ID: <96382.60182.qm@web95116.mail.in2.yahoo.com> (raw)
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?
?
Also is there any similar implementation for MMC-SPL?
?
Thanks
Hatim
next reply other threads:[~2011-02-26 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 11:34 Hatim Ali [this message]
2011-02-27 18:11 ` [U-Boot] Info on NAND-SPL Wolfgang Denk
2011-02-28 11:43 ` Albert ARIBAUD
2011-03-07 22:02 ` Scott Wood
2011-03-01 5:53 ` Aneesh V
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=96382.60182.qm@web95116.mail.in2.yahoo.com \
--to=rvhatim@yahoo.co.in \
--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