From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC + NatSemi dp83640 phy?
Date: Wed, 15 Apr 2009 21:24:40 -0400 [thread overview]
Message-ID: <49E688D8.60904@gmail.com> (raw)
In-Reply-To: <1239836447.7926.452.camel@localhost.localdomain>
Hi Nathan,
Nathan French wrote:
> Hi all,
>
> I've been tasked with bringing up a new board next week for my company
> that is essentially a Kilauea with a National Semiconductor DP83640
> ethernet phy. We have U-Boot working on our previous board rev which
> used the Marvell 88E1111 ethernet phy which U-Boot supports.
>
> I'm new to ethernet devices. I see that both the 88E1111 and the
> DP83xxx devices use MII. Does this mean the DP83640 may just work as
> is?
Maybe. My impression of and experience with the MII standard is that it
has lots of room for different "standard" implementations as well as
non-standard behavior. Maybe things are better now. Or not.
Theoretically, you should be able to drop in any PHY, use just the
standardized registers and behavior, and have it work. In practice,
maybe, maybe not. My (somewhat dated) experience is that I ended up
twiddling with "implementation extension" registers to get the behavior
I wanted.
If you look at the u-boot and linux PHY drivers, you will see a lot of
manufacturer's names. Not a good sign. On the other hand, there is
also a concept of a "generic" PHY. If "generic" works, that is great.
BTW, it is helpful to enable the MII command so that you can poke around
in your PHY's registers.
> Thanks,
>
> Nathan French
Have fun,
gvb
next prev parent reply other threads:[~2009-04-16 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 23:00 [U-Boot] PPC + NatSemi dp83640 phy? Nathan French
2009-04-16 1:24 ` Jerry Van Baren [this message]
2009-05-05 18:32 ` Nathan French
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=49E688D8.60904@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.denx.de \
/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