netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Andersson <johan.andersson@transmode.se>
To: Auke Kok <auke-jan.h.kok@intel.com>, netdev@vger.kernel.org
Subject: e1000e: Hardware CRC stripping doesn't work with 82566DM-2
Date: Wed, 06 Feb 2008 21:42:28 +0100	[thread overview]
Message-ID: <47AA1BB4.8010802@transmode.se> (raw)

Hi,

In commit 140a74802894e9db57e5cd77ccff77e590ece5f3 a workaround for crc 
stripping was removed.
However, the hardware supported crc stripping now in use doesn't seem to 
work with the following chip:
Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) (8086:10bd)

I discovered this while trying to make this nic member of a bridge. 
Since some frames get too large for the bridge they are dropped, making 
it impossible to use this nic in a bridge.

Reverting this commit makes the nic and brigde work again.

Are there any more chips in this family suffering from this?

/Johan Andersson



             reply	other threads:[~2008-02-06 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 20:42 Johan Andersson [this message]
2008-02-06 21:43 ` e1000e: Hardware CRC stripping doesn't work with 82566DM-2 Kok, Auke
2008-02-07  6:19   ` Johan Andersson

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=47AA1BB4.8010802@transmode.se \
    --to=johan.andersson@transmode.se \
    --cc=auke-jan.h.kok@intel.com \
    --cc=netdev@vger.kernel.org \
    /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).