From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] want to know scenario
Date: Wed, 18 Jul 2007 14:17:00 +0200 [thread overview]
Message-ID: <m2abttewjn.fsf@sowhat.denx.de> (raw)
In-Reply-To: <7ee1596c0707161359hdaff987rf75580d08cb8c293@mail.gmail.com> (sapirf fersht's message of "Mon\, 16 Jul 2007 23\:59\:12 +0300")
Hi Sapirf,
> How u-boot treats the following commands:
Your question is really cryptic. If you do have a running U-Boot, you
probably know the answers, but hey sometimes even I don't believe my
own eyes.
> setenv ipaddr 192.168.2.202
> saveenv
> printenv
This shold change ipaddr to what you tell U-Boot, save it to
persistent storage (whereever that is on your board) and finally dump
the whole environment.
> reset
Wow, now you reset your board...
> go
... and force the next incarnation of U-Boot to display an error
message as you didn't provide a second argumtn.
> printenv
But the environment is still there!
> vs
>
> saveenv
> printenv
> reset
> go
> printenv (is there a possiblity of failure in this command)?
Well, the error message is printed at a different time and you don't
change ipaddr - and no printenv will never fail as long as your
hardware lives.
By now I am pretty sure I did not understand your question, so maybe
you try again...
Cheers
Detlev
--
Man is a fool, and woman, for tolerating him, is a damned fool
-- Mark Twain
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
prev parent reply other threads:[~2007-07-18 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 20:59 [U-Boot-Users] want to know scenario sapirf fersht
2007-07-18 12:17 ` Detlev Zundel [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=m2abttewjn.fsf@sowhat.denx.de \
--to=dzu@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