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] Problems with fw_printenv
Date: Thu, 04 Mar 2010 09:55:10 +0100	[thread overview]
Message-ID: <20100304085510.9A37128BBC@gemini.denx.de> (raw)
In-Reply-To: <4B8F4FBB.8040204@chess.nl>

Dear Ronald Kortekaas,

In message <4B8F4FBB.8040204@chess.nl> you wrote:
>
> >> The problem was the definition of CONFIG_ENV_ADDR_REDUND after undefining this it works.
> >>      
> > Do you understand the consequewnces of removing this definition? Are
> > you sure you really want to do this?
...
> No, I'm not understanding the consequences of removing this definition. 
> I can't find a description what is does.

Hm... You can't? Didn't you find the README ?

> But if I want to use the CONFIG_ENV_ADDR_REDUND. Is there a way to solve 
> this problem?

Of course there is. You just have to adapt the fw_config file for
redundant environment, i. e. add entries for both copies of the
environment data.


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
In an organization, each person rises to the level of his own  incom-
petency                                         - The Peter Principle

  reply	other threads:[~2010-03-04  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 10:25 [U-Boot] Problems with fw_printenv Ronald Kortekaas
2010-03-03 20:21 ` Wolfgang Denk
2010-03-04  6:14   ` Ronald Kortekaas
2010-03-04  8:55     ` Wolfgang Denk [this message]
2010-03-04  7:26   ` Ronald Kortekaas
2010-03-04  8:57     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2010-03-03  9:14 Ronald Kortekaas

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=20100304085510.9A37128BBC@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