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 14:41:59 -0400 [thread overview]
Message-ID: <489B41F7.6010107@ge.com> (raw)
In-Reply-To: <BBDD524A-F763-49E1-B459-0EB5AA242A32@kernel.crashing.org>
Kumar Gala wrote:
>
> On Aug 7, 2008, at 12:21 PM, Jerry Van Baren wrote:
>
>> Kumar Gala 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?
>>> - k
>>
>> Yes.
>
> Than I think the ideas you guys have aren't beneficial to anyone. What
> benefit to we gain by doing this? Its going to be slower and larger.
>
> - k
...for some subset of "anyone."
A lot of people resisted moving to the linux 2.6 kernel because it is
slower and larger than the 2.4 kernel. A lot of embedded devices (and
probably some servers and desktops) are still running 2.4 kernels. I
would not conclude that 2.6 isn't beneficial to anyone.
Maybe the destination turns into a failure, but half the fun is planning
the trip.
gvb
next prev parent reply other threads:[~2008-08-07 18: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 [this message]
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
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=489B41F7.6010107@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