Wireshark mailing list archives
Re: Calculating CRC5 of 11-bit data
From: Tomasz Moń <desowin () gmail com>
Date: Sat, 20 Jul 2019 10:10:36 +0200
On Sat, Jul 20, 2019 at 5:37 AM Tomasz Moń <desowin () gmail com> wrote:
The advantage of 1) over 2) is the ability to be able, if the CRC is incorrect, to tell what the correct CRC should have been. Approach 2) allows only to veify if the CRC is correct - but at the advantage of being able to take full bytes as input.
Approach 2) is now implemented [1]. [1] https://code.wireshark.org/review/#/c/34025/ ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Calculating CRC5 of 11-bit data Tomasz Moń (Jul 19)
- Re: Calculating CRC5 of 11-bit data Ross Jacobs (Jul 19)
- Re: Calculating CRC5 of 11-bit data Tomasz Moń (Jul 19)
- Re: Calculating CRC5 of 11-bit data Guy Harris (Jul 19)
- Re: Calculating CRC5 of 11-bit data Tomasz Moń (Jul 19)
- Re: Calculating CRC5 of 11-bit data Tomasz Moń (Jul 20)
- Re: Calculating CRC5 of 11-bit data John Sullivan (Jul 20)
- Re: Calculating CRC5 of 11-bit data Tomasz Moń (Jul 20)
- Re: Calculating CRC5 of 11-bit data John Sullivan (Jul 21)
- Re: Calculating CRC5 of 11-bit data Tomasz Moń (Jul 25)
- Re: Calculating CRC5 of 11-bit data Tomasz Moń (Jul 19)
- Re: Calculating CRC5 of 11-bit data Ross Jacobs (Jul 19)