From: Tom Rini <trini@konsulko.com>
To: "Kory Maincent (TI.com)" <kory.maincent@bootlin.com>
Cc: u-boot@lists.denx.de,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"Bajjuri, Praneeth" <praneeth@ti.com>,
Simon Glass <sjg@chromium.org>, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH 0/2] Add support for customizable find_distro_rootpart
Date: Fri, 31 Oct 2025 11:47:33 -0600 [thread overview]
Message-ID: <20251031174733.GE6688@bill-the-cat> (raw)
In-Reply-To: <20251031-feature_distro_rootpart-v1-0-4e7c465708e8@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Fri, Oct 31, 2025 at 05:36:02PM +0100, Kory Maincent (TI.com) wrote:
> Add a customizable find_distro_rootpart command to allow each board to
> define its own logic for locating the rootfs partition inside the
> config_distro_bootcmd logic.
>
> Convert am335x_evm board to this new find_distro_rootpart customizable
> environment variable to locate the rootfs partition dynamically, instead
> of finduuid which hardcodes the rootfs partition location (mmc 0:2).
>
> Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
> ---
> Kory Maincent (TI.com) (2):
> distro_bootcmd: Add support for customizable find_distro_rootpart
> include: configs: am335x_evm: Replace findduid with find_distro_rootpart
The first question here is, can we migrate these to standard boot
instead, or is that kind of functionality also missing there?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-31 17:47 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
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 ` Tom Rini [this message]
2025-10-31 18:11 ` [PATCH 0/2] Add support for customizable find_distro_rootpart 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=20251031174733.GE6688@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