From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/6] reboard: define CONFIG_SYS_SKIP_RELOC for all archs
Date: Sun, 11 Dec 2011 15:57:39 +0100 [thread overview]
Message-ID: <4EE4C4E3.2030306@aribaud.net> (raw)
In-Reply-To: <1323544576-25940-3-git-send-email-sjg@chromium.org>
Le 10/12/2011 20:16, Simon Glass a ?crit :
> We are introducing a new generic relocation features and we want this to
> be the default. So we need to opt all architectures out first. Some may
> never have relocation, but those that do will eventually move over to
> this generic relocation framework.
>
> This is part of the unified board effort, but since we are only dealing
> with relocation in this series, CONFIG_SYS_SKIP_RELOC is more appropriate
> than CONFIG_SYS_LEGACY_BOARD.
I'm afraid I haven't made myself clear on CONFIG_SYS_SKIP_RELOC. I did
not mean it to be an 'old vs new reloc' choice mechanism; I mean it to
be the controlling option for whether relocation happens at all or not.
I want a relocation skip option, because it is useful for boards which,
for any reason, know that they are already residing at the Right
Address(tm).
As far as an option to switch from old to new relocation... If there is
a consensus from all custodians that all arches should move to generic
relocation, then I think we should avoid allowing the older mechanism to
persist at all.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-12-11 14:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 19:16 [U-Boot] [PATCH v2 0/6] reboard: Introduce generic relocation feature Simon Glass
2011-12-10 19:16 ` [U-Boot] [PATCH v2 1/6] reboard: Create reloc.h and include it where needed Simon Glass
2011-12-11 14:52 ` Albert ARIBAUD
2011-12-11 21:33 ` Simon Glass
2011-12-11 21:45 ` Albert ARIBAUD
2011-12-11 21:45 ` Graeme Russ
2011-12-11 22:29 ` Albert ARIBAUD
2011-12-11 22:31 ` Albert ARIBAUD
2011-12-12 5:02 ` Simon Glass
2011-12-10 19:16 ` [U-Boot] [PATCH v2 2/6] reboard: define CONFIG_SYS_SKIP_RELOC for all archs Simon Glass
2011-12-11 14:57 ` Albert ARIBAUD [this message]
2011-12-12 5:06 ` Simon Glass
2011-12-10 19:16 ` [U-Boot] [PATCH v2 3/6] reboard: Add generic relocation feature Simon Glass
2011-12-10 19:16 ` [U-Boot] [PATCH v2 4/6] reboard: arm: Add processor function library Simon Glass
2011-12-11 14:16 ` Albert ARIBAUD
2011-12-12 5:24 ` Simon Glass
2011-12-22 6:23 ` Simon Glass
2011-12-10 19:16 ` [U-Boot] [PATCH v2 5/6] reboard: arm: Move over to generic relocation Simon Glass
2011-12-10 19:16 ` [U-Boot] [PATCH v2 6/6] reboard: arm: Remove unused code in start.S Simon Glass
2011-12-11 14:59 ` Albert ARIBAUD
2011-12-12 5:09 ` Simon Glass
2011-12-11 14:47 ` [U-Boot] [PATCH v2 0/6] reboard: Introduce generic relocation feature Albert ARIBAUD
2011-12-11 21:30 ` Simon Glass
2011-12-11 22:27 ` Albert ARIBAUD
2011-12-12 5:20 ` Simon Glass
2011-12-12 5:58 ` Graeme Russ
2011-12-16 1:09 ` 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=4EE4C4E3.2030306@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