From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: mm: Ignore memory banks which are in front of the kernel when HIGHMEM is ON
Date: Wed, 13 Feb 2013 15:56:55 +0000 [thread overview]
Message-ID: <20130213155654.GD17833@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAHTX3dJXtx5V2SN4Wd7mrnhUzMyK86vT_h_xLOzmQKGo3rcDqQ@mail.gmail.com>
On Wed, Feb 13, 2013 at 04:52:50PM +0100, Michal Simek wrote:
> This case should probably end up on device-tree rule (+dtc fault).
> Not sure if memory banks should be ordered or not. Rob and Grant any thought?
They _are_ ordered by memblock, because memblock always arranges the
banks in ascending physical address order - and it will merge
contiguous banks together irrespective of what order they appear as.
So you can't do something like bank 0: 0x60000000-0x70000000, bank 1:
0x50000000-0x60000000. You'll end up with a single memblock entry for
0x50000000-0x70000000.
next prev parent reply other threads:[~2013-02-13 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 8:58 [PATCH 1/2] arm: mm: Ignore memory banks which are in front of the kernel when HIGHMEM is ON Michal Simek
2013-02-13 8:58 ` [PATCH 2/2] arm: mm: Add support for booting the kernel out of the first 16MB of memory Michal Simek
2013-02-13 9:03 ` [PATCH 1/2] arm: mm: Ignore memory banks which are in front of the kernel when HIGHMEM is ON Russell King - ARM Linux
2013-02-13 14:39 ` Michal Simek
2013-02-13 14:52 ` Russell King - ARM Linux
2013-02-13 15:52 ` Michal Simek
2013-02-13 15:56 ` Russell King - ARM Linux [this message]
2013-02-14 5:01 ` Nicolas Pitre
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=20130213155654.GD17833@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).