From: Michael Zimmermann <sigmaepsilon92@gmail.com>
To: valerij zaporogeci <vlrzprgts@gmail.com>
Cc: edk2-devel <edk2-devel@lists.01.org>
Subject: Re: Crc32
Date: Wed, 31 Aug 2016 05:54:27 +0200 [thread overview]
Message-ID: <CAN9vWDKDx+s7n4YYZv69dc9J01rHgrj=mJEH776m-+j=1OwmJQ@mail.gmail.com> (raw)
In-Reply-To: <CANPuzFwZvhY_ezYu+PkP8k40dsTTB7eKYdYJXsVNvijD0C_jHg@mail.gmail.com>
it doesn't. it just seems that if the crc text field is not empty it
calculates the crc of the crc, so you have to hit the "Reset CRC" button
before reprocessing the text.
On Wed, Aug 31, 2016 at 3:11 AM, valerij zaporogeci <vlrzprgts@gmail.com>
wrote:
> >> after testing it it indeed produces CCITT32 results like this online
> generator:
> >> http://g6auc.me.uk/CRC32/index.html
>
> I only now noticed that this "calculator", gives DIFFERENT values on
> the same input, no matter hex or text based.
> Interestingly, how it could produce the same results as the Tianocore
> implementation?
>
> I was thinking that all the difference in the Tianocore impl. from the
> pure crc is appending 32 1's at the beginning of the (input) message
> and then negating the Crc itself in the end.
>
> I see, the only way to check is to pull off the Tianocore function and
> check.)
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>
next prev parent reply other threads:[~2016-08-31 3:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 0:54 Crc32 valerij zaporogeci
2016-08-30 11:08 ` Crc32 Michael Zimmermann
2016-08-30 13:32 ` Crc32 valerij zaporogeci
2016-08-30 14:09 ` Crc32 Andrew Fish
2016-08-30 15:17 ` Crc32 valerij zaporogeci
2016-08-30 16:15 ` Crc32 Andrew Fish
2016-08-31 1:11 ` Crc32 valerij zaporogeci
2016-08-31 3:54 ` Michael Zimmermann [this message]
2016-08-31 14:31 ` Crc32 valerij zaporogeci
2016-08-31 23:27 ` Crc32 valerij zaporogeci
2016-09-01 22:36 ` Crc32 valerij zaporogeci
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-list 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='CAN9vWDKDx+s7n4YYZv69dc9J01rHgrj=mJEH776m-+j=1OwmJQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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