From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?J=F6rn?= Engel Subject: Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model) Date: Thu, 13 Jan 2005 22:58:08 +0100 Message-ID: <20050113215808.GA15124@wohnheim.fh-wedel.de> References: <20050106070245.GA6539@gate.ebshome.net> <61A37C72-659C-11D9-8D70-000393C30512@freescale.com> <20050113212152.GA16041@gate.ebshome.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: To: Andy Fleming , Kumar Gala , Netdev , Embedded PPC Linux list Content-Disposition: inline In-Reply-To: <20050113212152.GA16041@gate.ebshome.net> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org On Thu, 13 January 2005 13:21:52 -0800, Eugene Surovegin wrote: >=20 > 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=F6rn --=20 Optimizations always bust things, because all optimizations are, in the long haul, a form of cheating, and cheaters eventually get caught. -- Larry Wall=20