From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] ti, am3517: errata 430973 workaround
Date: Wed, 10 Dec 2014 11:25:28 +0100 [thread overview]
Message-ID: <54881F98.7060908@myspectrum.nl> (raw)
In-Reply-To: <CAOCHtYitAC0CG5OZ41pYLJqHw2MnAT_+0vGJPua=fF8mZamhgA@mail.gmail.com>
Hello Robert, Andreas,
On 09-12-14 22:45, Robert Nelson wrote:
> On Mon, Dec 8, 2014 at 4:19 PM, Jeroen Hofstee <jeroen@myspectrum.nl> wrote:
>> Hi,
>>
>> A while ago [1], a RFC was posted to disable workaround for
>> besides others, errata 430973. It is a bit unclear to me which
>> revision actually need this workaround, but as suggested in
>> [2] also enabling this workaround in Linux seem to make some
>> weird problems go away in linux (signal 4, bad instruction,
>> 11 segfaults etc).
>>
>> As said, I am a bit in doubt why this works. The board in question
>> is a tam3517 derived one:
>>
>> cat /proc/cpuinfo
>> Processor : ARMv7 Processor rev 7 (v7l)
>> BogoMIPS : 397.57
>> Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
>> CPU implementer : 0x41
>> CPU architecture: 7
>> CPU variant : 0x1
>> CPU part : 0xc08
>> CPU revision : 7
>>
>> Which makes this a r1p7 I assume, and hence the workaround
>> of linux, CONFIG_ARM_ERRATA_430973, "This option enables the
>> workaround for the 430973 Cortex-A8 (r1p0..r1p2) erratum",
>> should not be needed it seems.
> Digging thru my old beagle notes 430973 is also needed for "r1p3"
> (dm3730/bb-xm), so that config option was never updated since the
> errata was first discovered in r1p2 devices..
>
> Fixed in r2p1 sounds about right, as i know for sure it works fine in
> 'r3p2' (am335x/bbb)
Thanks for the clarification. I sent a patch to the linux folks
to update the help text.
Regards,
Jeroen
prev parent reply other threads:[~2014-12-10 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 22:19 [U-Boot] ti, am3517: errata 430973 workaround Jeroen Hofstee
2014-12-09 8:51 ` Andreas Bießmann
2014-12-09 21:45 ` Robert Nelson
2014-12-10 10:25 ` Jeroen Hofstee [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=54881F98.7060908@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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