[Top] [All Lists]

Re: [PATCH] MII bus API for PHY devices

To: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] MII bus API for PHY devices
From: Jason McMullan <jason.mcmullan@xxxxxxxxxxx>
Date: Fri, 19 Nov 2004 11:41:38 -0500
Cc: Andy Fleming <afleming@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, Linux Kernel list <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <1100820391.25521.14.camel@gaston>
References: <069B6F33-341C-11D9-9652-000393DBC2E8@xxxxxxxxxxxxx> <9B0D9272-398A-11D9-96F6-000393C30512@xxxxxxxxxxxxx> <1100820391.25521.14.camel@gaston>
Sender: netdev-bounce@xxxxxxxxxxx
On Fri, 2004-11-19 at 10:26 +1100, Benjamin Herrenschmidt wrote:
> The ethernet driver can instanciate the PHYs at it's childs, though the
> case of several MACs sharing PHYs will be difficult to represent...

I think *requiring* a binding to ethernet devices is a bad idea. 

For example, on many MPC8260 embedded systems, the MII bus is controlled
by GPIO pins, not an ethernet MDIO system.

Some applications may use the MII bus to control non-PHY devices, such
as Broadcom ethernet switches. I'm working for a general MII bus that
ethernet PHYs and other devices can all use.

Jason McMullan <jason.mcmullan@xxxxxxxxxxx>

<Prev in Thread] Current Thread [Next in Thread>