From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFD] store env size in env area (+ cookie + len)
Date: Thu, 12 Aug 2010 09:27:31 +0200 [thread overview]
Message-ID: <4C63A263.4060001@arcor.de> (raw)
In-Reply-To: <AANLkTi=+67z34H+R+tNab9MOPa55oLoRW0Vvs9BEEbf+@mail.gmail.com>
Am 12.08.2010 08:43, schrieb Frans Meulenbroeks:
> I've seen a few times that people get a u-boot with their board and
> want to use fw_setenv under linux to tweak with environment variables.
> This requires them to come up with an fw-env.config (if not provided).
> One of the things that I've seen, that some people have trouble with
> it is obtaining the proper size of the environment area to be stuffed
> in that file.
> Con: not compatible with current env layout so (without precautions) a
> new u-boot cannot use the old env and vice versa.
I didn't dig into the code but I don't think it is good idea to change
the environment format. There may be (or at least there is for my board)
code that scans the environment which is not derived from u-boot code. A
new header entry would break this code.
Why not store the size of the environment sector as env variable? The
size should be only needed for storing the environment and not for
loading (as it is terminated by a '\0'). So we could load the
environment, check for "env_size" and if its not there take the value
from fw_env.config
Matthias
next prev parent reply other threads:[~2010-08-12 7:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 6:43 [U-Boot] [RFD] store env size in env area (+ cookie + len) Frans Meulenbroeks
2010-08-12 6:57 ` Reinhard Meyer
2010-08-12 7:27 ` Matthias Weißer [this message]
2010-08-12 8:07 ` Alexander Stein
2010-08-12 8:41 ` Wolfgang Denk
[not found] ` <AANLkTi=LrEok8wT0Q0bt+rXYckPtFZasBRf=_1oeKCk4@mail.gmail.com>
2010-08-12 8:11 ` Matthias Weißer
2010-08-12 8:17 ` Reinhard Meyer
2010-08-12 8:35 ` Reinhard Meyer
2010-08-12 8:50 ` Wolfgang Denk
2010-08-12 8:47 ` Wolfgang Denk
2010-08-12 9:03 ` Reinhard Meyer
2010-08-12 10:15 ` Wolfgang Denk
2010-08-12 8:46 ` Wolfgang Denk
2010-08-12 8:38 ` Wolfgang Denk
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=4C63A263.4060001@arcor.de \
--to=weisserm@arcor.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 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.