From: Detlef Vollmann <dv@vollmann.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFG_ENV_SECT_SIZE != CFG_ENV_SIZE
Date: Tue, 27 Mar 2007 23:07:15 +0200 [thread overview]
Message-ID: <46098783.715A4905@vollmann.ch> (raw)
In-Reply-To: 200703271327.00147.rgetz@blackfin.uclinux.org
Robin Getz wrote:
> In [u-boot.git] / common / env_flash.c around line 171 there is a
>
> #if CFG_ENV_SECT_SIZE > CFG_ENV_SIZE
>
> to be able to mix other data, and the environment info. (Where 'other data'
> could be U-Boot code).
>
> However, in an email a few days ago:
>
> On 3/26/07, Wolfgang Denk <wd@denx.de> wrote:
> > In message <46040C60.5070505@inaccessnetworks.com> you wrote:
> > > I have a flash chip with equally sized sectors and I don't want to waste
> > > an entire sector for the environment. I have the u-boot environment
> > > embedded in the u-boot sector. The declarations in my board file are:
> >
> > Do not do this. Do NOT do this. DO NOT DO THIS.
> >
> > Please never mix U-Boot code and environment data in one sector.
> > Always use a separate sector (or two) for the environment.
>
> If that is the recommendation (which is fine), why have this code snippet in
> there, and not add something like:
>
> #error Do not do this. Do NOT do this. DO NOT DO THIS.
There is other data that you can put into the same sector as the
U-Boot environment.
In our BSP, we use it for data written there at production,
in another project we use it for data that is read from Linux
but must stay outside the Linux kernel and filesystem image.
Detlef
--
Detlef Vollmann vollmann engineering gmbh
Linux and C++ for Embedded Systems http://www.vollmann.ch/
Linux for PXA270 Colibri module: http://www.vollmann.ch/en/colibri/
prev parent reply other threads:[~2007-03-27 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 17:27 [U-Boot-Users] CFG_ENV_SECT_SIZE != CFG_ENV_SIZE Robin Getz
2007-03-27 17:47 ` Wolfgang Denk
2007-03-27 21:07 ` Detlef Vollmann [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=46098783.715A4905@vollmann.ch \
--to=dv@vollmann.ch \
--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