linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: diekema@bucks.si.com (diekema_jon)
To: ford@vss.fsi.com (Brian Ford)
Cc: linuxppc-embedded@lists.linuxppc.org, dan_malek@mvista.com
Subject: Re: EST SBC8260 and Canary CTX-1170
Date: Thu, 30 Nov 2000 09:47:32 -0500 (EST)	[thread overview]
Message-ID: <m141Uzk-001SzWC@bucks> (raw)
In-Reply-To: <Pine.GSO.4.21.0011291213330.493-100000@eos> from "Brian Ford" at Nov 29, 2000 12:18:44 PM


> I cracked open my CTX-1170 gizmo and it has a Lucent LU3X51FT-JE80 PHY in
> it.  I manually set the phy_duplex to 1 and the phy_speed to 100, still
> no dice.

We have several of the CTX-1170 MII, and we have at least two
different PHY's in them.  One of the types is the Lucent
LU3X51FT-JE80.  I was unable to find a data sheet for the LU3X51FT
from http://www.lucent.com/micro, however I was able to find one on
the LU3X54FT.  The LU3X54-FT is a quad version of the LU3X51-FT.

The cep->phy_type variable in arch/ppc/8260_io/fec_enet.c gets derived
from the PHY identifer registers 1 / 2.  When I run with FEC2 active,
I get a type of 0x00437412.  I would expect this to look something
like 0x0180????.

#
# MPC8260 Communication Options
#
# CONFIG_SCC_ENET is not set
CONFIG_FEC_ENET=y
# CONFIG_FCC1_ENET is not set
CONFIG_FCC2_ENET=y
# CONFIG_FCC3_ENET is not set

MPC8260 CPU/CPM/BUS: 200/133/33 Mhz

fec: Phy @ 0x0, type 0x00437412


When Dan Malek runs with the National Semi PHY DP83840A, how fast
is the MPC8260 running?  I think that Dan is running at 166Mhz,
if so we might have a timing problem on I2C bus.


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

  reply	other threads:[~2000-11-30 14:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-27 20:09 MP8240 UART Dan Jankins
2000-11-27 20:24 ` Dan Malek
2000-11-27 20:36 ` Mark A. Greer
2000-11-27 23:09   ` EST SBC8260 and Canary CTX-1170 Brian Ford
2000-11-28  3:14     ` Dan Malek
2000-11-28 19:19       ` Brian Ford
2000-11-28 22:04         ` Dan Malek
2000-11-28 22:33           ` Brian Ford
2000-11-28 23:28             ` Dan Malek
2000-11-29 18:18           ` Brian Ford
2000-11-30 14:47             ` diekema_jon [this message]
2000-11-30 17:51               ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2000-11-30 16:03 Jerry Van Baren
2000-11-30 18:41 Gessner, Matt
2001-03-08 15:39 Oliver Brown
2001-03-09  0:36 ` Dan Malek
2001-03-09  3:07   ` David Schleef
2001-03-09  4:23     ` Dan Malek
2001-03-09  4:55       ` David Schleef
2001-03-09  4:54         ` Dan Malek
2001-03-09  5:07           ` David Schleef
2001-03-11 13:28 Oliver Brown
2001-03-11 14:19 ` Wolfgang Denk

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=m141Uzk-001SzWC@bucks \
    --to=diekema@bucks.si.com \
    --cc=dan_malek@mvista.com \
    --cc=ford@vss.fsi.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).