From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Cc: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Philippe Robin <Philippe.Robin-5wv7dgnIgG8@public.gmane.org>,
David Rusling <David.Rusling-5wv7dgnIgG8@public.gmane.org>,
Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
Dave P Martin <Dave.Martin-5wv7dgnIgG8@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: RFC: ARM Boot standard for passing device tree blob
Date: Fri, 26 Mar 2010 23:00:59 +0000 [thread overview]
Message-ID: <20100326230059.GB29179@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4BACF238.3040405-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
On Fri, Mar 26, 2010 at 07:43:20AM -1000, Mitch Bradley wrote:
> What is the reason for turning off the data caches? Leaving all caches
> turned on and coherent with one another has always worked well for me at
> the interface from firmware to a booted program.
With the data caches on, you need the MMU to be setup and operational.
That's impractical when you're passing control between differing pieces
of software which may have different ideas about how to setup the MMU
and where to place the page tables. If you accidentally overwrite the
page tables, things quickly become undebuggable.
next prev parent reply other threads:[~2010-03-26 23:00 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
[not found] ` <20100325210409.GH24984-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
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
[not found] ` <1269610665.807.51.camel-uqmqopRKlSLZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2010-03-26 17:43 ` Mitch Bradley
[not found] ` <4BACF238.3040405-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2010-03-26 18:13 ` Grant Likely
2010-03-26 19:30 ` Nicolas Pitre
[not found] ` <alpine.LFD.2.00.1003261435460.694-QuJgVwGFrdf/9pzu0YdTqQ@public.gmane.org>
2010-03-26 19:52 ` Grant Likely
[not found] ` <fa686aa41003261252u7dc31bb6nca2e77ae8feb4355-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-26 23:03 ` Russell King - ARM Linux
2010-03-29 11:24 ` Dave P. Martin
2010-03-30 0:26 ` Jamie Lokier
[not found] ` <20100330002638.GI9876-yetKDKU6eevNLxjTenLetw@public.gmane.org>
2010-03-30 13:32 ` Dave P. Martin
2010-03-26 23:00 ` Russell King - ARM Linux [this message]
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=20100326230059.GB29179@n2100.arm.linux.org.uk \
--to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
--cc=Dave.Martin-5wv7dgnIgG8@public.gmane.org \
--cc=David.Rusling-5wv7dgnIgG8@public.gmane.org \
--cc=Philippe.Robin-5wv7dgnIgG8@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.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