From: Emil Micek <emil.micek@tkrjasek.cz>
To: netdev mailing list <netdev@vger.kernel.org>
Cc: "auke-jan.h.kok@intel.com" <auke-jan.h.kok@intel.com>,
Ben Greear <greearb@candelatech.com>,
Chris Leech <chris.leech@gmail.com>,
Francesco Fondelli <francesco.fondelli@gmail.com>,
jamal <hadi@cyberus.ca>, Jesse <jesse.brandeburg@intel.com>
Subject: Re: change the way e1000 is handling short VLAN frames
Date: Mon, 24 Sep 2007 10:40:51 +0200 [thread overview]
Message-ID: <1190623251.3614.30.camel@magi.nadr> (raw)
In-Reply-To: <41b516cb0709211502v5a9931bfx267d163c51bd4958@mail.gmail.com>
Thanks for your replies.
We contacted Arris (manufacturer of our CMTS) about this issue with
links to relevant parts of specification about minimum size of VLAN
tagged frames and it seems they'll acknowledge the problem and fix it in
next firmware.
Meantime i tried different suggestions posted there (patch from Chris,
replacing ETH_ZLEN with VLAN_ETH_ZLEN in e1000_main.c and disabling HW
VLAN tagging in netdev->features) and combinations of them, but none of
it worked and 64B VLAN frames are still generated by our intel NIC.
I'll now consider this issue as closed on the e1000 and intel NIC side,
because there was no problem with them in the first place, and I'll
rather concentrate on resolving it on the CMTS side which doesn't act
according to specs.
Cheer
Emil.
next prev parent reply other threads:[~2007-09-24 8:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 7:31 change the way e1000 is handling short VLAN frames Emil Micek
2007-09-21 11:59 ` jamal
2007-09-21 12:50 ` Emil Micek
2007-09-21 13:37 ` jamal
2007-09-21 13:46 ` jamal
2007-09-21 14:27 ` Francesco Fondelli
2007-09-21 15:43 ` Ben Greear
2007-09-21 21:12 ` jamal
2007-09-21 21:18 ` Ben Greear
2007-09-21 21:21 ` Kok, Auke
2007-09-21 21:29 ` jamal
2007-09-21 21:34 ` Kok, Auke
2007-09-21 21:43 ` jamal
2007-09-21 22:02 ` Chris Leech
2007-09-24 8:40 ` Emil Micek [this message]
2007-09-21 21:27 ` Chris Leech
2007-09-21 21:36 ` jamal
2007-09-21 17:05 ` Brandeburg, Jesse
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=1190623251.3614.30.camel@magi.nadr \
--to=emil.micek@tkrjasek.cz \
--cc=auke-jan.h.kok@intel.com \
--cc=chris.leech@gmail.com \
--cc=francesco.fondelli@gmail.com \
--cc=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=jesse.brandeburg@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).