9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Intel 8254[17] and switches
Date: Sat, 16 Apr 2005 08:51:04 -0400	[thread overview]
Message-ID: <f56acd4ec156b8ecde37f1c82630fcca@coraid.com> (raw)

Final update on the etherigbe.c effort.

The 82541 and 82547 have phy's that don't like inexpensive switches!
After a couple of weeks banging my head on the wall, I discover that
the PXE firmware on the things can't even drive 1GbE.  I couldn't find
any mention of this fact in anything from Intel, unless one of the
erata's on a sheet I got states this fact in an obscure way.

At first I noticed that at 100Mb I had to insert a delay after each
frame.  Otherwise it the frames that followed would disappear.  Counts
showed that they were transmitted, but snoopy didn't see anything.  I
shared my work in progress with several people, and they commented on
the resends.  This was because the stack would send 4 frames, drop
three, get acked for the first, wait and send the first 3 over and
another one.  This would finally work, but was very slow.  IL was less
patient.  I added a delay of 150µs and they all get out.

At 1 Gb things got really screwy.  The phy would state that it had to
use MDI-X, that is, it had to switch the cable to get a link.  This
obviously wasn't needed.  The cables were good, and they were plugged
into a switch.  Phy showed that it was linked at Gb, light on switch
concurred.  The MAC registered also agreed, but no data.  Nice
activity lights but nothing that could be snoopyed or forward by the
switch.  Buggers!

So, I would obviously discourage anyone from using these parts.

Does anyone have a driver for the Broadcom BCM5721?

  Brantley



             reply	other threads:[~2005-04-16 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 12:51 Brantley Coile [this message]
2005-04-16 16:10 ` Ronald G. Minnich

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=f56acd4ec156b8ecde37f1c82630fcca@coraid.com \
    --to=brantley@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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).