From: Ben Greear <greearb@candelatech.com>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v4] e1000: Support RX-ALL flag.
Date: Thu, 29 Mar 2012 18:56:50 -0700 [thread overview]
Message-ID: <4F7512E2.9010502@candelatech.com> (raw)
In-Reply-To: <1333068960.2622.72.camel@jtkirshe-mobl>
On 03/29/2012 05:56 PM, Jeff Kirsher wrote:
> On Thu, 2012-03-29 at 15:47 -0700, greearb@candelatech.com wrote:
>>
>> From: Ben Greear<greearb@candelatech.com>
>>
>> This allows the NIC to receive errored frames (bad FCS, etc)
>> and pass them up the stack. This can be useful when using
>> sniffers.
>>
>> Signed-off-by: Ben Greear<greearb@candelatech.com>
>> ---
>> :100644 100644 a680ee6... ab2f748...
>> M drivers/net/ethernet/intel/e1000/e1000_main.c
>> drivers/net/ethernet/intel/e1000/e1000_main.c | 22
>> ++++++++++++++++++++--
>> 1 files changed, 20 insertions(+), 2 deletions(-)
>
> FYI- I was just about to push this upstream :) Thanks Ben!
>
> This is the same patch Aaron has tested in-house.
Sounds good.
From what I recall, igb is missing rx-fcs (and it may not be possible to
support the feature..chipset seems to act weird), but I think that takes care
of the rest of the 10/100/1000 Intel NICs.
I'll see if I can add some support for ixgbe when I get a chance. That would
take care of all the NICs I normally use I think...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-03-30 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 22:47 [PATCH v4] e1000: Support RX-ALL flag greearb
2012-03-30 0:56 ` Jeff Kirsher
2012-03-30 1:56 ` Ben Greear [this message]
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=4F7512E2.9010502@candelatech.com \
--to=greearb@candelatech.com \
--cc=jeffrey.t.kirsher@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).