From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: ARM Boot standard for passing device tree blob
Date: Fri, 26 Mar 2010 23:03:43 +0000 [thread overview]
Message-ID: <20100326230343.GC29179@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <fa686aa41003261252u7dc31bb6nca2e77ae8feb4355@mail.gmail.com>
On Fri, Mar 26, 2010 at 01:52:24PM -0600, Grant Likely wrote:
> I could change the statement to something like, "virtually tagged or
> indexed data cache(s) must be off", or drop the statement entirely
> since it is implied by the requirement that the MMU must be off.
1. We're not going down the path of having differing conditions for
different caches; to do so would mean that we'd need to have two
entirely different sets of code to handle booting in the kernel.
2. No ARM CPU supports having the D-cache enabled without the MMU; the
data cache needs to be told via the page tables what can be cached
and what can't - it needs to be told that RAM can cached but IO
devices must not be.
In short, the MMU must always be off, which in turn means the D-cache
must always be disabled.
next prev parent reply other threads:[~2010-03-26 23:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:11 RFC: ARM Boot standard for passing device tree blob Grant Likely
2010-03-25 21:04 ` Russell King - ARM Linux
2010-03-25 23:40 ` David Gibson
2010-03-26 0:23 ` Jeremy Kerr
2010-03-26 3:24 ` Grant Likely
2010-03-26 13:37 ` Catalin Marinas
2010-03-26 17:43 ` Mitch Bradley
2010-03-26 18:13 ` Grant Likely
2010-03-26 19:30 ` Nicolas Pitre
2010-03-26 19:52 ` Grant Likely
2010-03-26 23:03 ` Russell King - ARM Linux [this message]
2010-03-29 11:24 ` Dave P. Martin
2010-03-30 0:26 ` Jamie Lokier
2010-03-30 13:32 ` Dave P. Martin
2010-03-26 23:00 ` Russell King - ARM Linux
2010-03-31 1:10 ` Ben Dooks
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=20100326230343.GC29179@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).