public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Multiple binaries built through u-boot source
Date: Tue, 14 Sep 2010 16:26:13 +0200	[thread overview]
Message-ID: <201009141626.13795.sr@denx.de> (raw)
In-Reply-To: <AANLkTik8fO0TK4Gb-7GXHZdAe8=GK2oDjAj9KVb-Oh87@mail.gmail.com>

Hi Kyungmin,

On Tuesday 14 September 2010 16:18:00 Kyungmin Park wrote:
> >> This looks promising. However, our SPL has to load u-boot from MMC. Is
> >> it OK to keep it under nand_spl directory or should we create
> >> something like 'mmc_spl'?
> 
> Good question, It created the mmc_ipl and use it for mmc booting e.g.,
> eMMC boot.

mmc_ipl? This is not in mainline yet.
 
> > Not sure. Perhaps we should now really think about a more generic
> > approach and merge all this IPL/SPL stuff into a single directory.
> > Perhaps something like this:
> > 
> > spl/
> > spl/nand
> > spl/onenand
> > spl/mmc
> > spl/board
> 
> Good, and use the CONFIG_PRELOADER as existing. but what's the SPL
> stand for? SPL (secondary program loader)?

Correct. That's how IBM/AMCC called this code first loaded from NAND in their 
documentation. IPL (Initial Program Loader) was used for the ROM code inside 
the SoC, loading this SPL code from NAND.

Please note that I don't have a strong preference here. We could also call 
this first loader stage in the U-Boot source "IPL". But we should move to one 
name and stop mixing these names.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2010-09-14 14:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  5:22 [U-Boot] Multiple binaries built through u-boot source Vipin Kumar
2010-09-14  7:05 ` Mike Frysinger
2010-09-14  7:16 ` Stefan Roese
2010-09-14  8:11   ` Kyungmin Park
2010-09-14 10:21   ` Vipin Kumar
2010-09-14 12:40     ` Stefan Roese
2010-09-14 13:02       ` Mike Frysinger
2010-09-14 13:33     ` V, Aneesh
2010-09-14 13:51       ` Stefan Roese
2010-09-14 14:18         ` Kyungmin Park
2010-09-14 14:26           ` Stefan Roese [this message]
2010-09-14 14:32             ` Kyungmin Park
2010-09-14 15:16               ` Mike Frysinger
2010-09-16 15:44           ` Premi, Sanjeev
2010-09-16 17:59             ` Scott Wood
2010-09-17  9:12               ` Premi, Sanjeev
2010-09-16 18:31             ` Mike Frysinger
2010-09-17  9:21               ` Premi, Sanjeev
2010-09-14 14:22       ` Vaibhav Bedia
2010-09-14 14:26         ` Kyungmin Park
2010-09-14 16:17       ` Wolfgang Denk
2010-09-15 16:36         ` Scott Wood
2010-09-15 17:20           ` Stefan Roese
2010-09-15 17:45           ` Wolfgang Denk
2010-09-15 18:01             ` Scott Wood
2010-09-15 19:21               ` Wolfgang Denk

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=201009141626.13795.sr@denx.de \
    --to=sr@denx.de \
    --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