From: Matt Porter <mporter@kernel.crashing.org>
To: Neil Wilson <NWilson@Airspan.com>
Cc: Eugene Surovegin <ebs@ebshome.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: IBM 440GX, Ocotea...
Date: Wed, 24 Mar 2004 09:05:28 -0700 [thread overview]
Message-ID: <20040324090528.A14405@home.com> (raw)
In-Reply-To: <3506EDCDEC47904CBE6FD2E1DEEA8984020CF985@fs5.airspan.com>; from NWilson@Airspan.com on Wed, Mar 24, 2004 at 02:21:38PM -0000
On Wed, Mar 24, 2004 at 02:21:38PM -0000, Neil Wilson wrote:
>
> > > Does this mean that the L2 cache is unusable on current
> > revisions of
> > > the chip? [That's why we would like to use this chip.]
> >
> > Yes, we found problems with current chip revisions (A & B).
> > Ask your IBM contact for more information.
> >
>
> Can you elaborate a bit on this please ?, we are considering using this
> processor but would need the cache.
> I have had a quick look at the 2 errata docs I found on the IBM web
> site but must be missing the bit this relate to.
I know if I elaborated the "issue" it would violate the NDA that
we (my employer) are covered under. I assume Eugene is in a similar
position. You really should talk to IBM, that's what mvista is forced
to tell its 440GX customers. :)
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-24 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 14:21 IBM 440GX, Ocotea Neil Wilson
2004-03-24 16:05 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 11:02 Wolfgang Grandegger
2004-03-23 16:03 ` Tolunay Orkun
2004-03-23 16:44 ` Wolfgang Denk
2004-03-23 16:57 ` Jaap-Jan Boor
2004-03-23 17:38 ` Wolfgang Denk
2004-03-23 18:24 ` Dan Malek
2004-03-24 8:07 ` Jaap-Jan Boor
2004-03-24 22:25 ` Tom Rini
2004-03-25 7:57 ` Jaap-Jan Boor
2004-03-25 19:40 ` Tom Rini
2004-03-25 21:14 ` Tolunay Orkun
2004-03-25 21:20 ` Tom Rini
2004-03-25 21:23 ` Tolunay Orkun
2004-03-25 12:12 ` Paul Mackerras
2004-03-25 13:16 ` Jaap-Jan Boor
2004-03-23 18:31 ` Eugene Surovegin
2004-03-24 8:49 ` Wolfgang Grandegger
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=20040324090528.A14405@home.com \
--to=mporter@kernel.crashing.org \
--cc=NWilson@Airspan.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.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).