linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Conn Clark <clark@esteem.com>
To: acurtis@onz.com
Cc: May Ling List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Poor 8260 FCC Ethernet performance
Date: Fri, 31 May 2002 08:51:50 -0700	[thread overview]
Message-ID: <3CF79C16.4B547602@esteem.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFCEOADHAA.acurtis@onz.com


Allen Curtis wrote:
>
> > The 8260 Ethernet controller needs to know about the duplex mode in which
> > the PHY operates. The driver sets it to half duplex by default, and needs
> > the feed back of the PHY to set it to full duplex.
> >
> > As you may know, the hub always operates in half duplex, while the switch
> > usually operates in full duplex, if it is directly connected to your unit,
> > and your PHY accepts to negociate to full duplex.
> >
>
> Yes, the source code has been modified to force full-duplex.
> (fcc_restart(dev,1) if I remember correctly :) In fact, before this change
> was made Ethernet communications did not work at all. (At least it would not
> get past bootp) I searched for something that looked like it was speed
> related but found nothing. (Other than the MII reporting)
>
> Other ideas?

Could it be an analog problem? Have you looked at the signals comming in on
a scope?


>
> BTW: We are using a BCM switch for our PHY. The interface to the processor
> is always full-duplex, 100BT regardless of the external connections. Hence
> the no MII PHY option.

Let me get this straight, You have no PHY, no magnet, no connector? If this
is the case are you sure your voltages on the I/O compatible?

I have thought about building a Beowolf cluster in this manner out of 8260s
just to impress my geek friends and colleages. Of course I don't have the
time or money to do it, but its fun to think about.

Good Luck

	Conn

--

*****************************************************************
  If you live at home long enough, your parents will move out.
*****************************************************************

Conn Clark
Engineering Stooge				clark@esteem.com
Electronic Systems Technology Inc.		www.esteem.com

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

  reply	other threads:[~2002-05-31 15:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31  3:25 Poor 8260 FCC Ethernet performance Jean-Denis Boyer
2002-05-31  3:42 ` Allen Curtis
2002-05-31 15:51   ` Conn Clark [this message]
2002-06-01  3:09     ` Allen Curtis
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10 19:26 Rune Torgersen
2004-06-09 22:33 Rune Torgersen
2004-06-10 17:56 ` Dan Malek
2004-06-09 22:19 Rune Torgersen
2004-06-09 22:27 ` Gary Thomas
2004-06-07 17:33 VanBaren, Gerald (AGRE)
2004-06-08  6:29 ` Wojciech Kromer
2004-06-07 12:32 Dayton, Dean
2004-06-07 12:14 Dayton, Dean
2004-06-07 12:16 ` Pantelis Antoniou
2004-06-06 18:00 Adisorn Ermongkonchai
2004-06-07 12:51 ` Mark Chambers
2004-06-07 17:21   ` Adisorn Ermongkonchai
2002-05-31  3:07 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=3CF79C16.4B547602@esteem.com \
    --to=clark@esteem.com \
    --cc=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).