All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <xeidos@gmx.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] a few questions about saving bootcount in the environment
Date: Wed, 27 Jul 2016 17:10:13 +0200	[thread overview]
Message-ID: <5798CED5.6080401@gmx.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1607270800590.25952@localhost.localdomain>

Hello Robert,

Am 27.07.2016 um 14:03 schrieb Robert P. J. Day:
> On Tue, 26 Jul 2016, Heiko Schocher wrote:
>
> ... snip ...
>
>>> it appears that, no matter what, the environment *is* updated
>>> every single time because of this line in the bootdelay_process()
>>> routine:
>>>
>>>     setenv_ulong("bootcount", bootcount);
>>>
>>> why? it seems, from the above, that no matter what boot counter
>>
>> Yes, the bootcount variable gets set here ... but the environment
>> gets not written...
>>
>>> mechanism you use, the environment will be updated because of that
>>> line.
>>
>> The Environment gets written when saveenv() gets called ... or?
>
> ... snip ...
>
>    yes, i already apologized to wolfgang for being so clueless, i
> didn't see the difference between "setenv" and "saveenv". anyway, i'm
> still writing a wiki page on this that i can use for future embedded
> linux classes, so ... onward.

no problem, I saw your response to wolfgang to late ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2016-07-27 15:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 17:29 [U-Boot] a few questions about saving bootcount in the environment Robert P. J. Day
2016-07-25  4:57 ` Wolfgang Denk
2016-07-25 13:57   ` Tom Rini
2016-07-25 14:35     ` Wolfgang Denk
2016-07-25 17:56       ` Robert P. J. Day
2016-07-25 18:37         ` Wolfgang Denk
2016-07-25 18:41           ` Robert P. J. Day
2016-07-25 17:26     ` Heiko Schocher
2016-07-26 12:21       ` Robert P. J. Day
2016-07-26 12:48         ` Wolfgang Denk
2016-07-26 12:49           ` Robert P. J. Day
2016-07-26 17:25         ` Heiko Schocher
2016-07-27 12:03           ` Robert P. J. Day
2016-07-27 15:10             ` Heiko Schocher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-25 14:36 Wolfgang Denk
2016-07-22 19:36 [U-Boot] confused by "upgrade_available=0\0" in include/configs/taurus.h Robert P. J. Day
2016-07-22 22:01 ` Wolfgang Denk
2016-07-23 11:42   ` Robert P. J. Day
2016-07-25  4:54     ` Wolfgang Denk
2016-07-25 10:03       ` Robert P. J. Day
2016-07-25 13:26         ` Wolfgang Denk
2016-07-25 17:24           ` [U-Boot] a few questions about saving bootcount in the environment Heiko Schocher

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=5798CED5.6080401@gmx.net \
    --to=xeidos@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.