From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH] Avoid R_ARM_ABS32 for bss start and end references -- tester(s) needed for non-ARM architectures also
Date: Thu, 14 Feb 2013 09:43:06 +0100 [thread overview]
Message-ID: <511CA39A.4040200@gmail.com> (raw)
In-Reply-To: <20130214091059.5df45b00@lilith>
Hi Albert,
On 02/14/2013 09:10 AM, Albert ARIBAUD wrote:
> Hi Luka,
>
> On Thu, 14 Feb 2013 01:17:24 +0100, Luka Perkov <luka@openwrt.org>
> wrote:
>
>> On Tue, Feb 12, 2013 at 06:27:27PM +0100, Albert ARIBAUD wrote:
>>> This patch SHOULD NOT BE applied in any official U-boot tree! It is
>>> submitted as an RFC and a request to test.
>>
>> I can confirm that this patch applied on top of 9c748e0 worked for my
>> two kirkwood boards. One is in mainline (ib62x0) and one is not.
>>
>> Tested-by: Luka Perkov <luka@openwrt.org>
>
> Thanks Luka!
>
> Anyone available to test on a non-ARM architecture? I can provide the
> patched linker script if testing on a mainline-supported target.
I can on AVR32, would you provide the linker script (atstk1002
preferred, but AFAIR all AVR32 targets use the same linker script)?
I think we should apply this change on top of "Refactor linker-generated
arrays", am I right?
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2013-02-14 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 17:27 [U-Boot] [RFC] [PATCH] Avoid R_ARM_ABS32 for bss start and end references Albert ARIBAUD
2013-02-14 0:17 ` Luka Perkov
2013-02-14 8:10 ` [U-Boot] [RFC] [PATCH] Avoid R_ARM_ABS32 for bss start and end references -- tester(s) needed for non-ARM architectures also Albert ARIBAUD
2013-02-14 8:43 ` Andreas Bießmann [this message]
2013-02-14 10:31 ` Albert ARIBAUD
2013-02-14 10:59 ` Andreas Bießmann
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=511CA39A.4040200@gmail.com \
--to=andreas.devel@googlemail.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