mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Fabian Pflug <f.pflug@pengutronix.de>
To: Jonas Rebmann <jre@pengutronix.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	 BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/2] Add additional globalvar for soc_uid
Date: Tue, 14 Apr 2026 13:10:40 +0200	[thread overview]
Message-ID: <1bbc8d371d0aacf39039d4f3f2c38c657ba7915a.camel@pengutronix.de> (raw)
In-Reply-To: <012c0d74-7a91-4294-9d7d-06e87ed57b02@pengutronix.de>

Hey,

On Mon, 2026-04-13 at 10:21 +0200, Jonas Rebmann wrote:
> Hi Fabian,
> 
> On 2026-03-30 14:24, Fabian Pflug wrote:
> > The binary representation was used to compare against,
> 
> What was compared against soc_uid_bin? Or is it still?

It is still used to compare against, but now also exposed to userspace.

> 
> tlv_bind_soc_uid?
> 
> > but never exposed to userspace to query, as the exposed variables
> > could correlate with the value, but did not.
> 
> The exposed string representation is encoded in a manufacturer-specific
> manner, hence for use in scripting, soc_uid_bin should be accessible in
> a generic representation.
> 
> > For example on i.MX8MP the byte order was reversed in comparing
> > the return value of barebox_get_soc_uid_bin and $global.soc_uid.
> 
> This was discussed with regard to i.MX8MP, where the byte order of
> $global.soc_uid and linux' /sys/devices/soc0/serial_number is reversed
> compared to barebox_get_soc_uid_bin.
> 
> Regardless of whether the current value of barebox_get_soc_uid_bin is
> correct, barebox_get_soc_uid_bin should be used for scripting.

I can't follow you on this one. Scripting in my understanding means barebox commands on the commandline or in boot-
scripts for example.
barebox_get_soc_uid_bin is a C function and not available on the commandline.

Could you elaborate what you mean here?

Fabian

> 
> > Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
> > ---
> > Fabian Pflug (2):
> >        common: misc: add soc_uid_bin to globalvar
> >        i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID
> > 
> >   arch/arm/mach-imx/Kconfig | 11 +++--------
> >   common/misc.c             |  8 ++++++--
> >   2 files changed, 9 insertions(+), 10 deletions(-)
> > ---
> > base-commit: 1d386a53086d28a0c4eda138ae9408a418b97b7e
> > change-id: 20260330-v2026-03-0-topic-soc_bin_id-d12a84d7b1b5
> > 
> > Best regards,



      reply	other threads:[~2026-04-14 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 12:24 Fabian Pflug
2026-03-30 12:24 ` [PATCH 1/2] common: misc: add soc_uid_bin to globalvar Fabian Pflug
2026-04-13  8:21   ` Jonas Rebmann
2026-04-13  8:24   ` Ahmad Fatoum
2026-03-30 12:24 ` [PATCH 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID Fabian Pflug
2026-04-13  8:21   ` Jonas Rebmann
2026-04-14 11:04     ` Fabian Pflug
2026-04-13  8:21 ` [PATCH 0/2] Add additional globalvar for soc_uid Jonas Rebmann
2026-04-14 11:10   ` Fabian Pflug [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=1bbc8d371d0aacf39039d4f3f2c38c657ba7915a.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