public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] bootm: Add subcommands
Date: Wed, 22 Oct 2008 07:32:21 -0400	[thread overview]
Message-ID: <48FF0F45.3000406@ge.com> (raw)
In-Reply-To: <E78921C7-E7F2-4B4D-89F7-B06F23A18B98@kernel.crashing.org>

Kumar Gala wrote:
> On Oct 21, 2008, at 2:30 PM, Wolfgang Denk wrote:
> 
>> Dear Kumar Gala,
>>
>> In message <1224520091-26756-1-git-send-email-galak@kernel.crashing.org 
>>> you wrote:
>>> Add the ability to break the steps of the bootm command into several
>>> subcommands: start, loados, ramdisk, fdt, bdt, cmdline, prep, go.
>>>
>>> This allows us to do things like manipulate device trees before
>>> they are passed to a booting kernel or setup memory for a secondary
>>> core in multicore situations.
>>>
>>> Not all OS types support all subcommands (currently only start,  
>>> loados,
>>> ramdisk, fdt, and go are supported).
>>>
>>> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>> This looks mostly OK to me, but I haven't actually tested any of this
>> code yet - can you please comment to what extend you tested it?
> 
> I've tested this on FSL 85xx HW.  I'm able to boot using a sequence of  
> bootm subcommands + a few other commands as well as plain old bootm.

Ditto for the MPC8360.

Best regards,
gvb

  reply	other threads:[~2008-10-22 11:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 16:28 [U-Boot] [PATCH 1/2] bootm: Add subcommands Kumar Gala
2008-10-20 16:28 ` [U-Boot] [PATCH 2/2] bootm: support subcommands in linux ppc bootm Kumar Gala
2008-10-21 19:30 ` [U-Boot] [PATCH 1/2] bootm: Add subcommands Wolfgang Denk
2008-10-21 22:22   ` Kumar Gala
2008-10-22 11:32     ` Jerry Van Baren [this message]
2008-10-21 19:44 ` Jerry Van Baren
2008-10-21 19:50   ` Wolfgang Denk
2008-10-21 19:51     ` Jerry Van Baren
2008-10-21 20:05       ` Wolfgang Denk
2008-10-21 20:07         ` Jerry Van Baren
2008-10-21 23:04   ` Kumar Gala
2008-10-22 11:35     ` Jerry Van Baren

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=48FF0F45.3000406@ge.com \
    --to=gerald.vanbaren@ge.com \
    --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