linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Wolfgang Grandegger" <wolfgang.grandegger@bluewin.ch>
To: linuxppc-embedded@lists.linuxppc.org
Subject: IBM 440GX, Ocotea...
Date: Tue, 23 Mar 2004 12:02:31 +0100	[thread overview]
Message-ID: <4057CCD40003780D@mssbzhh-int.msg.bluewin.ch> (raw)


Hello,

we are currently trying to understand which PPC Linux
kernel tree is best suited for the IBM 440GX on the
Ocotea eval board. We would like to support the 405GP
and 440GP as well.

The Ocotea 440GX board seems to be supported in the
"linuxppc_2_4_devel" tree. Is this board configuration
up-to-date and still maintained?

A more up-to-date implementation seems to be in the
"linuxppc-2.4" tree. Are there some open issues or known
problems? I realized that the L2 cache has been disabled
recently:

  $ cat arch/ppc/platforms/ocotea.c
  ...
  /* Disable L2-Cache due to hardware issues */
  ibm440gx_l2c_disable();

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.]

Does this tree support the 405GP and 440GP as well? Could
anybody make some comments on the stability? We currently
use the "linuxppc_2_4_devel" tree for these processors
with little problems.

It would be nice if somebody could shed some light on
these issues.

TIA.

Wolfgang.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-03-23 11:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 11:02 Wolfgang Grandegger [this message]
2004-03-23 16:03 ` IBM 440GX, Ocotea 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
2004-03-24  8:59   ` IBM 440GX performance (was Re: IBM 440GX, Ocotea...) Wolfgang Grandegger
2004-03-24 12:24     ` USB problem on 2.4.20 song sam
     [not found]     ` <20040324234025.GA11675@gate.ebshome.net>
2004-03-25  8:02       ` IBM 440GX performance (was Re: IBM 440GX, Ocotea...) Gerhard Jaeger
2004-03-25 19:43       ` Eugene Surovegin
  -- strict thread matches above, loose matches on Subject: below --
2004-03-24 14:21 IBM 440GX, Ocotea Neil Wilson
2004-03-24 16:05 ` Matt Porter

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=4057CCD40003780D@mssbzhh-int.msg.bluewin.ch \
    --to=wolfgang.grandegger@bluewin.ch \
    --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).