From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Sebastian Reichel <sre@kernel.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: errata 430973: move !ARCH_MULTIPLATFORM to Kconfig
Date: Mon, 27 Jul 2015 11:43:41 +0100 [thread overview]
Message-ID: <20150727104341.GG7576@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <55B6011C.9070906@codethink.co.uk>
On Mon, Jul 27, 2015 at 10:59:56AM +0100, Ben Dooks wrote:
> This isn't the only place ARM_ERRATA_430973 is used, and if
> you make it configurable on !ARCH_MULTIPLATFORM then it makes
> it impossible to use a ARCH_MULTIPLATFORM kernel on something
> that is an Cortex-A8.
>
> See arch/arm/mm/proc-v7-2level.S
That has been fixed so that the BTAC/BTB always gets flushed on each
context switch for all Cortex-A8 CPUs, but none of the other v7 CPUs.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-07-27 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 0:48 [PATCH 0/3] Another Errata 430973 Update Sebastian Reichel
2015-07-23 0:48 ` [PATCH 1/3] ARM: OMAP2+: N900: always enable IBE bit Sebastian Reichel
2015-07-23 7:28 ` Tony Lindgren
2015-10-05 13:53 ` Pavel Machek
2015-07-23 0:48 ` [PATCH 2/3] ARM: update errata 430973 documentation Sebastian Reichel
2015-07-23 0:48 ` [PATCH 3/3] ARM: errata 430973: move !ARCH_MULTIPLATFORM to Kconfig Sebastian Reichel
2015-07-23 12:35 ` Russell King - ARM Linux
2015-07-24 0:16 ` Sebastian Reichel
2015-07-26 22:51 ` Russell King - ARM Linux
2015-07-27 1:14 ` Sebastian Reichel
2015-07-27 9:59 ` Ben Dooks
2015-07-27 10:43 ` Russell King - ARM Linux [this message]
2015-07-27 17:36 ` Sebastian Reichel
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=20150727104341.GG7576@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®