From: Jonas Rebmann <jre@pengutronix.de>
To: Fabian Pflug <f.pflug@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] common: misc: add soc_uid_hex to globalvar
Date: Wed, 15 Apr 2026 13:14:49 +0200 [thread overview]
Message-ID: <46cbcdfd-4507-47a2-b381-07757011f379@pengutronix.de> (raw)
In-Reply-To: <20260415-v2026-03-0-topic-soc_bin_id-v2-1-81fab6ba5de0@pengutronix.de>
On 2026-04-15 13:10, Fabian Pflug wrote:
> uidstr and uidbuf could be the same, but don't have to be. This results
> in uncertainty on what exactly is the current UID used for
> machine_set_hashable and to compare against with TLV.
>
> Add an additional global var, that encodes SoC-UID registers in a
> manner uniform across SoCs/manufacturers.
>
> This can now be used to feed as data for bound-soc-uid into
> `bareboxtlv-generator.py` or as the value for
> `CONFIG_HABV4_CSF_UNLOCK_UID`
>
> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
Reviewed-by: Jonas Rebmann <jre@pengutronix.de>
next prev parent reply other threads:[~2026-04-15 11:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 11:10 [PATCH v2 0/2] Add additional globalvar for soc_uid Fabian Pflug
2026-04-15 11:10 ` [PATCH v2 1/2] common: misc: add soc_uid_hex to globalvar Fabian Pflug
2026-04-15 11:14 ` Jonas Rebmann [this message]
2026-04-22 7:56 ` Sascha Hauer
2026-04-22 8:14 ` Fabian Pflug
2026-04-22 8:25 ` Sascha Hauer
2026-04-22 8:52 ` Fabian Pflug
2026-04-22 9:16 ` Sascha Hauer
2026-04-22 9:19 ` Fabian Pflug
2026-04-22 9:38 ` Sascha Hauer
2026-04-15 11:10 ` [PATCH v2 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID Fabian Pflug
2026-04-15 11:14 ` Jonas Rebmann
2026-04-22 7:43 ` Sascha Hauer
2026-04-22 7:49 ` Fabian Pflug
2026-04-22 9:47 ` Jonas Rebmann
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=46cbcdfd-4507-47a2-b381-07757011f379@pengutronix.de \
--to=jre@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@pengutronix.de \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox