From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [PATCH] 4xx: Workaround for CHIP_11 Errata
Date: Fri, 16 May 2008 06:57:00 +0200 [thread overview]
Message-ID: <200805160657.00300.sr@denx.de> (raw)
In-Reply-To: <20080515160734.4e4ea759@zod.rchland.ibm.com>
On Thursday 15 May 2008, Josh Boyer wrote:
> > "Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:
> > > This implements the recommended workaround for this errata for chips
> > > that use older versions of firmware that do not already handle it.
> > > The last 4KiB of memory are hidden from the kernel to prevent the
> > > problem transactions from occurring.
> >
> > Do you know which versions of firmware have this problem?
>
> Any U-Boot older than 1.3.3-rc1. Not sure about PIBS, but I don't
> think the version that is on my Bamboo board has a fix for it.
PIBS will definitely have this problem too. This errata is quite new on
440EP/GR.
Best regards,
Stefan
prev parent reply other threads:[~2008-05-16 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:43 [PATCH] 4xx: Workaround for CHIP_11 Errata Josh Boyer
2008-05-15 15:16 ` Stefan Roese
2008-05-15 20:31 ` Sean MacLennan
2008-05-15 21:07 ` Josh Boyer
2008-05-16 4:57 ` Stefan Roese [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=200805160657.00300.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
/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;
as well as URLs for NNTP newsgroup(s).