From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Multiple binaries built through u-boot source
Date: Tue, 14 Sep 2010 09:02:25 -0400 [thread overview]
Message-ID: <201009140902.26755.vapier@gentoo.org> (raw)
In-Reply-To: <201009141440.55577.sr@denx.de>
On Tuesday, September 14, 2010 08:40:55 Stefan Roese wrote:
> On Tuesday 14 September 2010 12:21:41 Vipin Kumar wrote:
> > > 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.
> >
> > Yes, got it. The only point is that this is meant to boot from NAND,
> > ONENAND devices(As the name suggests). Can there be a generic interface
> > independent of a particular device.
> >
> > Offcourse I agree that execute in place would work for NOR devices and we
> > wont need this kinda solution but still a generic solution for both types
> > of devices is preferable
>
> Sure, a more generic approach would be better. But I suspect that this is
> not so easy to do. Those tight image-size restrictions of the IPL/SPL
> loaders will make such generalisation efforts quite difficult.
there should at least be a build system unification if the general source code
isnt possible. all Blackfin builds now (LDRs) have a dedicated binary to
initialize memory before any of u-boot is loaded. this is the "initcode"
stuff in the blackfin cpu dir.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100914/a769ee6c/attachment.pgp
next prev parent reply other threads:[~2010-09-14 13:02 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 [this message]
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
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=201009140902.26755.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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.