mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Andreas Pretzsch <apr@cn-eng.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: imx5: add imx5_cpu_lowlevel_init and use in all boards
Date: Tue, 11 Nov 2014 15:01:10 +0100	[thread overview]
Message-ID: <1415714470.2815.3.camel@pengutronix.de> (raw)
In-Reply-To: <1415713894.20385.20.camel@ws-apr.office.loc>

Am Dienstag, den 11.11.2014, 14:51 +0100 schrieb Andreas Pretzsch:
> On Do, 2014-11-06 at 12:23 +0100, Lucas Stach wrote:
> > This is similar to what we do on imx6 and makes sure we
> > apply the errata workarounds early.
> 
> Without checking, doesn't this also apply to other Cortex-A8, like the
> TI AM335x and OMAP3 chips ?
> 
> Reading "ARM Cortex A8 errata" raises this thought...
> 
I don't know exactly for the OMAP3 chips, but at least AM335x production
silicon has r3p2 of the Cortex-A8 where this errata is already fixed in
hardware.

Regards,
Lucas

-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-11-11 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 11:23 [PATCH 1/2] ARM: implement recommended WAR for errata 709718 Lucas Stach
2014-11-06 11:23 ` [PATCH 2/2] ARM: imx5: add imx5_cpu_lowlevel_init and use in all boards Lucas Stach
2014-11-11 13:51   ` Andreas Pretzsch
2014-11-11 14:01     ` Lucas Stach [this message]
2014-11-06 12:20 ` [PATCH 1/2] ARM: implement recommended WAR for errata 709718 Holger Schurig
2014-11-06 12:44   ` Lucas Stach
2014-11-06 12:46   ` Eric Bénard
2014-11-07  6:55 ` Sascha Hauer

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=1415714470.2815.3.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=apr@cn-eng.de \
    --cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox