From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Redundant environment
Date: Mon, 01 May 2006 17:55:43 -0500 [thread overview]
Message-ID: <445691EF.1000401@orkun.us> (raw)
In-Reply-To: <200605010819.26596.sr@denx.de>
Stefan Roese wrote:
> Hi Wolfgang,
>
> On Friday, 28. April 2006 21:31, Wolfgang Denk wrote:
>
>>> Of course, I will also document both behavior in README properly,
>>> introduce the same functionality in env_flash.c, env_nand.c etc. (i.e.
>>> all mediums that redundant environment is implemented) and fixup
>>> fw_setenv/fw_getenv utility.
>>>
>> You mean, you want to change more than the saveenc command to run
>> twice? Is this really needed?
>>
>
> As I mentioned before, I also tend to forget to use special commands like 2
> times "saveenv". So I still vote to include Tolunay's patch.
>
> Or do you mean that you would like to see this new behavior implemented in a
> patched saveenv command, that calls the original _saveenv twice? This would
> have the advantage of less code changes, but the disadvantage of doing
> everything twice (like unprotect, protect).
>
> Best regards,
> Stefan
>
Yes, I can do it in saveenv code to cycle twice but I would rather avoid
doing unlock/re-lock/over flag byte stuff twice.
Whichever way Wolfgang favors I am ready to work on a patch.
Best regards,
Tolunay
next prev parent reply other threads:[~2006-05-01 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 16:32 [U-Boot-Users] Redundant environment Tolunay Orkun
2006-04-28 19:31 ` [U-Boot-Users] " Wolfgang Denk
2006-05-01 6:19 ` Stefan Roese
2006-05-01 22:55 ` Tolunay Orkun [this message]
2006-05-01 23:13 ` Wolfgang Denk
2006-05-05 16:42 ` Tolunay Orkun
2006-05-05 16:45 ` Tolunay Orkun
2006-05-05 23:28 ` Wolfgang Denk
2006-05-08 13:09 ` Jerry Van Baren
2006-05-22 21:11 ` Tolunay Orkun
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=445691EF.1000401@orkun.us \
--to=listmember@orkun.us \
--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