From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support
Date: Mon, 15 Nov 2010 12:01:40 +0100 [thread overview]
Message-ID: <4CE11314.50807@free.fr> (raw)
In-Reply-To: <20101114212240.5FA7914EA7E@gemini.denx.de>
Le 14/11/2010 22:22, Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message<4CDBA515.3050106@free.fr> you wrote:
>>
>> Alright. I'll prepare a V5 patch set with fixes to all ARM cpus.
>> Wolfgang, is a single *patch* for all cpus ok or do you want a single
>> *patchset* with one patch per cpu? Please tell me the single patch
>> approach is ok. :)
>
> It is. Thanks in advance.
ATM on mainline master branch only five ARM cpus (arm926ejs, arm1136,
arm1176, armv7 and pxa) have ELF relocation support. Others still use
GOT relocation (or the older fixed-location scheme maybe), which IIUC
means all boards using these other cpus are broken unless a maintainer
gets patches pulled in to support ELF relocs.
I therefore propose that V5 of my patch fixes arm926ejs, armv7, arm1136,
arm1176 and pxa only, and leave the ten other ARM cpus untouched. Board
maintainers who want to fix their board support for ELF relocs may have
to also fix their cpu if it is not yet.
Does everyone agree?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-11-15 11:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 22:22 [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support Albert Aribaud
2010-11-04 22:22 ` [U-Boot] [PATCH V4 2/2] tx25: " Albert Aribaud
2010-11-04 22:27 ` [U-Boot] [PATCH V4 1/2] arm926ejs: " Albert ARIBAUD
2010-11-09 13:49 ` Albert ARIBAUD
2010-11-05 8:38 ` Reinhard Meyer
2010-11-05 9:04 ` Albert ARIBAUD
2010-11-09 18:24 ` Daniel Hobi
2010-11-09 18:47 ` Albert ARIBAUD
2010-11-09 18:55 ` Albert ARIBAUD
2010-11-09 19:30 ` Andreas Bießmann
2010-11-10 12:31 ` Daniel Hobi
2010-11-10 12:48 ` Albert ARIBAUD
2010-11-10 13:24 ` Daniel Hobi
2010-11-11 8:11 ` Albert ARIBAUD
2010-11-14 21:22 ` Wolfgang Denk
2010-11-15 11:01 ` Albert ARIBAUD [this message]
2010-11-15 11:09 ` Andreas Bießmann
2010-11-15 11:43 ` Sebastien Carlier
2010-11-16 7:38 ` Andreas Bießmann
2010-11-15 11:13 ` Wolfgang Denk
2010-11-15 11:49 ` Albert ARIBAUD
2010-11-15 11:55 ` Loïc Minier
2010-11-15 12:03 ` Wolfgang Denk
2010-11-15 14:06 ` Loïc Minier
2010-11-15 14:29 ` Albert ARIBAUD
2010-11-15 15:09 ` Loïc Minier
2010-11-16 13:42 ` Peter Maydell
2010-11-16 13:54 ` [U-Boot] qemu-arm (was: [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support) Albert ARIBAUD
2010-11-16 14:49 ` Peter Maydell
2010-11-16 16:02 ` [U-Boot] qemu-arm Albert ARIBAUD
2010-11-15 12:00 ` [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support Reinhard Meyer
2010-11-15 12:02 ` Wolfgang Denk
2010-11-15 12:13 ` Albert ARIBAUD
2010-11-15 12:16 ` Bas Mevissen
2010-11-10 13:02 ` [U-Boot] Timer Statics (was: arm926ejs: fix linker file for newer ld support) Reinhard Meyer
2010-11-09 19:27 ` [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support Andreas Bießmann
2010-11-09 19:31 ` Albert ARIBAUD
2010-11-09 23:43 ` Eric Cooper
2010-11-10 7:53 ` Albert ARIBAUD
2010-11-10 14:20 ` Eric Cooper
2010-11-11 7:33 ` Albert ARIBAUD
2010-11-15 14:15 ` Daniel Hobi
2010-11-15 14:37 ` Albert ARIBAUD
2010-11-15 19:14 ` Eric Cooper
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=4CE11314.50807@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