netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Ben Greear <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: [PATCH 3/3] rx_all e100 patch
Date: Tue, 25 Nov 2003 16:21:56 +0100	[thread overview]
Message-ID: <20031125162152.D1107@sygehus.dk> (raw)
In-Reply-To: <3FC30AEE.7000005@candelatech.com>; from greearb@candelatech.com on Mon, Nov 24, 2003 at 11:55:26PM -0800

On Mon, Nov 24, 2003 at 11:55:26PM -0800, Ben Greear wrote:
> @@ -2052,13 +2065,26 @@
>  			if (bdp->rev_id >= D102_REV_ID) {
>  				skb->ip_summed = e100_D102_check_checksum(rfd);
>  			} else {
> -				skb->ip_summed = e100_D101M_checksum(bdp, skb);
> +				skb->ip_summed = e100_D101M_checksum(bdp, skb, !!(dev->priv_flags & IFF_ACCEPT_ALL_FRAMES));
>  			}

Shouldn't that be IFF_SAVE_FCS rather than IFF_ACCEPT_ALL_FRAMES?

>  		} else {
>  			skb->ip_summed = CHECKSUM_NONE;
>  		}
>  
> +		/* Show the FCS? */
> +		if (unlikely(dev->priv_flags & IFF_SAVE_FCS)) {
> +			if (bdp->rev_id < D102_REV_ID) {
> +				/* Have to over-write the two IP checksum bytes
> +				 * TODO:  Will this break vlan_hwaccel_rx???
> +				 */
> +				skb->tail[-4] = skb->tail[-2];
> +				skb->tail[-3] = skb->tail[-1];
> +				skb->tail[-2] = skb->tail[0];
> +				skb->tail[-1] = skb->tail[1];
> +			}
> +		}
> +		

I don't understand this part of the code. The 55x docs say that the IP
checksum bytes are transferred to memory _following_ the FCS.

> +/**
> + * e100_config_promisc - configure promiscuous mode
> + * @bdp: atapter's private data struct
> + * @enable: should we enable this option or not

s/atapter/adapter/g

s/etherne /ethernet /g too, somewhere, IIRC.

> +/* Only valid for 82558 and 82559.  Must be zero for 82557 */
> +#define CB_CFIG_LONG_RX_OK          BIT_3	/* OK to receive Long frames */

I find it disappointing that the good, old 82586 transfers long frames to
memory without complaint while newer chips such as the 82557 and tulip
can't/don't.

-- 
Regards,
Rask Ingemann Lambertsen

  reply	other threads:[~2003-11-25 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  7:55 [PATCH 3/3] rx_all e100 patch Ben Greear
2003-11-25 15:21 ` Rask Ingemann Lambertsen [this message]
2003-11-25 18:03   ` Ben Greear
2003-11-25 23:41     ` Rask Ingemann Lambertsen
2003-11-25 16:56 ` Rask Ingemann Lambertsen
  -- strict thread matches above, loose matches on Subject: below --
2003-11-25 17:39 Feldman, Scott
2003-11-25 18:05 ` Ben Greear

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=20031125162152.D1107@sygehus.dk \
    --to=rask@sygehus.dk \
    --cc=greearb@candelatech.com \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).