[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1286457071.2271.4.camel@achroite.uk.solarflarecom.com>
Date: Thu, 07 Oct 2010 14:11:11 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Greg Ungerer <gerg@...pgear.com>
Cc: netdev@...r.kernel.org, gerg@...inux.org
Subject: Re: [RFC] net: allow FEC driver to not have attached PHY
On Thu, 2010-10-07 at 13:50 +1000, 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?
>
> The attached patch adds a config option to do this sort of generically
> for the FEC driver. But I am wondering if there isn't a better way?
[...]
Perhaps there could be a null PHY driver which does no MDIO and always
reports link-up at the expected speed and duplex. We used something
like that in the sfc driver for some PHY-less boards (though we use our
own PHY abstraction, not phylib).
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists