public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot env variables parsing
Date: Thu, 01 Apr 2010 20:27:47 +0200	[thread overview]
Message-ID: <20100401182747.90999C88C6@gemini.denx.de> (raw)
In-Reply-To: <OF5552925C.8F998468-ONC12576F8.005E3247-C12576F8.005E9BF2@transmode.se>

Dear Joakim Tjernlund,

In message <OF5552925C.8F998468-ONC12576F8.005E3247-C12576F8.005E9BF2@transmode.se> you wrote:
>
> > To me it looks like the new code would indeed do a "greedy" substitution
> > only stopping when no more substitutions can be done.  This is very
> > un-unixy and thus not something I'd like to see as a default behaviour.
> 
> Why not? What is gained by the current method?

We follow the principle of least surprise [1]; the command line
interpeter in U-Boot should behave as similar to a (say, POSIX
compatible) shell as possible. Restrictions and deviations are not
intentional, but caused by the attempt to do with a minimal memory
footprint.

Like Detlev I feel/fear that the suggested change will cause more
annoyance due to unexpected behaviour that it will do good.


I also see little actual need for such an extension, as in all cases
I've seen so far it has been possible to acchieve the goal without
code changes by just minimal adjustments of the definitions. For
example, your code:

linuxip=ip=$(ipaddr)::$(gatewayip):$(netmask):$(hostname):$(linuxif):off
tboot=setenv bootargs $(linuxroot) $(linuxip) $(extra);tftp 100000; bootm 100000

could be rewritten from plain variable definitions into an equivalent
command sequence, like that:

setenv setip 'setenv bootargs ${bootargs} ip=${ipaddr}::${gatewayip}:${netmask}:${hostname}:${linuxif}:off'

Do the same for "linuxroot" (=> setroot) and "extra" (=> setextra),
and then use:

setenv tboot 'run setroot setip setextra;tftp 100000;bootm'

will do exactly what you want. Detlev quoted similar code earlier.
This is what many, many existing boards use, and what we explain in
great detail in the manual.


[1] http://en.wikipedia.org/wiki/Principle_of_least_surprise


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Old programmers never die, they just become managers.

  reply	other threads:[~2010-04-01 18:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01  5:27 [U-Boot] U-boot env variables parsing Nitin Mahajan
2010-04-01 12:15 ` Detlev Zundel
2010-04-01 12:31   ` Joakim Tjernlund
2010-04-01 12:47     ` Wolfgang Denk
2010-04-01 12:56       ` Joakim Tjernlund
2010-04-01 13:05         ` Wolfgang Denk
2010-04-01 13:11           ` Joakim Tjernlund
2010-04-01 14:56             ` Detlev Zundel
2010-04-01 17:13               ` Joakim Tjernlund
2010-04-01 18:27                 ` Wolfgang Denk [this message]
2010-04-01 20:08                   ` Joakim Tjernlund
2010-04-08 10:00                     ` Detlev Zundel
2010-04-08 15:41                       ` Joakim Tjernlund
2010-04-08 16:06                         ` Detlev Zundel
2010-04-08 17:49                           ` Joakim Tjernlund

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=20100401182747.90999C88C6@gemini.denx.de \
    --to=wd@denx.de \
    --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