From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Andy Fleming <afleming@freescale.com>,
Kumar Gala <kumar.gala@freescale.com>,
Netdev <netdev@oss.sgi.com>,
Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model)
Date: Thu, 13 Jan 2005 22:58:08 +0100 [thread overview]
Message-ID: <20050113215808.GA15124@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20050113212152.GA16041@gate.ebshome.net>
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
next prev parent reply other threads:[~2005-01-13 21:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 19:01 [RFC] Patch to Abstract Ethernet PHY support (using driver model) Andy Fleming
2004-12-23 21:00 ` Andy Fleming
2005-01-06 7:02 ` Eugene Surovegin
2005-01-06 17:13 ` Eugene Surovegin
2005-01-13 19:50 ` Andy Fleming
2005-01-13 21:21 ` Eugene Surovegin
2005-01-13 21:58 ` Jörn Engel [this message]
2005-01-14 1:00 ` Eugene Surovegin
2005-01-14 14:55 ` Jörn Engel
2005-01-14 15:25 ` Eugene Surovegin
2005-01-14 15:49 ` Jörn Engel
2005-01-14 21:00 ` Andy Fleming
2005-01-17 17:17 ` Jörn Engel
2005-01-13 14:45 ` Kumar Gala
2005-01-13 17:02 ` Stephen Hemminger
2005-01-13 18:22 ` Andy Fleming
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=20050113215808.GA15124@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=afleming@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.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).