netdev
[Top] [All Lists]

RE: [Bridge] Bridging on broken Broadcom hardware.

To: <davem@xxxxxxxxxx>
Subject: RE: [Bridge] Bridging on broken Broadcom hardware.
From: "Paul Schulz" <pschulz@xxxxxxxxxxxxxx>
Date: Thu, 19 Feb 2004 11:39:00 +1030
Cc: <netdev@xxxxxxxxxxx>, "Stephen Hemminger" <shemminger@xxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Thread-index: AcP2f0H5Nq26m1ToSOmbJZ9ukNg3+QABEX6Q
Thread-topic: [Bridge] Bridging on broken Broadcom hardware.
Hi David,

What additional information would you like to have?

Paul Schulz - Software Engineer
Foursticks Pty Ltd - Level 16, 33 King William St, Adelaide 5000
Phone: +61 8 8111 4300  Fax: +61 8 8111 4399  Mobile: +61 401 981 301
Email: pschulz@xxxxxxxxxxxxxx  Web: www.foursticks.com

-----Original Message-----
From: David S. Miller [mailto:davem@xxxxxxxxxx] 
Sent: Thursday, February 19, 2004 10:59 AM
To: Stephen Hemminger
Cc: Paul Schulz; netdev@xxxxxxxxxxx; Simon Jolly
Subject: Re: [Bridge] Bridging on broken Broadcom hardware.

On Wed, 18 Feb 2004 16:16:11 -0800
Stephen Hemminger <shemminger@xxxxxxxx> wrote:

> This looks like a network driver not bridging problem, so forwarding
to
> the netdev list.

Bridging packets, which don't come from the IP stack, won't have
CHECKSUM_HW or similar set in the SKB checksum field.  Therefore
the chip won't be told to checksum the packet on transmit.

The firmware will not mess with the packet contents at all unless
it is told to do so, and in this case (as described) it won't.

> > +   /* 5703 A2 have issues with checksumming too. (sarah) */
> > +   if (tp->pci_chip_rev_id == CHIPREV_ID_5703_A2)
> > +           tp->tg3_flags |= TG3_FLAG_BROKEN_CHECKSUMS;
> > +

I'd like to see a real errata report supporting such a claim.


<Prev in Thread] Current Thread [Next in Thread>