From: John Newlin <jnewlin@rawbw.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Ethernet driver question
Date: Wed, 29 Oct 2003 18:24:00 -0000 [thread overview]
Message-ID: <3FA005C0.7070804@rawbw.com> (raw)
Couple of silly questions, I like multiple choice:
1) When the HDWR_Send function is called, is there:
a) a valid FCS already at the end of the data?
b) 4 bytes where the FCS should be, but expects the hardware to change
it on the way out
c) No FCS, expects the hardware to append an FCS
(Our hardware can generate an FCS, so would save some cycles if the FCS
were not generated in software)
2) When HDWR_recv is called to get a packet, does it expect a valid enet
frame including MAC address, and FCS on the end, or does it want those
stripped off? I imagine the former is correct, but I just want to make
sure.
Thanks,
-John Newlin
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-10-29 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 18:24 John Newlin [this message]
2003-10-30 7:54 ` Laurent GONZALEZ
2007-10-05 12:24 Gokoen
2007-10-08 8:30 ` Jürgen Lambrecht
2007-10-09 11:45 ` Gokoen
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=3FA005C0.7070804@rawbw.com \
--to=jnewlin@rawbw.com \
--cc=ecos-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).