| To: | Andy Fleming <afleming@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] MII bus API for PHY devices |
| From: | Jason McMullan <jason.mcmullan@xxxxxxxxxxx> |
| Date: | Thu, 18 Nov 2004 16:00:47 -0500 |
| Cc: | "<netdev@xxxxxxxxxxx>" <netdev@xxxxxxxxxxx>, "<linux-kernel@xxxxxxxxxxxxxxx>" <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <2B68D9FA-399B-11D9-96F6-000393C30512@xxxxxxxxxxxxx> |
| References: | <069B6F33-341C-11D9-9652-000393DBC2E8@xxxxxxxxxxxxx> <9B0D9272-398A-11D9-96F6-000393C30512@xxxxxxxxxxxxx> <1100806489.14467.47.camel@jmcmullan> <2B68D9FA-399B-11D9-96F6-000393C30512@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Thu, 2004-11-18 at 13:50 -0600, Andy Fleming wrote:
> Jason McMullan said:
> >
> > Actually, each PHY should have it's own device directory, like every
> > other device. Eventually, PHYs should have /dev/phy* entries, where
> > user-space can read/write PHY registers.
>
> I think you misunderstood. Are you talking about sysfs? I was talking
> about actual source files. i.e. should there be dm9161.c, m88e1101.c,
> cis8201.c, etc.
Yes, I am talking about sysfs. And yes, I think every PHY should have
it's own .c file. (although most people could get away with
using a non-IRQ 'drivers/net/phy/phy-generic.c'
> Also, do we need user-space to read/write PHY registers. ethtool has
> this capability, I believe, and the interfaces there are settled.
Doh! I forgot.
--
Jason McMullan <jason.mcmullan@xxxxxxxxxxx>
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH][6/12][RFC/v1] Add IPoIB (IP-over-InfiniBand) driver, Roland Dreier |
|---|---|
| Next by Date: | Re: Wrong UIDs reported in /proc/net/tcp, Herbert Xu |
| Previous by Thread: | Re: [PATCH] MII bus API for PHY devices, Andy Fleming |
| Next by Thread: | Re: [PATCH] MII bus API for PHY devices, Benjamin Herrenschmidt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |