From: Nye Liu <nyet@mrv.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FADS and ICU862 Environment problems
Date: Mon, 23 Jun 2003 14:42:11 -0700 [thread overview]
Message-ID: <20030623214211.GA10366@zumanetworks.com> (raw)
In-Reply-To: <20030623213554.0BF34C5FD7@atlas.denx.de>
On Mon, Jun 23, 2003 at 11:35:48PM +0200, Wolfgang Denk wrote:
> In message <20030623212553.GA10209@zumanetworks.com> you wrote:
> >
> > shouldn't the ifdef depend on ENV_IS_EMBEDDED? If that is set, even
> > in the ICU862 case, nothing in environment.c gets compiled (ALL of
> > the code is ifdef'ed out), and "environment" will be unresolved..
>
> ENV_IS_EMBEDDED? is not set on the ICU862 board, since the
> environment is located after the end of the U-Boot image, but not
> embedded within it.
>
> > > The #ifdef in "cpu/mpc8xx/start.S" makes sure that clear_bss() does
> > > not attempt to clear any memory that belongs to the environment.
> >
> > but only if ENV_IS_EMBEDDED is NOT set... unless i'm missing something
> > obvious?
>
> I see no discrepancy - ENV_IS_EMBEDDED is NOT set for ICU862
I'm sorry, i must be dense, i'm still not getting this (i do not know
anything about the ICU board) ...
So, leave in the ifdef ICU862 case, but what about FADS (and other
boards) which may or may not have ENV_IS_EMBEDDED set?
shouldn't they also NOT initialize past the bss into environment.o if
ENV_IS_EMBEDDED is not set, but not refer to the "environment" symbol if
ENV_IS_EMBEDDED IS set?
i.e.
#if !defined(ENV_IS_EMBEDDED) || defined(CONFIG_ICU862)
Sorry that this is taking so long to explain, but now i'm hopelessly
confused ;/
--
Nye Liu
nliu at mrv.com
(818) 772-6235x248
"Who would be stupid enough to quote a fictitious character?"
-- Don Quixote
next prev parent reply other threads:[~2003-06-23 21:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 1:45 [U-Boot-Users] FADS and ICU862 Environment problems Nye Liu
2003-06-21 0:21 ` Wolfgang Denk
2003-06-21 0:28 ` Nye Liu
2003-06-22 16:22 ` Wolfgang Denk
2003-06-23 21:25 ` Nye Liu
2003-06-23 21:35 ` Wolfgang Denk
2003-06-23 21:42 ` Nye Liu [this message]
2003-06-24 18:24 ` Wolfgang Denk
2003-06-24 20:28 ` Nye Liu
2003-06-24 20:38 ` Wolfgang Denk
2003-06-24 23:59 ` Nye Liu
2003-06-26 6:50 ` Wolfgang Denk
2003-06-26 21:40 ` Nye Liu
2003-06-26 22:03 ` Wolfgang Denk
2003-06-26 22:10 ` Nye Liu
2003-06-26 22:31 ` Wolfgang Denk
2003-06-26 22:41 ` Nye Liu
2003-06-26 23:10 ` Wolfgang Denk
2003-06-27 21:27 ` Nye Liu
2003-06-27 3:47 ` [U-Boot-Users] a small problem Yabo Ding
2003-06-27 6:51 ` [U-Boot-Users] " Wolfgang Denk
2003-06-27 7:56 ` Yabo Ding
2003-06-25 0:27 ` [U-Boot-Users] FADS and ICU862 Environment problems Nye Liu
2003-06-26 6:53 ` 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=20030623214211.GA10366@zumanetworks.com \
--to=nyet@mrv.com \
--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