From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: move firmware_ops to drivers/firmware
Date: Mon, 18 Nov 2013 17:14:45 +0000 [thread overview]
Message-ID: <20131118171445.GI16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAHkRjk5LBOFx3ir49RgEsaFwvp5UCpTjYFWto+URXebAsOP0RA@mail.gmail.com>
On Sun, Nov 17, 2013 at 03:59:04PM +0000, Catalin Marinas wrote:
> No L2x0 (L210, L220, PL310) cache on ARMv8. And here I strongly
> recommend the hardware people to make proper external caches which can
> be flushed by standard CPU instructions, not MMIO. Any such caches
> must be enabled by firmware before Linux starts.
Yea, and we've seen what a trainwreck that causes on 32-bit ARM with
the kernel exploding at boot time because of a dirty L2 cache.
prev parent reply other threads:[~2013-11-18 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 8:49 [PATCH] ARM: move firmware_ops to drivers/firmware Alexandre Courbot
2013-11-17 15:59 ` Catalin Marinas
2013-11-18 3:05 ` Alex Courbot
2013-11-18 11:58 ` Catalin Marinas
2013-11-18 17:03 ` Stephen Warren
2013-11-18 17:10 ` Russell King - ARM Linux
2013-11-18 17:18 ` Stephen Warren
2013-11-18 17:30 ` Catalin Marinas
2013-11-18 17:52 ` Stephen Warren
2013-11-19 11:38 ` Catalin Marinas
2013-11-18 19:04 ` Christopher Covington
2013-11-19 11:02 ` Catalin Marinas
2013-11-19 2:46 ` Alex Courbot
2013-11-19 12:26 ` Catalin Marinas
2013-11-19 14:29 ` Alexandre Courbot
2013-11-19 15:07 ` Catalin Marinas
2013-11-19 15:17 ` Alexandre Courbot
2013-11-18 17:00 ` Stephen Warren
2013-11-18 17:23 ` Catalin Marinas
2013-11-18 17:14 ` Russell King - ARM Linux [this message]
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=20131118171445.GI16735@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).