From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PHY Howto ?
Date: Tue, 25 Jul 2006 00:05:09 -0400 [thread overview]
Message-ID: <44C59875.4000309@dlasys.net> (raw)
In-Reply-To: <20060720220136.29326857@vitb.ru.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
Vitaly Bordug wrote:
> On Thu, 20 Jul 2006 13:52:47 -0400
> "David H. Lynch Jr." <dhlii@dlasys.net> wrote:
>
>
>> If I am writing a network MAC driver, for hardware that has a phy
>> that is already supported, if I provide the appropriate mdio_read() and
>> mdio_write() calls to access the phy registers, and setup my config to
>> include phylib and drivers for my specific phy, what else do I have to
>> take care of with respect to the phy within my driver ?
>>
>> Are there some resources, howto's, examples, ... demonstrating
>> how to use phylib ?
>>
> There is pretty good writeup in Documentation about your concern, find it at
> Documentation/networking/phy.txt . Live example is obviously drivers/net/gianfar*
>
>
>
Thanks that proved useful. I am already using gianfar as a reference
- but it is not a NIC I am familiar with.
And I still have some questions:
What is the distinction/interaction between phylib and MII
support ?
Are they independent ways of doing something similar ? Or do
they work together.
To get MII working I need to provide/populate an mii_if_info
structure and supply register read/write routines.
Since communicating with the PHY is MAC dependent shouldn't I
need to do the same for PHYLIB ?
As I understand it although PHY's are similar, and the same
PHY may be used on different NIC's
Communications to the PHY typically go through the NIC.
So my Network driver has to provide routines to read/write the
registers of the PHY, which phylib and the phy driver then use.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
[-- Attachment #2: Type: text/html, Size: 3352 bytes --]
next prev parent reply other threads:[~2006-07-25 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 17:52 PHY Howto ? David H. Lynch Jr.
2006-07-20 18:01 ` Vitaly Bordug
2006-07-25 4:05 ` David H. Lynch Jr. [this message]
2006-07-25 19:19 ` 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=44C59875.4000309@dlasys.net \
--to=dhlii@dlasys.net \
--cc=dhlii@comcast.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.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).