From: Eugene Surovegin <ebs@ebshome.net>
To: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: IBM 440GX, Ocotea...
Date: Tue, 23 Mar 2004 10:31:22 -0800 [thread overview]
Message-ID: <20040323183122.GA6724@gate.ebshome.net> (raw)
In-Reply-To: <4057CCD40003780D@mssbzhh-int.msg.bluewin.ch>
On Tue, Mar 23, 2004 at 12:02:31PM +0100, Wolfgang Grandegger wrote:
>
> 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.
linuxppc-2.4
>
> 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?
unlikely. linuxpp_2_4_devel is officialy "dead" tree :).
> A more up-to-date implementation seems to be in the
> "linuxppc-2.4" tree. Are there some open issues or known
> problems?
New UIC mode isn't supported yet.
Work on GigE support is still not finished yet.
> 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.]
Yes, we found problems with current chip revisions (A & B).
Ask your IBM contact for more information.
> Does this tree support the 405GP and 440GP as well?
Yes.
> Could
> anybody make some comments on the stability? We currently
> use the "linuxppc_2_4_devel" tree for these processors
> with little problems.
I'm using linuxppc-2.4 as of 2.4.21 in production for 440GP,
440GX, 405GPr, 405EP based hardware.
Eugene.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-23 18:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 11:02 IBM 440GX, Ocotea 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 [this message]
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=20040323183122.GA6724@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wolfgang.grandegger@bluewin.ch \
/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).