From: LEROY Christophe <christophe.leroy@c-s.fr>
To: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>, netdev@vger.kernel.org
Subject: Dual ethernet attachment with single FEC
Date: Tue, 21 Sep 2010 09:30:10 +0200 [thread overview]
Message-ID: <4C985F02.7060403@c-s.fr> (raw)
Hello,
I have a board with 2 PHYs attached to one FEC ethernet controler on
powerpc.
I want to implement some kind of main-standby attachment to LAN by
setting the ISOLATE bit on one on the two PHYs then monitoring the link
status and switch to the other PHY when the link status goes down.
I see this behaviour is implemented in the sis900 driver, but it doesn't
use the standard PHY layer as the Freescale FEC driver does.
What would be the most proper way to implement this functionality ?
* Modify FEC driver to manage that ?
* Implement a virtual PHY driver that would manage that ?
* Other solution ?
Best regards
C. Leroy
next reply other threads:[~2010-09-21 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 7:30 LEROY Christophe [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-03 11:49 Dual ethernet attachment with single FEC LEROY Christophe
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=4C985F02.7060403@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.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).