From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building two different "SPL" for the same board?
Date: Thu, 23 May 2013 11:54:13 +0200 [thread overview]
Message-ID: <20130523115413.4e5aad2d@lilith> (raw)
In-Reply-To: <1369299219.20995.14.camel@localhost>
Hi Henrik,
On Thu, 23 May 2013 10:53:39 +0200, Henrik Nordstr?m
<henrik@henriknordstrom.net> wrote:
> ons 2013-05-22 klockan 11:26 -0400 skrev Tom Rini:
>
> > If we can implement it cleanly, this isn't (at the 1000 meter view) all
> > that much different than what we do on some PowerPC platforms today
> > where everything must fit within a few kilobytes.
>
> Yes it is quite doable. The pieces I have done should be possible to fit
> without too much effort.
>
> The question is more if these kinds of board initialization only
> programs is seen as suitable for having in the u-boot tree. It's not
> really an SPL as it does not load anything, but it's 99.9% the same code
> as used in u-boot SPL.
My opinion is that such code fits in U-Boot quite well. After all, SPL
too was "that much shorter bit of code that was run before U-Boot
because U-Boot is too large to load and run directly on this platform".
Granted, SPL now tends to outgrow itself -- to the point that it becomes
more of a 'lightweight U-Boot', as Falcon mode shows -- but obviously,
there is a need for a very short code piece that can fit in e.g. a NAND
access device's read buffer.
> Regards
> Henrik
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-05-23 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 18:06 [U-Boot] Building two different "SPL" for the same board? Henrik Nordström
2013-05-17 18:17 ` Tom Rini
2013-05-17 20:56 ` Henrik Nordström
2013-05-22 15:26 ` Tom Rini
2013-05-23 8:53 ` Henrik Nordström
2013-05-23 9:54 ` Albert ARIBAUD [this message]
2013-05-23 20:39 ` Tom Rini
2013-05-24 1:14 ` Henrik Nordström
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=20130523115413.4e5aad2d@lilith \
--to=albert.u.boot@aribaud.net \
--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