public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Siarhei Siamashka <siarhei.siamashka@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 7/9] ARM: OMAP3: Introduce OMAP3 Cortex-A8 revision specific errata
Date: Tue, 3 Mar 2015 09:30:01 +0200	[thread overview]
Message-ID: <20150303093001.419b71be@i7> (raw)
In-Reply-To: <54EE2760.5010502@ti.com>

On Wed, 25 Feb 2015 13:49:52 -0600
Nishanth Menon <nm@ti.com> wrote:

> On 02/25/2015 05:15 AM, Paul Kocialkowski wrote:
> > Le mardi 24 f?vrier 2015 ? 16:57 -0600, Nishanth Menon a ?crit :
> >> 430973: Stale prediction on replaced inter working branch causes
> >> 	Cortex-A8 to execute in the wrong ARM/Thumb state
> >> Impacts: Everything lower than r2p1
> >> Work around: Set IBE to 1
> > 
> > According to the Linux kernel source, this should only affect r1p*
> > (hence, not r2p0):
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/mm/proc-v7.S#n321
> 
> I did look at the official Cortex-A8 errata doc (I think this is under
> NDA at least under TI).. Doc revision 20.0

The errata list is not that much secret. But more like all the
documents that you get from your employer are just under NDA by
default. Even though they might be also available from the other
sources.

I had the same problem. And specifically requested and obtained my
own personal copy of the Cortex-A8 errata list from ARM as a private
individual (to my gmail address, and clearly stating that I wanted it
for the purposes *not* related to my corporate job) :-)

I'm not allowed to share my copy with the other people though, so
everyone has to get it directly from ARM. I believe that that this
only requires filling in the registration form on the ARM website
and agreeing with the conditions.

There are also PDF documents from Freescale in public access, which
contain some Cortex-A8 errata information too:

    http://cache.freescale.com/files/32bit/doc/errata/IMX50CE.pdf
    http://www.freescale.com/docs/pcn_attachments/15760_IMX53CE_Rev4.pdf    

-- 
Best regards,
Siarhei Siamashka

  reply	other threads:[~2015-03-03  7:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 22:57 [U-Boot] [PATCH V2 0/9] ARM: OMAP3-DRA7: CP15 erratum workarounds and improvements Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 1/9] ARM: OMAP: Change set_pl310_ctrl_reg to be generic Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 2/9] ARM: OMAP3: Rename omap3.h to omap.h to be generic as all SoCs Nishanth Menon
2015-02-25 11:02   ` Paul Kocialkowski
2015-02-25 17:53     ` Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 3/9] ARM: OMAP3: Get rid of omap3_gp_romcode_call and replace with omap_smc1 Nishanth Menon
2015-02-25 11:06   ` Paul Kocialkowski
2015-02-24 22:57 ` [U-Boot] [PATCH V2 4/9] ARM: Provide a mechanism to invoke SoC specific errata WA for CP15 Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 5/9] ARM: DRA7 / OMAP5: Add workaround for ARM errata 798870 Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 6/9] configs: ti_omap5_common: Enable " Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 7/9] ARM: OMAP3: Introduce OMAP3 Cortex-A8 revision specific errata Nishanth Menon
2015-02-25 11:15   ` Paul Kocialkowski
2015-02-25 19:49     ` Nishanth Menon
2015-03-03  7:30       ` Siarhei Siamashka [this message]
2015-02-24 22:57 ` [U-Boot] [PATCH V2 8/9] configs: ti_omap3_common: Enable workaround for ARM errata 454179, 430973, 621766 Nishanth Menon
2015-02-25 11:19   ` Paul Kocialkowski
2015-02-25 11:31     ` Igor Grinberg
2015-02-25 12:27       ` Paul Kocialkowski
2015-02-25 14:32         ` menon.nishanth at gmail.com
2015-02-25 21:23           ` Paul Kocialkowski
2015-02-26  5:11             ` Nishanth Menon
2015-02-27 19:27               ` Paul Kocialkowski
2015-02-24 22:57 ` [U-Boot] [PATCH V2 9/9] ARM: OMAP5 / DRA7: Setup L2 Aux Control Register with recommended configuration Nishanth Menon

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=20150303093001.419b71be@i7 \
    --to=siarhei.siamashka@gmail.com \
    --cc=u-boot@lists.denx.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