From: Dan Malek <dan@embeddededge.com>
To: Jos Beck <jos_beck@euronet.nl>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Preferred Phy for MPC8260
Date: Fri, 26 Mar 2004 11:10:17 -0500 [thread overview]
Message-ID: <406455E9.90809@embeddededge.com> (raw)
In-Reply-To: 406448EC.5030009@euronet.nl
Jos Beck wrote:
> Would anyone of you know a preferred 10/100baseT phy for the MPC8260?
> Or specific brands/types to avoid?
> Or does it really not matter what we use?
It depends completely on your system requirements. There are many different
PHYs supported in the software right now, and it is relatively easy to
add new ones. Some of the features you may want to consider are whether
you want single or multiple PHYs in one package, and take a look at the
detail of how they may interrupt the processor on link changes and if
that is suitable for your product. For software compatibility, it's
more important how the PHY is connected to the pins of the processor
(due to its flexibility) than which one is used.
In typical fashion, when the LXT parts changed hands there were some
subtle differences from the original that has made them a PITA, so they
aren't high on my list, but something still makes them attractive to use :-)
My preference is AMD networking products.
Good Luck. :-)
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-26 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 15:14 Preferred Phy for MPC8260 Jos Beck
2004-03-26 16:10 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 15:21 Steven Blakeslee
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=406455E9.90809@embeddededge.com \
--to=dan@embeddededge.com \
--cc=jos_beck@euronet.nl \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).