From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] AT91: problems master vs. next
Date: Tue, 21 Sep 2010 16:36:47 +0200 [thread overview]
Message-ID: <4C98C2FF.3020103@emk-elektronik.de> (raw)
In-Reply-To: <4C98BEC7.9090500@emk-elektronik.de>
Reinhard Meyer schrieb:
> Therefore I strongly suggest that all extras (PIC) needed solely for relocation
> should be switchable OFF by a configuration option. Who does need that
> relocation in the first place? For years ARM did work without it; why now
> blowing up the code?
Sorry, to be precise: the option CONFIG_SYS_ARM_WITHOUT_RELOC should stay as a
permanent feature.
However, when I compile with that option defined in my board-config.h I get the
following warnings for EVERY file:
/home/reinhard/embedded/u-boot/include/configs/top9000_9xe.h:74:1: warning: "CONFIG_SYS_ARM_WITHOUT_RELOC" redefined
<command-line>: warning: this is the location of the previous definition
In file included from /home/reinhard/embedded/u-boot/include/config.h:4,
from /home/reinhard/embedded/u-boot/include/common.h:37,
from stmicro.c:30:
because of that recursion:
+ifdef CONFIG_SYS_ARM_WITHOUT_RELOC
+PLATFORM_CPPFLAGS += -DCONFIG_SYS_ARM_WITHOUT_RELOC
+endif
The code size changes from 223592 to 229792 which is more acceptable, but
I still does crash (I will look into that soon).
Reinhard
next prev parent reply other threads:[~2010-09-21 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 12:39 [U-Boot] AT91: problems master vs. next Reinhard Meyer
2010-09-21 14:00 ` Albert ARIBAUD
2010-09-21 14:18 ` Reinhard Meyer
2010-09-21 14:36 ` Reinhard Meyer [this message]
2010-09-21 17:27 ` Wolfgang Denk
2010-09-21 17:27 ` Wolfgang Denk
2010-09-22 7:14 ` [U-Boot] ARM Relocation compiler and linker switches (was: AT91: problems master vs. next) Albert ARIBAUD
2010-09-21 14:40 ` [U-Boot] AT91: problems master vs. next Stefan Roese
2010-09-21 14:50 ` Reinhard Meyer
2010-09-21 17:27 ` 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=4C98C2FF.3020103@emk-elektronik.de \
--to=u-boot@emk-elektronik.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.