From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason McMullan Subject: Re: [PATCH] MII bus API for PHY devices Date: Fri, 19 Nov 2004 11:41:38 -0500 Message-ID: <1100882498.14467.58.camel@jmcmullan> References: <069B6F33-341C-11D9-9652-000393DBC2E8@freescale.com> <9B0D9272-398A-11D9-96F6-000393C30512@freescale.com> <1100820391.25521.14.camel@gaston> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Andy Fleming , netdev@oss.sgi.com, Linux Kernel list Return-path: To: Benjamin Herrenschmidt In-Reply-To: <1100820391.25521.14.camel@gaston> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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