public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  eCos docs conflating Ethernt MII and MI interface?
Date: Wed, 16 Jul 2008 16:10:00 -0000	[thread overview]
Message-ID: <g5l6g3$ig4$1@ger.gmane.org> (raw)

I've been looking at the doc page below:

 http://www.ecos.sourceware.org/docs-latest/ref/io-eth-phy-generic1.html

The page appears to be conflating the MII and MI interfaces to
a PHY.  Based on the data structure and some parts of the
description I think the page it talking about the two-wire,
half-duplex, bit-serial serial management interface (aka MI or
SMI).  

But, in other parts, it talks about the MII interface between
the MAC and the PHY. MII (media independant interface) is a
16-wire, nibble-wide, full-duplex interface that's used to
transfer Ethernet frames and control/status info between the
MAC and the PHY.

MII and MI are completely separate interfaces, and it's not
clear which interface this page is describing. At one point it
talks about using "set_data(), get_data(), set_clock(),
set_dir() are used to control the MII signals and run the
protocol." That must be referring to MI instead of MII.

IIRC, the same PHY registers are generally available via both
MII and MI.

It _could_ be that the bit_level_ops members are being used to
access the MI interface on the PHY directly via processor I/O
port pins and the reg_level_ops are being used to access the
PHY registers via the MAC (which in turn uses MII), but that's
not clear from the page.

-- 
Grant Edwards                   grante             Yow! Loni Anderson's hair
                                  at               should be LEGALIZED!!
                               visi.com            


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2008-07-16 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 16:10 Grant Edwards [this message]
2008-07-16 17:44 ` Andrew Lunn
2008-07-16 18:41   ` [ECOS] " Grant Edwards

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='g5l6g3$ig4$1@ger.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).