From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: netdev@oss.sgi.com
Subject: Re: [PATCH] e100: Enable receiving bogus packets, and transmitting bad/custom CRC
Date: Tue, 25 Nov 2003 15:56:12 +0100 [thread overview]
Message-ID: <20031125155612.C1107@sygehus.dk> (raw)
In-Reply-To: <3FC298C9.8080302@candelatech.com>; from greearb@candelatech.com on Mon, Nov 24, 2003 at 03:48:25PM -0800
On Mon, Nov 24, 2003 at 03:48:25PM -0800, Ben Greear wrote:
>
> So, RX-ALL can be one flag, another for RX-FCS, and the TX-CUSTOM-FCS
> can be a separate patch altogether?
Yes. For example, the i82586 can support RX-ALL but not RX-FCS, and
TX-CUSTOM-FCS would be more work than with i82596 and i82557/8/9. Since the
i82586 has a global (as opposed to per TX cmd) TX-CUSTOM-FCS flag, it would
be necessary to send a configure command whenever this flag changes from one
TX skb to another. So yes, please separate these features.
--
Regards,
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2003-11-25 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 23:24 [PATCH] e100: Enable receiving bogus packets, and transmitting bad/custom CRC Ben Greear
2003-11-24 23:29 ` David S. Miller
2003-11-24 23:48 ` Ben Greear
2003-11-25 1:33 ` David S. Miller
2003-11-25 7:53 ` [PATCH 0/3] e100: Enable receiving bogus packets and saving FCS Ben Greear
2003-11-25 14:42 ` [PATCH] e100: Enable receiving bogus packets, and transmitting bad/custom CRC Rask Ingemann Lambertsen
2003-11-25 14:45 ` David S. Miller
2003-11-25 14:56 ` Rask Ingemann Lambertsen [this message]
2003-12-13 19:00 ` Rask Ingemann Lambertsen
2003-12-13 19:12 ` 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=20031125155612.C1107@sygehus.dk \
--to=rask@sygehus.dk \
--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).