From: Jason McMullan <jason.mcmullan@timesys.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andy Fleming <afleming@freescale.com>,
netdev@oss.sgi.com,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MII bus API for PHY devices
Date: Fri, 19 Nov 2004 11:41:38 -0500 [thread overview]
Message-ID: <1100882498.14467.58.camel@jmcmullan> (raw)
In-Reply-To: <1100820391.25521.14.camel@gaston>
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@timesys.com>
next prev parent reply other threads:[~2004-11-19 16:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <069B6F33-341C-11D9-9652-000393DBC2E8@freescale.com>
2004-11-18 17:52 ` [PATCH] MII bus API for PHY devices Andy Fleming
2004-11-18 19:34 ` Jason McMullan
2004-11-18 19:50 ` Andy Fleming
2004-11-18 21:00 ` Jason McMullan
2004-11-18 23:26 ` Benjamin Herrenschmidt
2004-11-19 16:41 ` Jason McMullan [this message]
2004-11-19 21:18 ` Andy Fleming
2004-11-19 22:43 ` Benjamin Herrenschmidt
2004-11-20 0:04 ` Andy Fleming
2004-11-19 20:18 Manfred Spraul
2004-11-19 21:01 ` Andy Fleming
-- strict thread matches above, loose matches on Subject: below --
2004-11-11 22:48 Jason McMullan
2004-11-11 23:54 ` Francois Romieu
2004-11-12 0:07 ` Francois Romieu
2004-11-12 6:15 ` Benjamin Herrenschmidt
2004-11-12 16:47 ` Jason McMullan
2004-11-13 1:36 ` Benjamin Herrenschmidt
2004-11-11 19:45 Jason McMullan
2004-11-11 21:31 ` Francois Romieu
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=1100882498.14467.58.camel@jmcmullan \
--to=jason.mcmullan@timesys.com \
--cc=afleming@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).