public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] common: fit: Allow U-Boot images to be booted
Date: Thu, 21 Jul 2016 06:56:30 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1607210648570.12265@localhost.localdomain> (raw)
In-Reply-To: <CAN1kZooof27a2ZkXSSN=dqmMH0aTT+M3-2sjjcyt-zqoOP=R2A@mail.gmail.com>

On Wed, 20 Jul 2016, Mario Six wrote:

> On Wed, Jul 20, 2016 at 3:56 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:

... snip ...

> >   not really, since i always thought that the difficulty in loading
> > and booting a second-stage u-boot was explained here:
> >
> > http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStartedInRAM
> >
> > that is, loading the second image to a different address is simple;
> > the apparent difficulty is that the second-stage u-boot might not be
> > able to handle the early setup already done by the first stage.
> >
> >   so i'm still confused as to what is being proposed here, and how it
> > works.
> >
> > rday
> >
>
> Ah, alright. Look at the following quote from the page:
>
> "On machines with boot-ROM and U-Boot-SPL, you might have better luck."
>
> I'd venture that most SoCs these days have a boot-ROM; on these
> U-Boot, is not as sensitive to not finding a "virgin" system
> (because the boot-ROM does some initialization beforehand). The
> system I tested with is a Armada 38x, and we've also use a similar
> approach on a MPC85xx system (if you would like to dig that deep,
> the code is upstream: board/gdsys/p1022/controlcenterd*). The whole
> SPL concept would be a problem if the boot loader needed a virgin
> CPU (since, well, the SPL *is* a second U-Boot), so the restrictions
> mentioned in the page are not as relevant for modern SoCs.
>
> That's as far as my knowledge goes, if anyone wants to correct me,
> you're welcome to do so :-)

  ok, so it appears that wiki page is a little on the pessimistic
side, then. i was aware of the SPL, having worked with beaglebone
black for a while. i've never looked *closely* at how limited or
restrictive the SPL is, but i did know it had to do far less than the
full-featured u-boot. maybe it's time to look into that far more
closely to understand it better, and to appreciate what's possible.

  i can see this 2013 presentation, "TPL: SPL loading SPL (and, SPL as
just another U-Boot config", from scott wood of freescale. that looks
like it might be educational.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2016-07-21 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20  6:32 [U-Boot] [PATCH v2] common: fit: Allow U-Boot images to be booted Mario Six
2016-07-20 12:27 ` Tom Rini
2016-07-20 12:59 ` Robert P. J. Day
2016-07-20 13:39   ` Mario Six
2016-07-20 13:56     ` Robert P. J. Day
2016-07-20 14:26       ` Mario Six
2016-07-21 10:56         ` Robert P. J. Day [this message]
2016-07-26  2:32 ` [U-Boot] [U-Boot, " Tom Rini

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=alpine.LFD.2.20.1607210648570.12265@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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