From: Gerhard Jaeger <gjaeger@sysgo.com>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH][PPC32] Disable broken L2 cache on all 440GX revs
Date: Wed, 27 Oct 2004 15:20:51 +0200 [thread overview]
Message-ID: <200410271520.51333.gjaeger@sysgo.com> (raw)
In-Reply-To: <20041026135847.A16409@home.com>
On Dienstag 26 Oktober 2004 22:58, Matt Porter wrote:
> Always disable L2 cache on PPC440GX. All revs/speeds of silicon
> have parity error problems despite errata claims to the contrary.
> Signed-off-by: Matt Porter <mporter@kernel.crashing.org>
Hi Matt,
is there any test, with which you can reproduce these failures?
We have here custom boards based on the 440GX latest rev and
we need to use them with enabled L2 cache...
TIA,
Gerhard
prev parent reply other threads:[~2004-10-27 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 20:58 [PATCH][PPC32] Disable broken L2 cache on all 440GX revs Matt Porter
2004-10-27 13:20 ` Gerhard Jaeger [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=200410271520.51333.gjaeger@sysgo.com \
--to=gjaeger@sysgo.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mporter@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).