From: Simon Farnsworth <simon@farnz.org.uk>
To: netdev@vger.kernel.org
Subject: Re: [RFC] net: allow FEC driver to not have attached PHY
Date: Thu, 07 Oct 2010 14:28:08 +0100 [thread overview]
Message-ID: <i8kht9$obm$1@dough.gmane.org> (raw)
In-Reply-To: 201010070350.o973oGFE026910@goober.internal.moreton.com.au
Greg Ungerer wrote:
>
> Hi All,
>
> I have a board with a ColdFire SoC on it with the built-in FEC
> ethernet module. On this hardware the FEC eth output is directly
> attached to a RTL8305 4-port 10/100 switch. There is no conventional
> PHY, the FEC output is direct into the uplink port of the switch
> chip.
>
> This setup doesn't work after the FEC code was switch to using
> phylib. The driver used to have code to bypass phy detection/setup
> for this particular board. The phylib probe finds nothing, and of
> course sets a no-link condition.
>
> So, what is the cleanest way to support this?
>
Is there anything that stops you using the fixed MDIO support in phylib
(CONFIG_FIXED_PHY)? It seems to me to be intended for this sort of
situation.
--
Simon
prev parent reply other threads:[~2010-10-07 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 3:50 [RFC] net: allow FEC driver to not have attached PHY Greg Ungerer
2010-10-07 13:11 ` Ben Hutchings
2010-10-08 5:58 ` Greg Ungerer
2010-10-07 13:24 ` Florian Fainelli
2010-10-08 5:57 ` Greg Ungerer
2010-10-07 13:28 ` Simon Farnsworth [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='i8kht9$obm$1@dough.gmane.org' \
--to=simon@farnz.org.uk \
--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).