From: Dan Malek <dan@embeddededge.com>
To: Peter Desnoyers <pdesnoyers@chinook.com>
Cc: Goddeeris Frederic <Frederic.Goddeeris@siemens.atea.be>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: FEC driver multicast patch
Date: Fri, 01 Feb 2002 11:36:17 -0500 [thread overview]
Message-ID: <3C5AC401.6030607@embeddededge.com> (raw)
In-Reply-To: 3C5AC192.E0500B87@chinook.com
Peter Desnoyers wrote:
> I think he took your suggestion to heart. fec_mulicast_calc_crc(char
> *pAddr) is a straightforward software implementation of the bit-by-bit
> CRC32 algorithm.
Apologies. I just quickly looked at and assumed it was still using SCCs.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-01 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 10:09 FEC driver multicast patch Goddeeris Frederic
2002-02-01 16:05 ` Dan Malek
[not found] ` <3C5AC192.E0500B87@chinook.com>
2002-02-01 16:36 ` Dan Malek [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=3C5AC401.6030607@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Frederic.Goddeeris@siemens.atea.be \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pdesnoyers@chinook.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).