From: Robin Murphy <robin.murphy@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: vladimir.murzin@arm.com, linux-kernel@vger.kernel.org,
dianders@chromium.org, kever.yang@rock-chips.com,
linux-arm-kernel@lists.infradead.org, armlinux@m.disordat.com,
Nisal Menuka <nisalmenuka23@gmail.com>
Subject: Re: [PATCH] Remove ARM errata Workarounds 458693 and 460075
Date: Tue, 2 May 2017 13:27:54 +0100 [thread overview]
Message-ID: <e7310f9f-96a3-186a-7e5d-7da902bc76f8@arm.com> (raw)
In-Reply-To: <20170418155725.GG27592@e104818-lin.cambridge.arm.com>
On 18/04/17 16:57, Catalin Marinas wrote:
> On Sun, Apr 16, 2017 at 09:04:46AM +0100, Russell King - ARM Linux wrote:
>> On Sat, Apr 15, 2017 at 07:06:06PM -0500, Nisal Menuka wrote:
>>> According to ARM, these errata exist only in a version of Cortex-A8
>>> (r2p0) which was never built. Therefore, I believe there are no platforms
>>> where this workaround should be enabled.
>>> link :http://infocenter.arm.com/help/index.jsp?topic=
>>> /com.arm.doc.faqs/ka15634.html
>>
>> These were submitted by ARM Ltd back in 2009 - if the silicon was never
>> built, there would've been no reason to submit them. Maybe Catalin can
>> shed some light on this, being the commit author who introduced these?
>
> We normally try not to submit errata workarounds for revisions that are
> not going to be built/deployed. It's possible that at the time there
> were plans for r2p0 to be licensed and built (not just FPGA) but I don't
> really remember the details. The A8 errata document indeed states that
> r1p0 and r2p0 are obsolete but this can mean many things (like not
> available to license).
>
> I'll try to see if any of the A8 past product managers know anything
> about this. In the meantime, I would leave them in (no run-time
> overhead).
FWIW, I just fired up a RealView PB-A8 board to check, and that reports
r1p1. True, it's not strictly a real silicon implementation (I think
it's one of the structured ASIC test chips), but since it was, as far as
I'm aware, a commercially-available development system, it's not
impossible that someone may still own and use one of these beasts.
Robin.
next prev parent reply other threads:[~2017-05-02 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 0:06 Nisal Menuka
2017-04-16 8:04 ` Russell King - ARM Linux
2017-04-18 15:57 ` Catalin Marinas
2017-05-02 12:27 ` Robin Murphy [this message]
2017-05-02 15:21 ` Catalin Marinas
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=e7310f9f-96a3-186a-7e5d-7da902bc76f8@arm.com \
--to=robin.murphy@arm.com \
--cc=armlinux@m.disordat.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nisalmenuka23@gmail.com \
--cc=vladimir.murzin@arm.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®