From: Heiko Schocher <hs@nabladev.com>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Tom Rini <trini@konsulko.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com>,
Andrew Goodbody <andrew.goodbody@linaro.org>,
Anshul Dalal <anshuld@ti.com>,
Arturs Artamonovs <arturs.artamonovs@analog.com>,
Casey Connolly <casey.connolly@linaro.org>,
Dinesh Maniyam <dinesh.maniyam@altera.com>,
Greg Malysa <malysagreg@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ibai Erkiaga <ibai.erkiaga-elorza@amd.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Jerome Forissier <jerome.forissier@linaro.org>,
"Kory Maincent (TI.com)" <kory.maincent@bootlin.com>,
Marek Vasut <marek.vasut@mailbox.org>,
Martin Schwan <m.schwan@phytec.de>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
Michael Trimarchi <michael@amarulasolutions.com>,
Michal Simek <michal.simek@amd.com>,
Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Oliver Gaskell <Oliver.Gaskell@analog.com>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
Peng Fan <peng.fan@nxp.com>,
Peter Robinson <pbrobinson@gmail.com>,
Philippe Reynes <philippe.reynes@softathome.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Raymond Mao <raymondmaoca@gmail.com>,
Sean Edmond <seanedmond@microsoft.com>,
Simon Glass <sjg@chromium.org>,
Stefan Roese <stefan.roese@mailbox.org>,
Sumit Garg <sumit.garg@kernel.org>,
Utsav Agarwal <utsav.agarwal@analog.com>,
Vasileios Bimpikas <vasileios.bimpikas@analog.com>,
Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>,
briansune <briansune@gmail.com>
Subject: Re: [PATCH v3 0/6] Add support for SM3 secure hash
Date: Mon, 8 Dec 2025 10:26:35 +0100 [thread overview]
Message-ID: <6bb63d2f-6bf0-3610-940f-6656b104b22d@nabladev.com> (raw)
In-Reply-To: <CAC_iWjK9zG3=x4n6n_kqJvp-SFKYqO6sFE-LcajC+h+0+Y-gNw@mail.gmail.com>
Hello Ilias,
On 08.12.25 10:07, Ilias Apalodimas wrote:
> Heiko,
>
> I had another look. Oberall the changes seem fine and I don't mind keeping them.
> Any chance you tested this on actual hardware?
I have here an imx8mp board with tpm chip, and I try to test
it soon... sorry for the delay.
bye,
Heiko
>
> Cheers
> /Ilias
>
> On Fri, 5 Dec 2025 at 16:11, Tom Rini <trini@konsulko.com> wrote:
>>
>> On Fri, Dec 05, 2025 at 09:02:28AM +0100, Heiko Schocher wrote:
>>> Hello Ilias,
>>>
>>> On 05.12.25 08:24, Ilias Apalodimas wrote:
>>>> On Fri, 5 Dec 2025 at 07:03, Heiko Schocher <hs@nabladev.com> wrote:
>>>>>
>>>>> Hello Tom,
>>>>>
>>>>> On 04.12.25 20:31, Tom Rini wrote:
>>>>>> On Tue, 18 Nov 2025 05:30:36 +0100, Heiko Schocher wrote:
>>>>>>
>>>>>>> Add SM3 secure hash, as specified by OSCCA GM/T 0004-2012 SM3 and described
>>>>>>> at https://datatracker.ietf.org/doc/html/draft-sca-cfrg-sm3-02
>>>>>>>
>>>>>>> TPMv2 defines hash algo sm3_256, which is currently
>>>>>>> not supported and prevented TPMv2 chip with newer
>>>>>>> firmware to work with U-Boot. Seen this on a ST33TPHF2XI2C
>>>>>>>
>>>>>>> [...]
>>>>>>
>>>>>> Applied to u-boot/next, thanks!
>>>>>>
>>>>>> [1/6] lib: Import rol32 function from Linux
>>>>>> commit: 6a0c939b88fd42c6b0a374f7c87317f292df46a1
>>>>>> [2/6] lib: import sm3 256 hash parts from linux
>>>>>> commit: 41c0131b950a16747929ab310588cf5db8e38123
>>>>>> [3/6] lib: sm3: implement U-Boot parts
>>>>>> commit: c4ab316269debc321907acc4f8f02dfe5653aeaf
>>>>>> [4/6] test: cmd: hash: add unit test for sm3_256
>>>>>> commit: 213601a600f1e8894cea76b0bfc131f038882407
>>>>>> [5/6] tpm2: add sm3 256 hash support
>>>>>> commit: 7c3f05ad51e4bc23dd4f411f28968f1d8f43099c
>>>>>> [6/6] test: cmd: fix a typo in md5 test
>>>>>> commit: b30557b3b46c5162cb88a57907c517ed95557239
>>>>>
>>>>> Oh, may a little to fast, as Ilias and Quentin had some comments
>>>>> about tpm2 implementation/test (tpm2: add sm3 256 hash support
>>>>> patch). But I can send changes on top of that patches (but
>>>>> give me some time for it... end of year rally has started...)
>>>>>
>>>>
>>>> Yea I pinged Tom yesterday.
>>>> tbh, my main concern was testing the changes. I dont mind if we revert
>>>> and reapply or send the changes on top.
>>>
>>> I am fine with sending updates on top.
>>
>> Sorry for getting ahead of everyone else here, since it sounds like
>> everyone is OK with updates on top, we can move forward. Thanks!
>>
>> --
>> Tom
--
Nabla Software Engineering
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Geschäftsführer : Stefano Babic
prev parent reply other threads:[~2025-12-08 12:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 4:30 [PATCH v3 0/6] Add support for SM3 secure hash Heiko Schocher
2025-11-18 4:30 ` [PATCH v3 1/6] lib: Import rol32 function from Linux Heiko Schocher
2025-11-18 4:30 ` [PATCH v3 2/6] lib: import sm3 256 hash parts from linux Heiko Schocher
2025-11-19 11:02 ` Ilias Apalodimas
2025-11-18 4:30 ` [PATCH v3 3/6] lib: sm3: implement U-Boot parts Heiko Schocher
2025-11-18 10:30 ` Quentin Schulz
2025-11-19 7:13 ` Heiko Schocher
2025-11-18 4:30 ` [PATCH v3 4/6] test: cmd: hash: add unit test for sm3_256 Heiko Schocher
2025-11-18 4:30 ` [PATCH v3 5/6] tpm2: add sm3 256 hash support Heiko Schocher
2025-11-18 4:30 ` [PATCH v3 6/6] test: cmd: fix a typo in md5 test Heiko Schocher
2025-11-18 10:06 ` [PATCH v3 0/6] Add support for SM3 secure hash Ilias Apalodimas
2025-11-18 15:11 ` Raymond Mao
2025-11-19 5:40 ` Heiko Schocher
2025-11-19 7:18 ` Ilias Apalodimas
2025-12-04 19:31 ` Tom Rini
2025-12-05 5:03 ` Heiko Schocher
2025-12-05 7:24 ` Ilias Apalodimas
2025-12-05 8:02 ` Heiko Schocher
2025-12-05 14:11 ` Tom Rini
2025-12-08 9:07 ` Ilias Apalodimas
2025-12-08 9:26 ` Heiko Schocher [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=6bb63d2f-6bf0-3610-940f-6656b104b22d@nabladev.com \
--to=hs@nabladev.com \
--cc=Oliver.Gaskell@analog.com \
--cc=alif.zakuan.yuslaimi@altera.com \
--cc=andrew.goodbody@linaro.org \
--cc=anshuld@ti.com \
--cc=arturs.artamonovs@analog.com \
--cc=briansune@gmail.com \
--cc=casey.connolly@linaro.org \
--cc=dinesh.maniyam@altera.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=kory.maincent@bootlin.com \
--cc=m.schwan@phytec.de \
--cc=malysagreg@gmail.com \
--cc=marek.vasut@mailbox.org \
--cc=michael@amarulasolutions.com \
--cc=michal.simek@amd.com \
--cc=mikhail.kshevetskiy@iopsys.eu \
--cc=miquel.raynal@bootlin.com \
--cc=mkorpershoek@kernel.org \
--cc=nathan.morrison@timesys.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=pbrobinson@gmail.com \
--cc=peng.fan@nxp.com \
--cc=philippe.reynes@softathome.com \
--cc=quentin.schulz@cherry.de \
--cc=raymondmaoca@gmail.com \
--cc=seanedmond@microsoft.com \
--cc=sjg@chromium.org \
--cc=stefan.roese@mailbox.org \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=utsav.agarwal@analog.com \
--cc=vasileios.bimpikas@analog.com \
--cc=venkatesh.abbarapu@amd.com \
--cc=xypron.glpk@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.