All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC405EX CHIP_21 erratum
Date: Mon, 2 May 2011 13:50:42 +0200	[thread overview]
Message-ID: <201105021350.43119.sr@denx.de> (raw)
In-Reply-To: <4DBAED2A.4030705@harris.com>

Hi Steve,

On Friday 29 April 2011 18:54:02 Steven A. Falco wrote:
> We've been bitten by the PPC405EX CHIP_21 erratum.

How did it affect you exactly? Was an incorrect PVR detected? Did this result 
in some problems (Linux etc)?

> I've looked through the
> U-Boot code, but it doesn't appear that there is a work-around for this
> one.

Correct, there currently is no workaround.
 
> The following patch is my adaptation of AMCC's suggestion as to the fix. 
> But I have to say that I don't care for it, if for no other reason that it
> will break if a rev E comes out.
> 
> Also, I made it #ifdef'd on CONFIG_405EX, but it will not work on a 405EXr.
> And I have seen a 405EX report its PVR as if it were a 405EXr.  It's not
> looking good for the suggested work-around.
>
> AMCC claims this can be fixed in hardware, by always doing a double reset.
> Naturally, that is hard to implement and would mean massive rework of
> existing boards.

Yes, there are many 405EX(r) boards in the field already. Such an hardware 
workaround should really be avoided if possible.

> So I am contemplating a different work-around, whereby software always
> resets the board on a cold boot (if such a thing can be reliably
> detected).  That would hopefully be the equivalent of the hardware double
> reset, and would not be dependent on specific PVR values, making it more
> "future proof".
> 
> Has anyone else run across this?  Do you have similar concerns about the
> patch?

No, I have not seen this problem before. And yes, I would also prefer your 
"alternative suggestion", with the always reboot after powerup optionally 
built into the U-Boot image. But as you already mentioned, we would have to 
find a way to reliably detect the powerup reset, so that we don't end in an 
reset-loop.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2011-05-02 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 16:54 [U-Boot] PPC405EX CHIP_21 erratum Steven A. Falco
2011-05-02 11:50 ` Stefan Roese [this message]
     [not found] <4DBF1F33.4040101@harris.com>
2011-05-02 21:44 ` Steven A. Falco
2011-05-03 13:07   ` Stefan Roese

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=201105021350.43119.sr@denx.de \
    --to=sr@denx.de \
    --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 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.