linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Brian Ford <ford@vss.fsi.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: EST SBC8260 and Canary CTX-1170
Date: Mon, 27 Nov 2000 22:14:03 -0500	[thread overview]
Message-ID: <3A2322FB.ECCD2CA2@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0011271651000.493-100000@eos


Brian Ford wrote:


> Does Linux support the CTX-1170 MII?  The arch/ppc/8260_io/fcc_enet.c
> source code talks about the QS6612.  Will I need to extended fcc_enet.c to
> support the CTX-1170?

That driver either "supports" any PHY, or none at all, depending upon
your perspective.  None of the command/status MII interface is in
place to do anything.  None of those functions are called in the
driver.  The QS6612 comment is left over from the 860T FEC driver I
copied to get the framework for the FCC driver.

The Linux 8260 FCC driver works with the supplied EST hardware and the
CTX-1170 I have.  I know it doesn't work on some others, and I don't
know if they use the same Ethernet PHY or the deal of the week.

>From looking at the drivers, it appears they are a little out of
date.  I have a newer one (that I was certain I checked in) that will
interrogate the PHY.  In any case, this driver should work fine on
any half duplex Ethernet, and you should see transmit packets in any
case.

> I know that the hardware can work, because the VxWorks boot rom loads
> Linux successfully via this interface and MII.

Then the driver must not be configuring the I/O lines correctly for
some unknown reason, or you are running full duplex without the FCC
initialized to do that.


	-- Dan

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

  reply	other threads:[~2000-11-28  3:14 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 [this message]
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
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=3A2322FB.ECCD2CA2@mvista.com \
    --to=dan@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).