public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] ARM: omap3: Add option to disable errata workarounds.
Date: Tue, 09 Jul 2013 17:18:32 +0200	[thread overview]
Message-ID: <51DC29C8.7060603@gmail.com> (raw)
In-Reply-To: <51DC25AC.7000507@andin.de>

Hi Andreas,

On 07/09/2013 05:01 PM, Andreas Naumann wrote:
>>>> It seems that all three ARM errata workarounds done in omap3 board-init
>>>> (#454179 #430973 #621766) are solved/not longer needed e.g. in the
>>>> AM/DM37xx chips. Other people have noticed this:
>>>> http://e2e.ti.com/support/arm/sitara_arm/f/791/t/254742.aspx
>>>>
>>>> When still applying them (especcially #430973), lots of segmentations
>>>> faults and other strange stuff begin to appear.
>>
>> I read your link the other way round. If the #430973 errata fix is _not_
>> applied to r3p2 it gives a lot of segfaults. Unfortunately the thread
>> has noc more information on that.
> 
> I dont know what bootloader the guy used, but he states that he needs to
> enable the errata fix in the kernel for the segfaults to disappear. I
> found exactly the same: Initially I had no errata fixes configured for
> the kernel, only when I added them the segfaults disappeared.
> However they also disappear if I remove the workarounds from kernel as
> well as u-boot, hence this patch.

Ok, understand.

<snip>

>> I join Albert's suggestion. Another solution could be to read the
>> silicon revision and enable erratum workarounds on that information. It
>> would be a step towards single binary.
> 
> So I'd rather do that, but can we map the ARM revision e.g. r2p1 to the
> TI die versions ES1.0, 1.1 and so on? Or can the ARM revision be read
> directly?

You should use the ARM revisions. They are available, but dunno how:

---8<---
~ cat /proc/cpuinfo
Processor	: ARMv7 Processor rev 2 (v7l)
BogoMIPS	: 512.57
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
--->8---

AFAIK is CPU variant 'r3' and CPU revision 'p2' for this cpuinfo.

Regards

Andreas Bie?mann

  reply	other threads:[~2013-07-09 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1373356832-28983-1-git-send-email-anaumann@ultratronik.de>
2013-07-09  8:08 ` [U-Boot] [RFC] ARM: omap3: Add option to disable errata workarounds Andreas Naumann
2013-07-09  9:10   ` Albert ARIBAUD
2013-07-09 10:42     ` Andreas Bießmann
2013-07-09 11:05       ` Albert ARIBAUD
2013-07-09 15:01       ` Andreas Naumann
2013-07-09 15:18         ` Andreas Bießmann [this message]
2013-07-09 15:49           ` Peter Meerwald

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=51DC29C8.7060603@gmail.com \
    --to=andreas.devel@googlemail.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