mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Meerwald <pmeerw@pmeerw.net>
To: Tim Niemeyer <tim.niemeyer@corscience.de>,
	Thomas Weber <thomas.weber@corscience.de>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: regarding arm: update ARM_ERRATA_430973 Kconfig
Date: Tue, 26 Mar 2013 12:57:07 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.01.1303261247320.18121@pmeerw.net> (raw)

Hello,

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) 

ARM_ERRATA_430973 is relevant for which processors? have you checked the 
errata list? I had no luck obtaining it yet


cat /proc/cpuinfo 
Processor       : ARMv7 Processor rev 2 (v7l)
BogoMIPS        : 313.29
Features        : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x3
CPU part        : 0xc08
CPU revision    : 2

thanks, p.

-- 

Peter Meerwald
+43-664-2444418 (mobile)

             reply	other threads:[~2013-03-26 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 11:57 Peter Meerwald [this message]
2013-03-28 11:19 ` Tim Niemeyer

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=alpine.DEB.2.01.1303261247320.18121@pmeerw.net \
    --to=pmeerw@pmeerw.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=thomas.weber@corscience.de \
    --cc=tim.niemeyer@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

all inboxes | Powered by JetHome®