| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: PHY Abstraction Layer II |
| From: | Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 09 Mar 2005 14:50:14 +1100 |
| Cc: | afleming@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linuxppc-embedded@xxxxxxxxxx |
| In-reply-to: | <20050308194229.41c23707.davem@xxxxxxxxxxxxx> |
| References: | <1107b64b01fb8e9a6c84359bb56881a6@xxxxxxxxxxxxx> <1110334456.32556.21.camel@gaston> <20050308194229.41c23707.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 2005-03-08 at 19:42 -0800, David S. Miller wrote: > On Wed, 09 Mar 2005 13:14:16 +1100 > Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> wrote: > > > I'll have a closer look when I find some time, see if it makes sense to > > adapt sungem or not. > > Especially because of the Broadcom PHYs I bet it doesn't. > > Too many chips have to reset the MAC, or do other fancy stuff > when programming the PHY to make this genphy thing very useful. Oh, I think genphy is just a generic driver, but his layer has hooks for other PHY drivers (wasn't it based on sungem_phy in the first place ?) I discussed several steps of the design with Andy, the idea was to have something a bit like sungem_phy.c with addditional common library for doing the link polling & fallback stuff etc... that could be easily shared by drivers. Ben. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RFC: PHY Abstraction Layer II, David S. Miller |
|---|---|
| Next by Date: | Re: Do you know the TCP stack? (127.x.x.x routing), Zdenek Radouch |
| Previous by Thread: | Re: RFC: PHY Abstraction Layer II, David S. Miller |
| Next by Thread: | Re: RFC: PHY Abstraction Layer II, Andy Fleming |
| Indexes: | [Date] [Thread] [Top] [All Lists] |