Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RFC\:\s+Enabling\s+ethernet\s+drivers\s+to\s+return\s+FCS\s+in\s+the\s+skb\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RFC\:\s+Enabling\s+ethernet\s+drivers\s+to\s+return\s+FCS\s+in\s+the\s+skb\?\s*$/: 14 ]

Total 14 documents matching your query.

1. RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: avem@xxxxxxxxxx>; Date: Mon, 17 Nov 2003 13:52:17 -0800; Ethereal now has the ability to decode (and check) the FCS for ethernet frames (assuming it understands the protocol so it can determine that the last 4 bytes are FCS). Is there any interest in addin; /archives/netdev/2003-11/msg00328.html (8,838 bytes)
2. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: @xxxxxxxxxxxxxx>; Date: Wed, 19 Nov 2003 12:35:57 +0100; [cut] 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; /archives/netdev/2003-11/msg00383.html (8,962 bytes)
3. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: ask@xxxxxxxxxx>; Date: Wed, 19 Nov 2003 14:20:24 +0100 (CET); 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; /archives/netdev/2003-11/msg00386.html (10,107 bytes)
4. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: @xxxxxxxxxx>; Date: Wed, 19 Nov 2003 07:33:53 -0800; Rask Ingemann Lambertsen wrote: On Mon, Nov 17, 2003 at 01:52:17PM -0800, Ben Greear wrote: Is there any interest in adding an Ethtool command to tell the driver to push the extra 4 bytes of CSUM int; /archives/netdev/2003-11/msg00391.html (10,834 bytes)
5. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: on <Robert.Olsson@xxxxxxxxxxx>; Date: Thu, 20 Nov 2003 17:34:08 +0100; The i825xx Ethernet chips are configured by putting a configure command on the TX list. One of the bits of the configure command tells the chip to discard or keep packets with errors. Assuming you ca; /archives/netdev/2003-11/msg00432.html (14,685 bytes)
6. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: @xxxxxxxxxxxxxxxxxxx>; Date: Sun, 23 Nov 2003 01:02:41 -0800; Rask Ingemann Lambertsen wrote: On Wed, Nov 19, 2003 at 07:33:53AM -0800, Ben Greear wrote: Rask Ingemann Lambertsen wrote: The Intel i82586 and i82596 and can be told to receive frames with a bad FC; /archives/netdev/2003-11/msg00460.html (11,736 bytes)
7. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: S. Miller" <davem@xxxxxxxxxx>; Date: Mon, 24 Nov 2003 01:05:05 +0100; [Intel i82557/8/9 Ethernet chips] Saving bad frames to memory is controlled by CB_CFIG_SAVE_BAD_FRAMES in byte 6. Saving the FCS to memory is controlled by CB_CFIG_CRC_IN_MEM in byte 18. See drivers/; /archives/netdev/2003-11/msg00473.html (9,648 bytes)
8. RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Mon, 17 Nov 2003 13:52:17 -0800; Ethereal now has the ability to decode (and check) the FCS for ethernet frames (assuming it understands the protocol so it can determine that the last 4 bytes are FCS). Is there any interest in addin; /archives/netdev/2003-11/msg00941.html (8,672 bytes)
9. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>; Date: Wed, 19 Nov 2003 12:35:57 +0100; [cut] 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; /archives/netdev/2003-11/msg00996.html (9,049 bytes)
10. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: "Maciej W. Rozycki" <macro@xxxxxxxxxxxxx>; Date: Wed, 19 Nov 2003 14:20:24 +0100 (CET); 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; /archives/netdev/2003-11/msg00999.html (10,185 bytes)
11. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Wed, 19 Nov 2003 07:33:53 -0800; 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 wit; /archives/netdev/2003-11/msg01004.html (10,712 bytes)
12. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>; Date: Thu, 20 Nov 2003 17:34:08 +0100; The i825xx Ethernet chips are configured by putting a configure command on the TX list. One of the bits of the configure command tells the chip to discard or keep packets with errors. Assuming you ca; /archives/netdev/2003-11/msg01045.html (14,826 bytes)
13. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Sun, 23 Nov 2003 01:02:41 -0800; 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 trans; /archives/netdev/2003-11/msg01073.html (11,642 bytes)
14. Re: RFC: Enabling ethernet drivers to return FCS in the skb? (score: 1): Author: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>; Date: Mon, 24 Nov 2003 01:05:05 +0100; [Intel i82557/8/9 Ethernet chips] Saving bad frames to memory is controlled by CB_CFIG_SAVE_BAD_FRAMES in byte 6. Saving the FCS to memory is controlled by CB_CFIG_CRC_IN_MEM in byte 18. See drivers/; /archives/netdev/2003-11/msg01086.html (9,841 bytes)

Current List: 1 - 14
Page: [1]