From: "Elliott, Robert (Servers)" <elliott@hpe.com>
To: Kamlesh Gurudasani <kamlesh@ti.com>, Eric Biggers <ebiggers@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>
Subject: RE: Re: [PATCH v2 2/6] crypto: crc64 - add crc64-iso framework
Date: Thu, 22 Feb 2024 21:50:44 +0000 [thread overview]
Message-ID: <MW5PR84MB18424EC8DDB4863777D302E2AB562@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87jztserrf.fsf@kamlesh.i-did-not-set--mail-host-address--so-tickle-me>
> -----Original Message-----
> From: Kamlesh Gurudasani <kamlesh@ti.com>
> Sent: Friday, August 18, 2023 2:26 AM
> Subject: Re: [EXTERNAL] Re: [PATCH v2 2/6] crypto: crc64 - add crc64-iso
> framework
>
> Eric Biggers <ebiggers@kernel.org> writes:
>
> > Is "crc64-iso" clear enough, or should it be "crc64-iso3309"? There are
> > thousands of ISO standards. Different CRC variants are specified by
> different
> > ISO standards. Is this particular variant indeed commonly referred to
> as simply
> > the "ISO" CRC-64? Even if it's currently the case that all other CRCs
> in ISO
> > standards are different widths than 64 bits (which may be unlikely?),
> I'm not
> > sure we should count on no CRC-64 variant ever being standardized by
> ISO.
> >
> > - Eric
> https://en.wikipedia.org/wiki/Cyclic_redundancy_check
>
> Last entry CRC-64-ISO in the table.
> It is mentioned as crc64-iso and that's the
> only 64-bit CRC standardized by ISO.
ECMA-182 (DLT-1 tapes) was contributed to become ISO/IEC 13421 in 1993, so
that was another "64-bit CRC standardized by ISO." Plus, ISO could publish new
standards with new CRCs at any time.
> But I do agree that crc64-iso3309 would be more specific, will change it
> to crc64-iso3309 in next revision. Thanks.
>
> Regards,
> Kamlesh
ISO-3309:1991 was withdrawn and revised by
ISO/IEC 3309:1993, which was withdrawn and revised by
ISO/IEC 13239:2002, which was confirmed in 2007 and is still current.
Apparently only the 1991 version defined a CRC-64; later versions dropped
that.
Is there really a demand for adding a 23 year old deprecated algorithm to
the kernel?
next prev parent reply other threads:[~2024-02-22 21:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 19:28 [PATCH v2 0/6] Add support for Texas Instruments MCRC64 engine Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 1/6] lib: add ISO 3309 model crc64 Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 2/6] crypto: crc64 - add crc64-iso framework Kamlesh Gurudasani
2023-08-11 4:24 ` Eric Biggers
2023-08-11 6:40 ` [EXTERNAL] " Kamlesh Gurudasani
2023-08-12 2:55 ` Eric Biggers
2023-08-18 7:25 ` [EXTERNAL] " Kamlesh Gurudasani
2024-02-22 21:50 ` Elliott, Robert (Servers) [this message]
2024-02-29 8:45 ` Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 3/6] dt-bindings: crypto: Add Texas Instruments MCRC64 Kamlesh Gurudasani
2023-08-11 15:34 ` Conor Dooley
2023-08-11 15:36 ` Conor Dooley
2024-05-27 8:25 ` [EXTERNAL] " Kamlesh Gurudasani
2024-05-27 8:33 ` Krzysztof Kozlowski
2024-05-27 10:11 ` Kamlesh Gurudasani
2024-05-29 5:13 ` Vignesh Raghavendra
2023-08-10 19:28 ` [PATCH v2 4/6] crypto: ti - add driver for MCRC64 engine Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 5/6] arm64: dts: ti: k3-am62: Add dt node, cbass_main ranges for MCRC64 Kamlesh Gurudasani
2023-08-10 20:21 ` Nishanth Menon
2023-08-10 19:28 ` [PATCH v2 6/6] arm64: defconfig: enable TI MCRC64 module Kamlesh Gurudasani
2023-08-10 20:25 ` Nishanth Menon
2023-08-12 3:01 ` [PATCH v2 0/6] Add support for Texas Instruments MCRC64 engine Eric Biggers
2023-08-18 9:06 ` [EXTERNAL] " Kamlesh Gurudasani
2023-08-22 5:17 ` Eric Biggers
2023-08-30 11:51 ` [EXTERNAL] " Kamlesh Gurudasani
2023-09-20 6:53 ` Kamlesh Gurudasani
2023-10-03 6:07 ` Kamlesh Gurudasani
2023-08-30 13:48 ` Kamlesh Gurudasani
2023-08-30 14:34 ` Kamlesh Gurudasani
2023-08-30 14:46 ` Kamlesh Gurudasani
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=MW5PR84MB18424EC8DDB4863777D302E2AB562@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM \
--to=elliott@hpe.com \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kamlesh@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=will@kernel.org \
/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