All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] CONFIG_SYS_ARM_WITHOUT_RELOC: document feature removal
Date: Wed, 29 Sep 2010 11:29:32 +0200	[thread overview]
Message-ID: <1285752572-2107-1-git-send-email-wd@denx.de> (raw)

Signed-off-by: Wolfgang Denk <wd@denx.de>
---
 doc/feature-removal-schedule.txt |   29 ++++++++++++++++++++++++++++-
 1 files changed, 28 insertions(+), 1 deletions(-)

diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt
index 5fe21e8..3879cb4 100644
--- a/doc/feature-removal-schedule.txt
+++ b/doc/feature-removal-schedule.txt
@@ -1,11 +1,38 @@
 The following is a list of files and features that are going to be
 removed from the U-Boot source tree.  Every entry should contain what
 exactly is going away, when it will be gone, why it is being removed,
-and who is going to be doing the work.  When the feature is removed
+and who is going to be doing the work.	When the feature is removed
 from U-Boot, its corresponding entry should also be removed from this
 file.
 
 ---------------------------
+What:	CONFIG_SYS_ARM_WITHOUT_RELOC option
+When:	After Release 2010.03
+
+Why:	The implementation of U-Boot for the ARM architecture has
+	been reworked to support relocation. This allows to
+	efficiently use the same U-Bot binary image on systems with
+	different RAM sizes, and brings the implementation much more
+	in line with the code used for example on Power Architecture
+	systems (eventually allowing to merge into common code). This
+	seems especailly interesting now that ARM is getting Device
+	Tree support as well.
+
+	All ARM boards need to be adapted to this new code, which
+	requires testing on the actual hardware, so this is a task
+	for the respective board maintainers or other users.
+
+	Please see the commit message of commit f1d2b31 for details:
+
+	http://git.denx.de/?p=u-boot.git;a=commit;h=f1d2b31
+
+	Support for CONFIG_SYS_ARM_WITHOUT_RELOC will be removed
+	after release v2010.03; all boards that have not been
+	converted by then, i. e. that are still broken then, are
+	considered unmaintained and without interest for the
+	community and will be removed as well.
+
+---------------------------
 
 What:	CONFIG_NET_MULTI option
 When:	Release 2009-11
-- 
1.7.2.3

             reply	other threads:[~2010-09-29  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29  9:29 Wolfgang Denk [this message]
2010-09-29  9:36 ` [U-Boot] [PATCH] CONFIG_SYS_ARM_WITHOUT_RELOC: document feature removal Rogan Dawes
2010-09-29  9:42   ` Wolfgang Denk
2010-09-29  9:37 ` Wolfgang Denk
2010-09-29  9:39 ` Wolfgang Wegner
2010-09-29  9:56   ` Wolfgang Denk
2010-10-04  8:58 ` Wolfgang Denk

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=1285752572-2107-1-git-send-email-wd@denx.de \
    --to=wd@denx.de \
    --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.