From: Ben Warren <bwarren@qstreams.com>
To: DI BACCO ANTONIO - technolabs <Antonio.DiBacco@technolabs.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Making fs_enet phy unaware
Date: Mon, 11 Jun 2007 13:52:16 -0400 [thread overview]
Message-ID: <1181584336.6079.2.camel@saruman.qstreams.net> (raw)
In-Reply-To: <F1F6EC0C8B75034F9E3A79FC85122E8E8EADF8@aquib01a>
Hi Antonio,
On Mon, 2007-06-11 at 12:30 +0200, DI BACCO ANTONIO - technolabs wrote:
> Hi all,
>
> how can I avoid that fs_enet driver uses its associated phy? My problem
> is that my FEC is attached to a switch and three other ports of the
> switch are connected to three physical connectors. I don't want that the
> driver bothers about the PHYs.
If you search the archives you'll find patches by Vitaly Bordug and Andy
Fleming for so-called 'Fixed PHY'. I've been using this for quite a
while and it works quite well.
regards,
Ben
prev parent reply other threads:[~2007-06-11 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 10:30 Making fs_enet phy unaware DI BACCO ANTONIO - technolabs
2007-06-11 17:52 ` Ben Warren [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=1181584336.6079.2.camel@saruman.qstreams.net \
--to=bwarren@qstreams.com \
--cc=Antonio.DiBacco@technolabs.it \
--cc=linuxppc-embedded@ozlabs.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).