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 15:51:18 +0200 [thread overview]
Message-ID: <201009141551.18603.sr@denx.de> (raw)
In-Reply-To: <FF55437E1F14DA4BAEB721A458B6701706C58885A2@dbde02.ent.ti.com>
Hi Aneesh,
On Tuesday 14 September 2010 15:33:53 V, Aneesh wrote:
> > >> I wanted to know if there is a generic way to create two
> > >> binaries from the u-boot source both compiled for different
> > >> address ranges. The first initializes the RAM (may be
> > >> something else as well) and the second is the u-boot binary
> > >> responsible for loading OS etc.
>
> It's sheer coincidence that I also wanted to post a very similar query
> today. We have a similar requirement for OMAP platforms.
>
> Presently, we are maintaining a mini bootloader(called x-loader, based
> on u-boot)separately. We want to integrate x-loader with u-boot and
> up-stream the source code.
That's definitely a good idea.
> > > Take a look at the NAND_SPL infrastructure (nand_spl/*). It was
> > > created for
> > > platforms booting from NAND with tight restrictions (e.g. 4k image
> > > size for
> > > inital setup, mostly DDR). General idea here is that 2 images are
> > > created:
> > > a) Very small SPL (secondary program loader) image with only basic
> > > setup, like DDR and NAND
> > >
> > > b) RAM based U-Boot image
> > >
> > > Both images are combined in the build process creating a single
> > > image that can be flashed into NAND.
> > >
> > > doc/README.nand-boot-ppc440 might be interesting to get some more
> > > infos about this, some of it PPC4xx specific though.
>
> 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'?
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
...
Comments welcome.
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
next prev parent reply other threads:[~2010-09-14 13:51 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 [this message]
2010-09-14 14:18 ` Kyungmin Park
2010-09-14 14:26 ` Stefan Roese
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=201009141551.18603.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