It appears that I'm hitting an exactly the same problem with my MPC8548
rev2.0 (errata number eTSEC 49).
Considering that it's close to 3 month now since this most unfortunate
bug was reported, was there any resolution/patch that can fix it for good?
_
From: "Matthew L. Creech"
Date: Thu, 18 Nov 2010 14:31:46 -0500
> On Thu, Nov 18, 2010 at 12:06 PM, David Miller wrote:
>>
>> Can someone please follow up Matthew to get this bug resolved? It has
>> been sitting around for a long time.
>>
>> I suspect the gianfar driver, for these chip revision
On Thu, Nov 18, 2010 at 12:06 PM, David Miller wrote:
>
> Can someone please follow up Matthew to get this bug resolved? It has
> been sitting around for a long time.
>
> I suspect the gianfar driver, for these chip revisions, will need to
> do a software checksum when the offset matches the crit
From: "Matthew L. Creech"
Date: Tue, 2 Nov 2010 18:29:08 -0400
> An upgrade from 2.6.34 to 2.6.35 caused networking to stop working on
> my MPC8313-based board. It turned out that TCP checksums were
> invalid, so I dug through the .35 changelog to try and isolate the
> reason. The change "tcp:
Hi,
An upgrade from 2.6.34 to 2.6.35 caused networking to stop working on
my MPC8313-based board. It turned out that TCP checksums were
invalid, so I dug through the .35 changelog to try and isolate the
reason. The change "tcp: Set CHECKSUM_UNNECESSARY in
tcp_init_nondata_skb" seems to be the sp
