From: sbolderoff@foursticks.com
To: Paul Schulz <pschulz@foursticks.com>, linux-kernel@vger.kernel.org
Subject: Re: Broadcom Gigabit 5703 and Bridging
Date: Wed, 8 Jan 2003 15:11:56 +1030 [thread overview]
Message-ID: <20030108044155.GA1473@fuzzy.foursticks.com.au> (raw)
In-Reply-To: <E18W7jh-0001Co-00@mars>
On Wed, Jan 08, 2003 at 02:52:37PM +1030, Paul Schulz wrote:
> Greetings,
>
> I'm seeing 'TCP Checksum' Errors after packets pass through a host
> bridging TCP packets with:
>
> - Kernel 2.4.20
> - Bridge code
> - tg3 (Broadcom Gigabit 5703)
>
> eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)]
> (PCIX:100MHz:64-bit) 10/100/1000BaseT
> (eth1 is similar)
The BCM95703A30 rev 1002 has issues with the hardware checksumming.
The following patch for the tg3 (linux-2.4.20-ac2/drivers/net/tg3.c)
driver, fixes the problem.
Note: I've tested this on the 2.4.20-ac2, but it should work OK with
2.4.20 too.
diff -u linux-2.4.20/drivers/net/tg3.c linux-2.4.20-ac2/drivers/net/tg3.c
--- linux-2.4.20/drivers/net/tg3.c Fri Nov 29 10:23:14 2002
+++ linux-2.4.20-ac2/drivers/net/tg3.c Wed Jan 8 14:34:44 2003
@@ -6161,6 +6161,10 @@
if (tp->pci_chip_rev_id == CHIPREV_ID_5700_B0)
tp->tg3_flags |= TG3_FLAG_BROKEN_CHECKSUMS;
+ /* 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;
+
/* Regardless of whether checksums work or not, we configure
* the StrongARM chips to not compute the pseudo header checksums
* in either direction. Because of the way Linux checksum support
Cheers,
Sarah Bolderoff
--
Foursticks Pty Ltd, http://www.foursticks.com
33 King William Street, ADELAIDE South Australia 5000
Phone +61 8 841114 309 Fax +61 8 841114 777
This message was brought to you by the numbers 0 and 1.
next parent reply other threads:[~2003-01-08 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18W7jh-0001Co-00@mars>
2003-01-08 4:41 ` sbolderoff [this message]
2003-01-08 6:58 ` Broadcom Gigabit 5703 and Bridging David S. Miller
2003-01-02 1:50 Paul Schulz
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=20030108044155.GA1473@fuzzy.foursticks.com.au \
--to=sbolderoff@foursticks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pschulz@foursticks.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