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-Users] bootm as a script -- requires HUSH?
Date: Thu, 07 Aug 2008 16:41:17 -0400	[thread overview]
Message-ID: <489B5DED.5030203@ge.com> (raw)
In-Reply-To: <D40FF1A0-B5E5-49A9-9DD1-2D0434F32D73@kernel.crashing.org>

Kumar Gala wrote:
> On Aug 7, 2008, at 2:29 PM, Wolfgang Denk wrote:
> 
>> In message  
>> <44343BF5-2E91-4596-8CCA-61CEA1F84F63@kernel.crashing.org> you wrote:
>>> if I understand Wolfgang and Jerry they'd like to recode the control
>>> flow of the bootm command in the scripting env u-boot provides.
>>>
>>> This seems to imply that we'd require HUSH as the simple parser
>>> doesn't seem to provide any control statements like (if..then..else).
>>>
>>> is this correct?
>> I woul like to avoid that, if possible.
> 
> Which implies to me the sequence has to be a simple ordered sequence w/ 
> o any if/than/else aspects to it.  Am I missing something?
> 
> - k

Nope.

Remaining to be shown: how far apart "reality" is from "goal".

gvb

"I've always used my ignorance as a weapon. I don't know why things 
can't be done. Engineers spend a lot of time telling us why things can't 
be done. Sometimes they're right. But sometimes they're not."

    - Garry Hoyt

      reply	other threads:[~2008-08-07 20:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 16:10 [U-Boot-Users] bootm as a script -- requires HUSH? Kumar Gala
2008-08-07 17:21 ` Jerry Van Baren
2008-08-07 18:17   ` Kumar Gala
2008-08-07 18:41     ` Jerry Van Baren
2008-08-07 19:34     ` Wolfgang Denk
2008-08-07 20:25       ` Kumar Gala
2008-08-07 20:47         ` Wolfgang Denk
2008-08-07 21:01           ` Kumar Gala
2008-08-07 19:29 ` Wolfgang Denk
2008-08-07 20:28   ` Kumar Gala
2008-08-07 20:41     ` Jerry Van Baren [this message]

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=489B5DED.5030203@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