linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: ARM Boot standard for passing device tree blob
Date: Fri, 26 Mar 2010 13:37:45 +0000	[thread overview]
Message-ID: <1269610665.807.51.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <20100325210409.GH24984@n2100.arm.linux.org.uk>

On Thu, 2010-03-25 at 21:04 +0000, Russell King - ARM Linux wrote:
> On Wed, Mar 24, 2010 at 09:11:56AM -0600, Grant Likely wrote:
> > ===Required System State===
[...]
> > *IRQs disabled
> > *MMU off
> > *Instruction cache either on or off
> > *Data cache turned off
> 
> Would recommend saying "Data cache(s) turned off" so that L2 cache is
> included.

There are platforms where the L2 cache is turned on by the boot monitor
(secure monitor) and Linux has no control over it (I think OMAP).

-- 
Catalin

  parent reply	other threads:[~2010-03-26 13:37 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 [this message]
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
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=1269610665.807.51.camel@e102109-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.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).