All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux-arm@myspectrum.nl (Jeroen Hofstee)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND][PATCH] ARM errata, 430973: update the affected revisions
Date: Fri, 10 Apr 2015 23:29:13 +0200	[thread overview]
Message-ID: <552840A9.8070406@myspectrum.nl> (raw)
In-Reply-To: <54EE2453.9080301@myspectrum.nl>

Hi again,

On 25-02-15 20:36, Jeroen Hofstee wrote:
> Hi,
>
> On 09-12-14 14:30, Jeroen Hofstee wrote:
>> From: Jeroen Hofstee <linux-arm@myspectrum.nl>
>>
>> Update the list of revisions subject to this errata.
>>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
>> Cc: Andreas Bie?mann <andreas.devel@googlemail.com>
>> Signed-off-by: Jeroen Hofstee <jhofstee@victronenergy.com>
>> ---
>> I don't have access to the AT400/AT401/AT490 document, but
>> Andreas was kind enough to provide this information, see
>> https://www.mail-archive.com/u-boot at lists.denx.de/msg156620.html
>>
>> Resending from an address which is subscribed to the ML...
>> ---
>>   arch/arm/Kconfig | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>> index 89c4b5c..a2202fa 100644
>> --- a/arch/arm/Kconfig
>> +++ b/arch/arm/Kconfig
>> @@ -1063,7 +1063,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
>> +      (r1p0..r1p3, r1p7) 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
>
> It seems this is not applied yet. For completeness, this only updates 
> the description
> of the workaround, so should be safe to apply. At the moment people 
> might disable
> this workaround (since the description says its not applicable) even 
> if the cpu does
> need this workaround.
>
> Please consider applying this,
>

ping

This still seems not be be applied. Please do update the documentation 
because it
causes segfaults when disabled wrongly. Below is a discussion about the 
topic as well.

Regards,
Jeroen

http://lists.denx.de/pipermail/u-boot/2014-December/198092.html

  reply	other threads:[~2015-04-10 21:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1418131842-6752-1-git-send-email-jhofstee@victronenergy.com>
2015-02-25 19:36 ` [RESEND][PATCH] ARM errata, 430973: update the affected revisions Jeroen Hofstee
2015-04-10 21:29   ` Jeroen Hofstee [this message]
2015-04-11  7:52     ` Russell King - ARM Linux
2015-04-11  9:25       ` Jeroen Hofstee
2015-04-13 14:39         ` Tony Lindgren
2015-04-13 16:28           ` Tony Lindgren
2015-04-13 16:28             ` Tony Lindgren
2015-04-13 21:35             ` Russell King - ARM Linux
2015-04-13 21:35               ` Russell King - ARM Linux
2015-04-13 21:45               ` Tony Lindgren
2015-04-13 21:45                 ` Tony Lindgren
2015-04-14 22:10               ` Jeroen Hofstee
2015-04-14 22:10                 ` Jeroen Hofstee

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=552840A9.8070406@myspectrum.nl \
    --to=linux-arm@myspectrum.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.