public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Simon Glass <sjg@chromium.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	"Bajjuri, Praneeth" <praneeth@ti.com>,
	Marek Vasut <marex@denx.de>
Subject: Re: [PATCH 1/2] distro_bootcmd: Add support for customizable find_distro_rootpart
Date: Mon, 3 Nov 2025 10:19:05 -0600	[thread overview]
Message-ID: <20251103161905.GP6688@bill-the-cat> (raw)
In-Reply-To: <20251103171630.4df1efdd@kmaincent-XPS-13-7390>

[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]

On Mon, Nov 03, 2025 at 05:16:30PM +0100, Kory Maincent wrote:
> On Mon, 3 Nov 2025 11:52:25 +0100
> Kory Maincent <kory.maincent@bootlin.com> wrote:
> 
> > On Sun, 2 Nov 2025 20:54:02 +0100
> > Simon Glass <sjg@chromium.org> wrote:
> > 
> > > Hi Kory,
> > > 
> > > On Fri, 31 Oct 2025 at 17:36, Kory Maincent (TI.com) <  
> > > kory.maincent@bootlin.com> wrote:
> > > >
> > > > Commit d0ba0ca45a49 ("distro_bootcmd: Set distro_bootpart_uuid for block
> > > > devices") added support for the distro_boot_part_uuid environment variable
> > > > to allow using PARTUUID in the kernel command line.
> > > >
> > > > However, the way it was written only supports the case where the boot    
> > > files  
> > > > and the rootfs are located in the same partition. There are many cases
> > > > where the boot partition and rootfs partition are separate.
> > > >
> > > > Add a customizable find_distro_rootpart command to allow each board to
> > > > define its own logic for locating the rootfs partition. This provides
> > > > flexibility for boards with custom partition layouts while maintaining
> > > > backward compatibility for the default case where boot and rootfs share
> > > > the same partition.
> > > >
> > > > Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
> > > > ---
> > > >  doc/develop/distro.rst          | 11 +++++++++++
> > > >  include/config_distro_bootcmd.h | 10 +++++++---
> > > >  2 files changed, 18 insertions(+), 3 deletions(-)
> > > >    
> > > 
> > > How about moving to standard boot and look at this there?  
> > 
> > Ok, I will take a look at it.
> 
> There is a custom nand boot target [1], and I have not any am335x board with
> nand memory to test it. I am afraid to break it during the update to bootstd.
> Not sure we can accept that. What do you think?
> 
> [1]https://elixir.bootlin.com/u-boot/v2025.10/source/include/configs/am335x_evm.h#L27

I think we can risk it. I'd even be OK with not migrating that portion
and letting anyone still using those platforms, with NAND only, to just
use a custom boot command instead as I have strong doubts there's anyone
doing anything other than that currently.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-03 16:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 16:36 [PATCH 0/2] Add support for customizable find_distro_rootpart Kory Maincent (TI.com)
2025-10-31 16:36 ` [PATCH 1/2] distro_bootcmd: " Kory Maincent (TI.com)
2025-11-02 19:54   ` Simon Glass
2025-11-03 10:52     ` Kory Maincent
2025-11-03 16:16       ` Kory Maincent
2025-11-03 16:19         ` Tom Rini [this message]
2025-11-04  9:29           ` Kory Maincent
2025-11-04 16:38             ` Tom Rini
2025-11-06 18:00               ` Kory Maincent
2025-11-06 18:23                 ` Tom Rini
2025-11-07  9:05                   ` Kory Maincent
2025-11-07  9:58                     ` Simon Glass
2025-11-07 15:51                     ` Tom Rini
2025-11-11 12:38                       ` Simon Glass
2025-10-31 16:36 ` [PATCH 2/2] include: configs: am335x_evm: Replace findduid with find_distro_rootpart Kory Maincent (TI.com)
2025-10-31 17:47 ` [PATCH 0/2] Add support for customizable find_distro_rootpart Tom Rini
2025-10-31 18:11   ` Kory Maincent

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=20251103161905.GP6688@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=kory.maincent@bootlin.com \
    --cc=marex@denx.de \
    --cc=praneeth@ti.com \
    --cc=sjg@chromium.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=u-boot@lists.denx.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