From: "Stefan Roese" <stefan.roese@esd-electronics.com>
To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Linux-Support for IBM PPC405EP
Date: Thu, 6 Mar 2003 12:34:56 +0100 [thread overview]
Message-ID: <EFEAIMDCOOOHIEPHDNFJIEFFFCAA.stefan.roese@esd-electronics.com> (raw)
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?
Best regards,
Stefan Roese
*******************************************
esd gmbh
Vahrenwalder Str. 207
D-30165 Hannover
Phone: +49-511-37298-0
Fax: +49-511-37298-68
email: stefan.roese@esd-electronics.com
www: http://www.esd-electronics.de
*******************************************
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-03-06 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 11:34 Stefan Roese [this message]
2003-03-06 21:00 ` Linux-Support for IBM PPC405EP Todd Poynor
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=EFEAIMDCOOOHIEPHDNFJIEFFFCAA.stefan.roese@esd-electronics.com \
--to=stefan.roese@esd-electronics.com \
--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).