| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [Bridge] Bridging on broken Broadcom hardware. |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Wed, 18 Feb 2004 16:29:04 -0800 |
| Cc: | pschulz@xxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, sjolly@xxxxxxxxxxxxxx |
| In-reply-to: | <20040218161611.6365c3bf@dell_ss3.pdx.osdl.net> |
| References: | <1077146945.3779.17.camel@localhost> <20040218161611.6365c3bf@dell_ss3.pdx.osdl.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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> |
|---|---|---|
| ||
| Previous by Date: | Re: [BK PATCH] 2.4 SCTP fixes, David S. Miller |
|---|---|
| Next by Date: | Re: [janitor] tr/3c359: handle kmalloc failures during init, Jeff Garzik |
| Previous by Thread: | Re: [Bridge] Bridging on broken Broadcom hardware., Stephen Hemminger |
| Next by Thread: | RE: [Bridge] Bridging on broken Broadcom hardware., Paul Schulz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |