From: David Updegraff <dave@cray.com>
To: Cindy Peters <cinpet@adaptivemicro.com>
Cc: Stefan Roese <stefan.roese@esd-electronics.com>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: AW: New Linux PowerPC development
Date: Tue, 24 Jul 2001 10:35:52 -0500 [thread overview]
Message-ID: <3B5D95D8.3040702@cray.com> (raw)
In-Reply-To: EFEAIMDCOOOHIEPHDNFJCEDBDAAA.stefan.roese@esd-electronics.com
Hi.
We also use 405GP, and have a tentatively "stable" kernel from a 2.4.2 tree.
The combination of these tools with PPCBOOT has been a really nice, open
environment to work in...
>>We feel we would have to design an interface into an FPGA. It doesn't
>>support 100BaseT either. We are also looking at using either the
>>MPC8260/MPC8265 or the IBM 405GP. I have been browsing through the
>>mailing-list archives and have seen that these processors are both widely
>>used. I would like some feedback from people that have experience in using
>>these processors with Linux and what recommendations they have.
>>
>
> We are using the IBM PPC405GP in some of our new designs and are pretty
> pleased with the hardware itself. The only annoying thing is that the "free
> available" Linux is still pretty buggy and old (at least 3 months or so) :-(
>
> By the way: Dan, how are you doing with the ppc4xx merge into the linuxppc
> queue?
>
> Eventually (hopefully soon) when this problem is solved, I would recommend
> the PPC405GP.
>
> Sorry I can't say anything about the Motorola parts and their Linux support.
>
> Stefan Roese
>
>
>
--
Dave Updegraff / dave@cray.com / 218-525-1154
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-24 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 14:56 New Linux PowerPC development Cindy Peters
2001-07-24 15:26 ` AW: " Stefan Roese
2001-07-24 15:35 ` David Updegraff [this message]
2001-07-24 15:44 ` Grant Erickson
2001-07-24 17:26 ` Dan Malek
2001-07-25 17:14 ` Ralph Blach
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=3B5D95D8.3040702@cray.com \
--to=dave@cray.com \
--cc=cinpet@adaptivemicro.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.