From: Tim Niemeyer <tim.niemeyer@corscience.de>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Thomas Weber <thomas.weber@corscience.de>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: regarding arm: update ARM_ERRATA_430973 Kconfig
Date: Thu, 28 Mar 2013 12:19:25 +0100 [thread overview]
Message-ID: <1364469565.2235.6.camel@herbert.er.corscience.de> (raw)
In-Reply-To: <alpine.DEB.2.01.1303261247320.18121@pmeerw.net>
Hi
Am Dienstag, den 26.03.2013, 12:57 +0100 schrieb Peter Meerwald:
> regarding your patch against arch/arm/Kconfig:
>
> @@ -1215,7 +1215,7 @@ config ARM_ERRATA_430973
> depends on CPU_V7
> help
> This option enables the workaround for the 430973 Cortex-A8
> - (r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
> + (r1p*) erratum. If a code sequence containing an ARM/Thumb
> interworking branch is replaced with another code sequence at the
> same virtual address, whether due to self-modifying code or virtual
> to physical address re-mapping, Cortex-A8 does not recover from the
>
>
> I am seeing strange segfault/illegal instructions fixed by enabling
> ARM_ERRATA_430973 on a TI OMAP3 DM3730, r3p2 IMHO (see below)
The only information i have is that it was fixed in r2p1. The statement
is from mru on:
http://www.beagleboard.org/irclogs/index.php?date=2013-02-18#T15:00:07
> ARM_ERRATA_430973 is relevant for which processors? have you checked the
> errata list? I had no luck obtaining it yet
No, i don't have it either.
--
Tim Niemeyer
Corscience GmbH & Co. KG
Henkestr. 91
D-91052 Erlangen
Germany
e-mail: tim.niemeyer@corscience.de
Internet: www.corscience.de
prev parent reply other threads:[~2013-03-28 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 11:57 regarding arm: update ARM_ERRATA_430973 Kconfig Peter Meerwald
2013-03-28 11:19 ` Tim Niemeyer [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=1364469565.2235.6.camel@herbert.er.corscience.de \
--to=tim.niemeyer@corscience.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=thomas.weber@corscience.de \
/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