From: ian.campbell@citrix.com (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: update advice on kernel and FDT load address.
Date: Mon, 29 Jul 2013 13:56:18 +0100 [thread overview]
Message-ID: <1375102578-5869-1-git-send-email-ian.campbell@citrix.com> (raw)
Based on the discussion in [0]:
- Recommend that the kernel be placed under 128MiB ("for automatic RAM
location to work", says Nico)
- Recommend that DTB larger than ~16KiB be placed after the 128MiB boundary
(in order to avoid conflicting with the kernel decompressor, kernel is at
most 32MiB) and within the lowmem region. Somewhat arbitrarily recommend
placement below the 256MiB boundary, the real lowmem limit is likely up
around 600-800MiB but varies.
[0] http://article.gmane.org/gmane.linux.ports.arm.kernel/254538
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Dave Martin <dave.martin@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-arm-kernel at lists.infradead.org
---
Documentation/arm/Booting | 14 +++++++++++---
1 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/arm/Booting b/Documentation/arm/Booting
index 0c1f475..72c035e 100644
--- a/Documentation/arm/Booting
+++ b/Documentation/arm/Booting
@@ -125,6 +125,13 @@ with the caveat that it may not be located at physical address 0 since
the kernel interprets a value of 0 in r2 to mean neither a tagged list
nor a dtb were passed.
+If the DTB is larger than ~16KiB, such that placement in the first
+16KiB would lead to a conflict with the kernel loaded at 32KiB (as
+recommended below) which uses the memory between 16KiB-32KiB itself,
+then the DTB should be placed after the first 128MiB of RAM in order
+to avoid conflicting with the kernel decompressor. The recommnded
+placement in this case just below the 256MiB boundary.
+
5. Calling the kernel image
---------------------------
@@ -136,9 +143,10 @@ is stored in flash, and is linked correctly to be run from flash,
then it is legal for the boot loader to call the zImage in flash
directly.
-The zImage may also be placed in system RAM (at any location) and
-called there. Note that the kernel uses 16K of RAM below the image
-to store page tables. The recommended placement is 32KiB into RAM.
+The zImage may also be placed in system RAM and called there. The
+kernel should be placed in the first 128MiB of RAM. Note that the
+kernel uses 16KiB of RAM below the image to store page tables. The
+recommended placement is 32KiB into RAM.
In either case, the following conditions must be met:
--
1.7.2.5
next reply other threads:[~2013-07-29 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 12:56 Ian Campbell [this message]
2013-07-29 13:50 ` [PATCH] arm: update advice on kernel and FDT load address Will Deacon
2013-07-29 14:03 ` Ian Campbell
2013-07-30 3:05 ` Nicolas Pitre
2013-07-30 9:41 ` Will Deacon
2013-07-30 10:23 ` Russell King - ARM Linux
2013-07-30 13:18 ` Thomas Petazzoni
2013-07-30 13:56 ` Ian Campbell
2013-07-30 14:04 ` Russell King - ARM Linux
2013-07-30 14:30 ` Ian Campbell
2013-07-30 14:42 ` Russell King - ARM Linux
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=1375102578-5869-1-git-send-email-ian.campbell@citrix.com \
--to=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).