From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_ENV_IS_EMBEDDED problems
Date: Sat, 29 Jan 2011 13:58:37 +0100 [thread overview]
Message-ID: <4D440EFD.70000@discworld.dascon.de> (raw)
Hi,
I am wondering how CONFIG_ENV_IS_EMBEDDED is supposed to work.
As far as I understand the code, it is set automatically by
environment.h in case the environment is in a sector in NOR flash that
overlaps with the u-boot code.
However, I see two problems:
- CONFIG_ENV_IS_EMBEDDED does not end up in autoconf.mk - however, it
is used in common/Makefile. This does not cause problems as long as
CONFIG_ENV_IS_IN_FLASH is also set, but the switch in the Makefile is
either useless or broken.
- include/common.h also contains #ifdef CONFIG_ENV_IS_EMBEDDED without
including environment.h, so that the definitions inside that block are
never reached.
Which of these is in error?
I think we could include environment.h from config.h - that would fix
all the problems, however that would mean environment.h ends up as a
dependency practically everywhere, which sounds bad.
cu
Michael
next reply other threads:[~2011-01-29 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 12:58 Michael Schwingen [this message]
2011-02-15 9:11 ` [U-Boot] CONFIG_ENV_IS_EMBEDDED problems Mike Frysinger
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=4D440EFD.70000@discworld.dascon.de \
--to=rincewind@discworld.dascon.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