From: Todd Poynor <tpoynor@mvista•com>
To: Stefan Roese <stefan.roese@esd-electronics•com>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Linux-Support for IBM PPC405EP
Date: Thu, 06 Mar 2003 13:00:13 -0800 [thread overview]
Message-ID: <3E67B6DD.4070402@mvista.com> (raw)
In-Reply-To: <EFEAIMDCOOOHIEPHDNFJIEFFFCAA.stefan.roese@esd-electronics.com>
Stefan Roese wrote:
> Hi,
>
> Is anybody successfully runnning linux (linuxppc_2_4_devel) on the new
> PPC405EP? I know it's pretty much the PPC405GP(r), but it has 2 Ethernet
> Controllers.
>
> I would assume that there will be no problems (at least when not using the
> second ethernet controller). Any comments/experiences?
I didn't experience any problems when I briefly tried things out a few
weeks ago, but didn't test a lot of devices. Others at MontaVista have
successfully tested more stuff, including both ethernets, on a similar
code base.
--
Todd
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-03-06 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 11:34 Linux-Support for IBM PPC405EP Stefan Roese
2003-03-06 21:00 ` Todd Poynor [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=3E67B6DD.4070402@mvista.com \
--to=tpoynor@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=stefan.roese@esd-electronics$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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