From: Gerhard Jaeger <g.jaeger@sysgo•com>
To: linuxppc-embedded@ozlabs•org
Subject: Which PHY connection to use on MPC8541...
Date: Tue, 11 Oct 2005 12:13:39 +0200 [thread overview]
Message-ID: <200510111213.39859.g.jaeger@sysgo.com> (raw)
Hi list,
we're currently designing a custon MPC8541 based board having three ethernet connections.
For some reasons, we'd like to use the FCC1 and 2 + TSEC1. From what I see from the
docs, it should be no problem to connect i.e. a quad phy (for FCC1/2) and a gigabit phy
(for TSEC1) to the EC_MDIO of the TSEC as long as they have different addresses.
I don't want to use the GPIO stuff for MDIO.
The question is, what does this mean to the drivers? For the gianfar driver this should
be okay and from what I see, the upcoming fs_enet driver supports also a phy
connected either to the GPIOs (bitbanging) or the TSEC MDIO. Is this right, or am I
missing something essential?
Would it be better to use the GPIO-MDIO for the FCC phy and the TSEC-MDIO
for the TSEC phy?
TIA
Gerhard
next reply other threads:[~2005-10-11 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 10:13 Gerhard Jaeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-11 10:57 Which PHY connection to use on MPC8541 Stefan Nickl
2005-10-11 18:05 ` Andy Fleming
2005-10-12 6:43 ` Gerhard Jaeger
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=200510111213.39859.g.jaeger@sysgo.com \
--to=g.jaeger@sysgo$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/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