| To: | Andy Fleming <afleming@xxxxxxxxxxxxx>, Kumar Gala <kumar.gala@xxxxxxxxxxxxx>, Netdev <netdev@xxxxxxxxxxx>, Embedded PPC Linux list <linuxppc-embedded@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model) |
| From: | Jörn Engel <joern@xxxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 13 Jan 2005 22:58:08 +0100 |
| In-reply-to: | <20050113212152.GA16041@gate.ebshome.net> |
| References: | <FC6D9B81-5514-11D9-8D51-000393C30512@freescale.com> <A3A281FF-5525-11D9-80ED-000393C30512@freescale.com> <20050106070245.GA6539@gate.ebshome.net> <61A37C72-659C-11D9-8D70-000393C30512@freescale.com> <20050113212152.GA16041@gate.ebshome.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Thu, 13 January 2005 13:21:52 -0800, Eugene Surovegin wrote: > > It's a standard, period. If there is a PHY which isn't compliant I > guess it will not work anyway, but in this case, yes, we can use > PHY-specific link detection, but only in this case. I suspect you'll > have a hard time finding such PHY :) http://www.broadcom.com/collateral/pb/5325-PB05-R.pdf With some thinking and very little code, you can use this neat chip almost like a normal phy. Jörn -- Optimizations always bust things, because all optimizations are, in the long haul, a form of cheating, and cheaters eventually get caught. -- Larry Wall |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model), Eugene Surovegin |
|---|---|
| Next by Date: | Re: V2.4 policy router operates faster/better than V2.6, Jeremy M. Guthrie |
| Previous by Thread: | Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model), Eugene Surovegin |
| Next by Thread: | Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model), Eugene Surovegin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |