public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Steve Strublic <SStrublic@hypercom.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] No zlib crc32 support?
Date: Tue, 09 Dec 2003 20:45:00 -0000	[thread overview]
Message-ID: <1071002700.16658.151.camel@hermes> (raw)
In-Reply-To: <OF4C671845.2019E8CA-ON07256DF7.006FE816-07256DF7.00707DF0@hypercom.com>

On Tue, 2003-12-09 at 13:25, Steve Strublic wrote:
> Hello all,
> 
> I'm working on a little project to perform validation of a data set, and planned to use zlib's crc32
> call to validate the data.  Much to my surprise, I found that eCos does not support the crc32
> call--apparently, on purpose.
> 
> Would someone be so kind as to explain why this is the case?  I know I can use Adler32 as it's
> supported, but I'm just wondering why crc32 isn't supported.

Actually, I think it's just not duplicated in the ZLIB package.
CRC32 is available in the CRC package.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-12-09 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 20:29 Steve Strublic
2003-12-09 20:45 ` Gary Thomas [this message]
2003-12-09 21:08 Steve Strublic
2003-12-09 21:27 ` Gary Thomas
2003-12-10  8:39 ` Andrew Lunn
2003-12-10 16:14 Steve Strublic
2003-12-10 16:20 ` Gary Thomas
2003-12-11  0:38 ` Andrew Lunn
2003-12-10 16:22 Steve Strublic
2003-12-12 22:35 Steve Strublic
2003-12-15  8:33 ` Andrew Lunn
2003-12-15 17:56 Steve Strublic
2003-12-15 19:52 ` Nick Garnett

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=1071002700.16658.151.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=SStrublic@hypercom.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).