From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support
Date: Thu, 04 Nov 2010 23:06:28 +0100 [thread overview]
Message-ID: <4CD32E64.2080407@free.fr> (raw)
In-Reply-To: <4CD30BEC.1050203@ahsoftware.de>
Le 04/11/2010 20:39, Alexander Holler a ?crit :
> Sidenote: My toolchain is reproducable, but that means you have to
> compile a Gentoo system, because Gentoo is a source only distribution.
> So it isn't as comfortable as using binary distributions (here), but it
> has other advantages.
It probably has advantages, but having to adopt and run a given
distribution in order to get access to a given toolchain goes way beyond
what I am willing to do.
However, I think I have found the cause of the problem in my V3 build,
at least on an openrd_base.
V3 tried to overlay bss and rel.dyn so as to minimize the FLASH/NAND
footprint as well as RAM footprint. However, overlaying was done by
forcing .rel.dyn address to be equal to __bss_start and marking it
OVERLAY, which made it disappear from the .bin file, thus causing
relocation to fail.
I reversed the definition and order by forcing bss to start at
__rel_dyn_start, which worked but caused a linker warning that two
sections started at the same VMA -- the linker apparently does not take
into account that one of them, .bss, is NOLOAD.
I changed NOLOAD into OVERLAY, and then all worked: initial mapping (in
FLASH or in RAM when loaded from NAND) has text, data, rel.dyn and
dynsym bytes but not bss, which is fine since no code running there
should use it; final mapping (once relocated) has text, data and bss
without rel.dyn and dynsym using up RAM.
Tested on openrd_base, works.
V4 of patch set coming in the next few minutes.
> Regards,
>
> Alexander
Amicalement,
--
Albert.
prev parent reply other threads:[~2010-11-04 22:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 18:24 [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support Albert Aribaud
2010-11-03 18:24 ` [U-Boot] [PATCH V3 2/3] tx25: " Albert Aribaud
2010-11-03 18:24 ` [U-Boot] [PATCH V3 3/3] tx25: increase u-boot NAND size to match current build sizes Albert Aribaud
2010-11-03 18:27 ` [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support Albert ARIBAUD
2010-11-04 10:26 ` Alexander Holler
2010-11-04 10:46 ` Alexander Holler
2010-11-04 12:40 ` Albert ARIBAUD
2010-11-04 12:47 ` Alexander Holler
2010-11-04 12:55 ` Albert ARIBAUD
2010-11-04 13:18 ` Alexander Holler
2010-11-04 16:56 ` Albert ARIBAUD
2010-11-04 18:37 ` Alexander Holler
2010-11-04 18:42 ` Alexander Holler
2010-11-04 19:20 ` Albert ARIBAUD
2010-11-04 19:39 ` Alexander Holler
2010-11-04 22:06 ` Albert ARIBAUD [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=4CD32E64.2080407@free.fr \
--to=albert.aribaud@free.fr \
--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