From: Fabian Pflug <f.pflug@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Jonas Rebmann <jre@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] common: misc: add soc_uid_hex to globalvar
Date: Wed, 22 Apr 2026 11:19:02 +0200 [thread overview]
Message-ID: <3e226610c6b2e4a5b2f2d702d4eb11c03680cbac.camel@pengutronix.de> (raw)
In-Reply-To: <aeiR55jQR56V3YDQ@pengutronix.de>
On Wed, 2026-04-22 at 11:16 +0200, Sascha Hauer wrote:
> On Wed, Apr 22, 2026 at 10:52:34AM +0200, Fabian Pflug wrote:
> >
> > There already is
> >
> > BAREBOX_MAGICVAR(global.soc_uid_hex, "SoC Unique ID (in hex)");
> >
> > And since it is a single value and not a byte array, I think byte array is the wrong representation.
> > Using a byte-array for TLV does not work with the TLV tooling. This expects a single value.
>
> You are right, byte array is not the correct term here. What I wanted to
> make clear is that it is the raw buffer content with the first byte in
> the buffer being the first two digits of the string, just to make the
> difference between these two clearer:
>
> global.soc_uid=0011223344556677 "SoC Unique ID"
> global.soc_uid_hex=7766554433221100 "SoC Unique ID (in hex)"
>
> Both are obviously hex values, which one means what?
maybe "Raw SoC Unique ID (vendor independent representation)"?
>
> Sascha
next prev parent reply other threads:[~2026-04-22 9:19 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
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 [this message]
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=3e226610c6b2e4a5b2f2d702d4eb11c03680cbac.camel@pengutronix.de \
--to=f.pflug@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jre@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