All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Medhurst (Tixy) <jon.medhurst@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: vexpress: Extend default boot sequence to load script from MMC
Date: Wed, 30 Nov 2011 15:19:06 +0000	[thread overview]
Message-ID: <1322666346.3969.26.camel@linaro1> (raw)
In-Reply-To: <CA+M6bXnNgA-_V42yGvxBmNLOXYUOMRbssF+_Z1jD9H8mbCS_6Q@mail.gmail.com>

On Wed, 2011-11-30 at 07:51 -0700, Tom Rini wrote:
> On Wed, Nov 30, 2011 at 1:32 AM, Jon Medhurst (Tixy)
> <jon.medhurst@linaro.org> wrote:
> > On Tue, 2011-11-29 at 13:46 -0700, Tom Rini wrote:
> >> On Tue, Nov 29, 2011 at 6:46 AM, Jon Medhurst (Tixy)
> >> <jon.medhurst@linaro.org> wrote:
> >> > Extend the default boot sequence on Versatile Express to load a boot
> >> > script from MMC.
> >> >
> >> > Signed-off-by: Jon Medhurst <jon.medhurst@linaro.org>
> >>
> >> Is there any interest in defining a common 'fancy' boot command?  Over
> >> on beagleboard (and a few other eval boards) we are (or will be)
> >> doing, roughly:
> >> Is there mmc? {
> >>   Can we load a bootscript? {
> >>     load it, do it
> >>   }
> >>   Can we load uEnv.txt? {
> >>     Did it set 'uenvcmd'? {
> >>       Run it
> >>     }
> >>   }
> >>   Did we load the kernel? {
> >>     bootm it
> >>   }
> >> }
> >> Try nand.
> >>
> >> And it's not hard to replace NAND with "whatever flash the board sets"
> >
> > It could make sense. However, the combinations of boot methods could get
> > quite big, e.g. do we include pxeboot, tftp?
> 
> Well, maybe we define some blocks (TRY_MMC, TRY_ENET, TRY_NAND,
> TRY_SPI, ...) ...
> 
> > If everything was included in the common 'fancy boot' then some boards
> > would have to define boot methods (or stubs) for things they weren't
> > interested in. And, conversely, if fancy boot didn't include everything,
> > then other people would need to extend it.
> 
> ... provide a few examples of the blocks strung together and have
> people string up what they need themselves, so long as it's an
> otherwise good idea to have complex default boot methods?

If something like this was planned for BeagleBoard anyway, then perhaps
it could written in terms of these TRY_MMC etc. macros (which seem like
a reasonable idea to me). Then a working prototype could be posted as an
RFC for others to comment on? I suspect at the moment there's not many
people reading this 'vexpress' thread ;-)

-- 
Tixy

  reply	other threads:[~2011-11-30 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 13:46 [U-Boot] ARM: vexpress: Extend default boot sequence to load script from MMC Jon Medhurst
2011-11-29 16:04 ` Ryan Harkin
2011-11-29 20:46 ` Tom Rini
2011-11-30  8:32   ` Jon Medhurst
2011-11-30 14:51     ` Tom Rini
2011-11-30 15:19       ` Jon Medhurst [this message]
2011-11-30 15:46         ` 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=1322666346.3969.26.camel@linaro1 \
    --to=jon.medhurst@linaro.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.