mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/9] soc: imx8mp: Soc ID is 128bit
Date: Fri, 14 Nov 2025 21:08:44 +0100	[thread overview]
Message-ID: <aReMTCIwWptYn8HH@pengutronix.de> (raw)
In-Reply-To: <20251114162213.tweck3zgcgot3t6t@pengutronix.de>

On Fri, Nov 14, 2025 at 05:22:13PM +0100, Marco Felsch wrote:
> Hi Sascha,
> 
> On 25-11-13, Sascha Hauer wrote:
> > On i.MX8MP the SoC ID has 128 bits instead of 64 bits as on other i.MX8M
> > SoCs. Read the remaining 64 bits which so far haven't been included in
> > the SoC ID.
> 
> Linux fixed this as well in a non-backward compatible way. Don't get me
> wrong this is the correct fix and we should fix it, but this change will
> certainly influence in-field systems badly which rely on the the current
> behavior e.g. to set the `systemd.machine` or which make use of the UID
> to construct a hostname which is later on passed to the kernel cmdline
> via `systemd.hostname`.
> 
> These systems now need to revert this change to archieve the same system
> behavior. Can we add a Kconfig option or some function which can set the
> soc_uid limit to keep these systems working.

Yes, I've written about it in the cover letter.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-11-14 20:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  9:34 [PATCH 0/9] Unify SoC UID and machine hashable data Sascha Hauer
2025-11-13  9:34 ` [PATCH 1/9] introduce SoC UID Sascha Hauer
2025-11-13  9:34 ` [PATCH 2/9] soc: imx8mp: Soc ID is 128bit Sascha Hauer
2025-11-14 16:22   ` Marco Felsch
2025-11-14 20:08     ` Sascha Hauer [this message]
2025-11-13  9:34 ` [PATCH 3/9] ARM: i.MX6: print leading zero for SoC ID Sascha Hauer
2025-11-13  9:34 ` [PATCH 4/9] nvmem: bsec: call barebox_set_soc_uid() Sascha Hauer
2025-11-13  9:34 ` [PATCH 5/9] nvmem: imx-ocotp-ele: " Sascha Hauer
2025-11-13  9:34 ` [PATCH 6/9] nvmem: ocotp: Fix SoC ID reading for i.MX8MP Sascha Hauer
2025-11-13  9:34 ` [PATCH 7/9] nvmem: imx-ocotp: call barebox_set_soc_uid() Sascha Hauer
2025-11-13  9:34 ` [PATCH 8/9] soc: imx8m: register SoC UID Sascha Hauer
2025-11-13  9:34 ` [PATCH 9/9] Documentation: migration: add i.MX8MP SoC UID change note Sascha Hauer

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=aReMTCIwWptYn8HH@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@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