linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Stephen Edie <sedie@terraplex.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: PCNET32 driver
Date: Wed, 15 Dec 1999 17:44:42 +0100	[thread overview]
Message-ID: <19991215174442.007768@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9912150919400.26215-100000@newhope.terraplex.com>


On Wed, Dec 15, 1999, Stephen Edie <sedie@terraplex.com> wrote:

>When running in 100mbit mode, the PCNET32 driver reports the following
>error message:
>
>eth0:TX FIFO error! Status 02e3
>
>With this messages present, we have seen a number of problems from
>TCP connections being closed after a few bytes of transfer to very poor
>performance (1-mbit throughput) to not working at all.  Is there a quick
>way to fix this problem perhaps?  We would like to get some of our
>in-house CHRP machines running at the full 100mbit and we have some
>customers who require 100mbit throughput as well.

Which pcnet32 chip are you using ? There are some issues with
auto-negociation on some integreated-PHY models, and you may have to
adjust a few of the chip parameters. I used the pcnet32 driver with an
AMD 973 on an ARM platform and it worked just fine (after I fixed the
cache coherency issues but those won't happen on PPC).


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

  reply	other threads:[~1999-12-15 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-15 16:23 PCNET32 driver Stephen Edie
1999-12-15 16:44 ` Benjamin Herrenschmidt [this message]
1999-12-15 16:53   ` Stephen Edie

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=19991215174442.007768@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sedie@terraplex.com \
    /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).