From: "Gerhard TAEUBL" <Gerhard.TAEUBL@frequentis.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: 2 Ethernet ports on a MPC860T
Date: Tue, 11 Jun 2002 09:34:43 +0200 [thread overview]
Message-ID: <sd05c43a.096@mail.frequentis.com> (raw)
Hi all!
We have to redesign our customer board next year, and there is a requirement to use two ethernet ports. At the moment we use of course the FEC with 10/100 MBit. So we want to add a SCC (SCC3 fits for us ...) for a second ethernet. Is that configuration supported by linux, or easy to adapt? (to switch from another SCC to SCC3 or similar).
What kind of external devices are necessary? And how do you store the MAC Address? (We do it at the moment via a one wire chip, they garant for the right MAC Address).
Thanks in advance
Gerhard
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-11 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 7:34 Gerhard TAEUBL [this message]
2002-06-11 8:30 ` 2 Ethernet ports on a MPC860T Steffen Rumler
-- strict thread matches above, loose matches on Subject: below --
2002-06-11 9:10 Goddeeris Frederic
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=sd05c43a.096@mail.frequentis.com \
--to=gerhard.taeubl@frequentis.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).