From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [NEW_RELOC] arm1136, qong: add support for ELF relocations
Date: Tue, 12 Oct 2010 17:03:48 +0200 [thread overview]
Message-ID: <4CB478D4.3030702@free.fr> (raw)
In-Reply-To: <1286883087-362-1-git-send-email-hs@denx.de>
Le 12/10/2010 13:31, Heiko Schocher a ?crit :
> Signed-off-by: Wolfgang Denk<wd@denx.de>
> Signed-off-by: Heiko Schocher<hs@denx.de>
> ---
I assume this is [ELF_RELOC], not [NEW_RELOC], right? I'm asking because
using the same tag for all "elf_reloc" branch related patches makes it
easier to find them all back.
> diff --git a/arch/arm/cpu/arm1136/u-boot.lds b/arch/arm/cpu/arm1136/u-boot.lds
> + __dynsym_start = .;
> + .dynsym : { *(.dynsym) }
> +
> __got_start = .;
> . = ALIGN(4);
> .got : { *(.got) }
Do you need to keep .got in the linker file? I think it can be removed.
You could also add
/DISCARD/ : { *(.dynstr*) }
/DISCARD/ : { *(.dynamic*) }
/DISCARD/ : { *(.plt*) }
/DISCARD/ : { *(.interp*) }
/DISCARD/ : { *(.gnu*) }
At the end of the sections statement.
> diff --git a/include/configs/qong.h b/include/configs/qong.h
> +#define CONFIG_RELOC_FIXUP_WORKS
I believe this is now common to all ARMs, hence unneeded in config files.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-10-12 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 11:31 [U-Boot] [PATCH] [NEW_RELOC] arm1136, qong: add support for ELF relocations Heiko Schocher
2010-10-12 15:03 ` Albert ARIBAUD [this message]
2010-10-12 18:00 ` Wolfgang Denk
2010-10-13 5:31 ` Heiko Schocher
2010-10-13 5:27 ` Heiko Schocher
2010-10-13 6:40 ` Albert ARIBAUD
2010-10-13 5:57 ` [U-Boot] [PATCH v2] [ELF_RELOC] " Heiko Schocher
2010-10-13 8:30 ` 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=4CB478D4.3030702@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 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.