From: Ben Greear <greearb@candelatech.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: RFC: Enabling ethernet drivers to return FCS in the skb?
Date: Sun, 23 Nov 2003 01:02:41 -0800 [thread overview]
Message-ID: <3FC077B1.1050807@candelatech.com> (raw)
In-Reply-To: <20031120173404.A1538@sygehus.dk>
Rask Ingemann Lambertsen wrote:
> On Wed, Nov 19, 2003 at 07:33:53AM -0800, Ben Greear wrote:
>
>>Rask Ingemann Lambertsen wrote:
>>
>>>The Intel i82586 and i82596 and can be told to receive frames with a bad FCS.
>>>They can also be told to send a precomputed FCS rather than computing it on
>>>the fly. The i82596 and tulip can also transfer the FCS to memory when
>>>receiving frames. I guess all of this is also supported on the i82557/8/9.
>>
>>If you have a patch or example code that shows how to do this, I'd love to
>>see it. I have code that should RX bad CSUM from the Intel folks, but I can't
>>get it to generate bad CRC (it does framing errors instead with my attempt),
>>so I can't test the RX code properly!
>
>
> The i825xx Ethernet chips are configured by putting a configure command on
> the TX list. One of the bits of the configure command tells the chip to
> discard or keep packets with errors. Assuming you can find that piece of
> code, flipping the bit is easy enough. Similiarily for transferring the FCS
> to/from memory. IIRC, this is a per-frame setting for TX on i82596 and
> i82557/8/9. You can find i82596 documentation on Intel's home page and
> the i82557/8/9 on SourceForge under the e100 (or was it e1000?) project.
Thanks, I found the e100 document (from sourceforge) and it looks like it can
definately receive all sorts of busted packets with a little configuration.
It's less clear what happens when you turn off the FCS generation. One part of
the document mentions it gets it from RAM, which I assume means it uses the last
part of the DMA'd packet??? Another explanation of the transmit state machine does
not mention that you can disable FCS generation... I'm going to print this out
and read it again in detail...
I searched Intel's site for the e1000 docs, but could not find any detailed
information. Does anyone have a link to a (legal) copy of the e1000 docs?
Thanks for the detailed information. When I get the e100 and e1000 working to
my satisfaction, I'll work on the tulip driver a bit.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2003-11-23 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 21:52 RFC: Enabling ethernet drivers to return FCS in the skb? Ben Greear
2003-11-19 11:35 ` Rask Ingemann Lambertsen
2003-11-19 13:20 ` Maciej W. Rozycki
2003-11-19 15:33 ` Ben Greear
2003-11-20 16:34 ` Rask Ingemann Lambertsen
2003-11-23 9:02 ` Ben Greear [this message]
2003-11-24 0:05 ` Rask Ingemann Lambertsen
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=3FC077B1.1050807@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=rask@sygehus.dk \
/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).