[Top] [All Lists]

Re: RFC: Enabling ethernet drivers to return FCS in the skb?

To: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
Subject: Re: RFC: Enabling ethernet drivers to return FCS in the skb?
From: "Maciej W. Rozycki" <macro@xxxxxxxxxxxxx>
Date: Wed, 19 Nov 2003 14:20:24 +0100 (CET)
Cc: "'netdev@xxxxxxxxxxx'" <netdev@xxxxxxxxxxx>
In-reply-to: <20031119123556.A7622@xxxxxxxxxx>
Organization: Technical University of Gdansk
References: <3FB94311.10004@xxxxxxxxxxxxxxx> <20031119123556.A7622@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Wed, 19 Nov 2003, Rask Ingemann Lambertsen wrote:

> > Is there any interest in adding an Ethtool command to tell the driver to
> > push the extra 4 bytes of CSUM into the skb?
> > 
> > When enabling this feature, I'd also like to allow drivers to receive
> > frames with bad FCS as well.
> [cut]
> > At least some hardware appears
> > to support receiving bad FCS frames (e1000, evidently), but I am not sure
> > how wide-spread this feature is...
> The Intel i82586 and i82596 and can be told to receive frames with a bad FCS.
> They can also be told to send a precomputed FCS rather than computing it on
> the fly. The i82596 and tulip can also transfer the FCS to memory when
> receiving frames. I guess all of this is also supported on the i82557/8/9.

 FYI, all DEC FDDI controllers we currently support (or support is being
worked on) do support receiving bad frames -- all frames are always passed
to the rx path and it's up to a driver to decide if a bad frame should be
completely discarded or other actions should be taken.  By specification
the boards also support sending frames with a manually calculated
checksum, which may possibly be intentionally wrong, but I haven't
actually tested it.

 If such functionality is added for Ethernet boards, I'm willing to 
support it for these DEC FDDI boards as well.

+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+        e-mail: macro@xxxxxxxxxxxxx, PGP key available        +

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