netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [TG3] Always load TSO firmware
Date: Mon, 17 Nov 2003 12:38:36 -0800	[thread overview]
Message-ID: <20031117123836.2f8e70af.davem@redhat.com> (raw)
In-Reply-To: <20031117093225.GA12420@gondor.apana.org.au>

On Mon, 17 Nov 2003 20:32:25 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> In 2.5 the TSO firmware is always loaded on capable cards.  This
> does not happen in 2.4.  I've received a report from a Broadcom
> 5705M user that unless the firmware is loaded his card does not
> work.
> 
> This patch makes it load the TSO firmware even if the kernel
> does not support it.
> 
> The only catch is that the Broadcom driver doesn't always load
> the firmware either and yet it still works under 2.4 for that user.
> 
> Despite that this should still be safe as 2.5 always loads the
> firmware regardless of whether TSO is going to be used or not.
> It also removes another variable between 2.4/2.5 when chasing
> down tg3 bugs.

I'd like to figure out the problem instead of applying this patch.

In fact, the behavior is the biggest clue as to what the problem
might be.  Espcially since in 2.4.x the TSO firmware is not executed
at all by the chip, and therefore should have no bearing on it's
operation.

Whether we load the TSO firmware or not on 5705 determines how big
an onboard buffer area we give to the chip for packet data.  It may
be the case that we are miscalculating these values or not programming
them into the chip correctly.

This is where you should look for the problem.

FWIW all of my 5782 and 5705 PCI boards work perfectly fine with the
current 2.4.x driver.

  reply	other threads:[~2003-11-17 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  9:32 [TG3] Always load TSO firmware Herbert Xu
2003-11-17 20:38 ` David S. Miller [this message]
2003-11-20  9:56   ` Herbert Xu
     [not found]     ` <20031120092530.4dfe9016.davem@redhat.com>
2003-11-20 17:41       ` Jeff Garzik
2003-11-20 17:59     ` Jeff Garzik

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=20031117123836.2f8e70af.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.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).