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 11:59:36 +0100 [thread overview]
Message-ID: <511CC398.7060904@gmail.com> (raw)
In-Reply-To: <20130214113157.1e2729bb@lilith>
Hi Albert,
On 02/14/2013 11:31 AM, Albert ARIBAUD wrote:
> Hi Andreas,
>
> On Thu, 14 Feb 2013 09:43:06 +0100, "Andreas Bie?mann"
> <andreas.devel@googlemail.com> wrote:
>
>> Hi Albert,
>>
>> On 02/14/2013 09:10 AM, Albert ARIBAUD wrote:
>> I can on AVR32, would you provide the linker script (atstk1002
>> preferred, but AFAIR all AVR32 targets use the same linker script)?
>
> Yes, there is a single linker script for AVR. Do you have a URL handy
> for the AVR toolchain you're using?
No, I use a self patched OSELAS toolchain, I like to push the changes
mainline but haven't managed yet.
I know buildroot and openwrt has toolchain support for avr32 and AFAIR
Mike Frysinger has a set of pre-compiled toolchains including a AVR32
one [1].
>
>> I think we should apply this change on top of "Refactor linker-generated
>> arrays", am I right?
>
> It uses the same methods as the linker lists one, and eventually it
> will be part of the series, but it is autonomous -- no need to apply
> anything else.
Ok.
Best regards
Andreas Bie?mann
[1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/117404
prev parent reply other threads:[~2013-02-14 10:59 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
2013-02-14 10:31 ` Albert ARIBAUD
2013-02-14 10:59 ` Andreas Bießmann [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=511CC398.7060904@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 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.