From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/7] reboard: Add generic relocation feature
Date: Wed, 07 Dec 2011 08:38:40 +0100 [thread overview]
Message-ID: <4EDF1800.8060409@aribaud.net> (raw)
In-Reply-To: <201111292158.12478.vapier@gentoo.org>
Le 30/11/2011 03:58, Mike Frysinger a ?crit :
> On Tuesday 29 November 2011 18:49:58 Graeme Russ wrote:
>> On Wed, Nov 30, 2011 at 10:41 AM, Simon Glass wrote:
>>> On Tue, Nov 29, 2011 at 3:20 PM, Mike Frysinger wrote:
>>>> On Tuesday 29 November 2011 17:15:18 Simon Glass wrote:
>>>>> On Mon, Nov 28, 2011 at 7:07 PM, Mike Frysinger wrote:
>>>>>> On Monday 21 November 2011 18:57:56 Simon Glass wrote:
>>>>>>> --- /dev/null
>>>>>>> +++ b/board/Makefile
>>>>>>>
>>>>>>> +ifndef CONFIG_SYS_LEGACY_BOARD
>>>>>>> +COBJS += reloc.o
>>>>>>> +endif
>>>>>>
>>>>>> i don't think relocation should be tied "legacy board". not all
>>>>>> arches do relocation at all, which means they might never opt in to
>>>>>> this aspect.
>>>>>
>>>>> If they don't do reloc then when we move them over we should add a
>>>>> CONFIG for this I think. But would prefer to wait until we have an
>>>>> arch moving over that requires no relocation, before addressing this.
>>>>
>>>> Blackfin does no relocation, so i'd be annoyed to have to carry a define
>>>> like "LEGACY_BOARD" forever ;)
>>>
>>> Would you be happier with CONFIG_ARCH_NO_RELOCATION?
>>
>> CONFIG_SYS_NO_RELOC
>
> either is fine by me
> -mike
CONFIG_SYS_SKIP_RELOC clearly states there is some usual step we're
skipping, plus we could homogeneize with other config settings that
"SKIP" some step.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-12-07 7:38 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 23:57 [U-Boot] [RFC PATCH 0/7] reboard: Introduce generic relocation feature Simon Glass
2011-11-21 23:57 ` [U-Boot] [RFC PATCH 1/7] reboard: define CONFIG_SYS_LEGACY_BOARD everywhere Simon Glass
2011-11-29 3:11 ` Mike Frysinger
2011-11-29 20:08 ` Simon Glass
2011-11-29 21:40 ` Mike Frysinger
2011-11-29 22:09 ` Simon Glass
2011-11-29 23:19 ` Mike Frysinger
2011-11-29 23:40 ` Simon Glass
2011-12-07 8:15 ` Albert ARIBAUD
2011-12-07 16:28 ` Simon Glass
2011-12-05 6:42 ` Aneesh V
2011-11-21 23:57 ` [U-Boot] [RFC PATCH 2/7] reboard: Add generic link symbols Simon Glass
2011-11-29 2:59 ` Mike Frysinger
2011-12-07 22:37 ` Simon Glass
2011-11-21 23:57 ` [U-Boot] [RFC PATCH 3/7] reboard: Add generic relocation feature Simon Glass
2011-11-29 3:07 ` Mike Frysinger
2011-11-29 22:15 ` Simon Glass
2011-11-29 23:00 ` Graeme Russ
2011-11-29 23:20 ` Mike Frysinger
2011-11-29 23:41 ` Simon Glass
2011-11-29 23:49 ` Graeme Russ
2011-11-30 2:58 ` Mike Frysinger
2011-12-07 7:38 ` Albert ARIBAUD [this message]
2011-12-08 0:35 ` Mike Frysinger
2011-12-09 3:36 ` Simon Glass
2011-12-07 22:45 ` Simon Glass
2011-12-07 22:54 ` Graeme Russ
2011-12-07 22:55 ` Simon Glass
2011-11-21 23:57 ` [U-Boot] [RFC PATCH 4/7] reboard: arm: Add relocation function Simon Glass
2011-11-21 23:57 ` [U-Boot] [RFC PATCH 5/7] reboard: arm: Add processor function library Simon Glass
2011-11-29 3:12 ` Mike Frysinger
2011-12-07 7:44 ` Albert ARIBAUD
2011-12-07 16:24 ` Simon Glass
2011-11-21 23:57 ` [U-Boot] [RFC PATCH 6/7] reboard: arm: Move over to generic relocation Simon Glass
2011-11-29 3:14 ` Mike Frysinger
2011-12-09 3:41 ` Simon Glass
2011-11-21 23:58 ` [U-Boot] [RFC PATCH 7/7] reboard: arm: Remove unused code in start.S Simon Glass
2011-11-29 3:15 ` Mike Frysinger
2011-12-09 3:42 ` Simon Glass
2011-11-28 23:45 ` [U-Boot] [RFC PATCH 0/7] reboard: Introduce generic relocation feature Tom Rini
2011-12-07 1:56 ` Simon Glass
2011-12-07 2:56 ` Graeme Russ
2011-12-07 3:25 ` Simon Glass
2011-12-07 3:36 ` Graeme Russ
2011-12-07 23:29 ` Simon Glass
2011-12-07 8:10 ` Albert ARIBAUD
2011-12-09 3:34 ` Simon Glass
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=4EDF1800.8060409@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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