diff options
author | Gabe Black <gabeblack@chromium.org> | 2013-07-01 05:03:47 -0700 |
---|---|---|
committer | Ronald G. Minnich <rminnich@gmail.com> | 2013-07-15 18:33:41 +0200 |
commit | 978c21512751c50ad92d459cbca39d98d9fc39a9 (patch) | |
tree | b3188c219b61b65c25929c53e9eade9e7505d1cc /src/device/oprom | |
parent | c392b6477f656331c7e19b22f6eb240cdd5465a1 (diff) | |
download | coreboot-978c21512751c50ad92d459cbca39d98d9fc39a9.tar.xz |
ARM: Define custom ELF headers for ARM.
At least when building with the gnu toolchain, the headers the linker
automatically generate save space for the actual ELF headers in one of the
loadable segments. This creates two problems. First, the data you intended to
be at the start of the image doesn't actually show up there, it's actually the
ELF headers. Second, the ELF headers are essentially useless for firmware
since there's currently nothing to tell you where they are, and even if there
was, there isn't much of a reason to look at them. They're useful in userspace
for, for instance, the dynamic linker, but not really in firmware.
This change adds a PHDRS construct to each of the linker scripts used on ARM
which define a single segment called to_load which does not have the flag set
which would tell the linker to put headers in it. The first section defined in
the script has ": to_load" to tell the linker which segment to put it in, and
from that point on the other sections go in there by default.
Change-Id: I24b721eb436d17afd234002ae82f9166d2fcf65d
Signed-off-by: Gabe Black <gabeblack@chromium.org>
Reviewed-on: http://review.coreboot.org/3580
Tested-by: build bot (Jenkins)
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
Diffstat (limited to 'src/device/oprom')
0 files changed, 0 insertions, 0 deletions