linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Allen Curtis" <acurtis@onz.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: ibm_ocp_enet.c - PHY implementation requirements?
Date: Tue, 7 May 2002 07:15:19 -0700	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFEEJNDGAA.acurtis@onz.com> (raw)


We have an 405GP design, very similar to the Walnut LSP. One of the major
differences is that we have a BroadCom 9-port switch instead of a dedicated
PHY for Ethernet. Supporting the switch is much easier than a dedicated PHY
because you can always assume:  100Mb, Full-Duplex and you do not have to
handle disconnect and mode change interrupts. The problem is that the OCP
Ethernet implementation has become much more complex and it is not obvious
what must be supported when adding a new interface and what could be a stub.
(and its expected result)

Another issue is that the switch supports both the MII and SPI interfaces.
These are mutually exclusive, determined by first access to the device. Our
design requires the use of the SPI interface. All currently supported PHY
are MII, which is expected. Do you forsee any problems using SPI within
ibm_ocp_phy.c?

TIA


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-05-07 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 14:15 Allen Curtis [this message]
2002-05-07 15:49 ` ibm_ocp_enet.c - PHY implementation requirements? Armin
2002-05-08  5:03   ` Allen Curtis
  -- strict thread matches above, loose matches on Subject: below --
2002-05-07 14:16 Allen Curtis

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=NCBBIINEHIPFGJPLBEIFEEJNDGAA.acurtis@onz.com \
    --to=acurtis@onz.com \
    --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).