From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: "Yanhong Wang" <yanhong.wang@starfivetech.com>,
"Simon Glass" <sjg@chromium.org>, "Andrew Davis" <afd@ti.com>,
"Alper Nebi Yasak" <alpernebiyasak@gmail.com>,
"Stefan Roese" <sr@denx.de>,
"Andre Przywara" <andre.przywara@arm.com>,
"Jérôme Carretero" <cJ-uboot@zougloub.eu>,
"Harald Seiler" <hws@denx.de>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 1/1] spl: allow loading via partition type GUID
Date: Thu, 16 Feb 2023 12:01:42 -0500 [thread overview]
Message-ID: <Y+5hdpP54Y54OU6x@bill-the-cat> (raw)
In-Reply-To: <20230216152956.130038-1-heinrich.schuchardt@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Thu, Feb 16, 2023 at 04:29:56PM +0100, Heinrich Schuchardt wrote:
> Some boards provide main U-Boot as a dedicated partition to SPL.
> Currently we can define either a fixed partition number or an MBR
> partition type to define which partition is to be used.
>
> Partition numbers tend to conflict with established partitioning schemes
> of Linux distros. MBR partitioning is more and more replaced by GPT
> partitioning.
>
> Allow defining a partition type GUID identifying the partition to load
> main U-Boot from.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
[snip]
> +config SYS_MMCSD_RAW_MODE_U_BOOT_GPT_PARTITION_TYPE
> + string "GPT Partition Type on the MMC to load U-Boot from"
> + depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_GPT_PARTITION_TYPE
> + default d2f002f8-e4e7-4269-b8ac-3bb6fabeaff6
Is there a reason to use any other GUID value here? If not, just define,
or use it directly with a comment. If there is a reason for other
values to be used:
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-02-16 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:29 [PATCH v2 1/1] spl: allow loading via partition type GUID Heinrich Schuchardt
2023-02-16 17:01 ` Tom Rini [this message]
2023-02-16 17:19 ` Heinrich Schuchardt
2023-02-16 17:22 ` Tom Rini
2023-02-16 20:17 ` Simon Glass
2023-02-16 21:31 ` Heinrich Schuchardt
2023-02-17 2:55 ` Simon Glass
2023-02-17 6:55 ` Heinrich Schuchardt
2023-02-17 10:34 ` Mark Kettenis
2023-02-17 11:06 ` Heinrich Schuchardt
2023-02-17 15:03 ` Tom Rini
2023-02-19 19:52 ` Mark Kettenis
2023-02-19 21:21 ` Heinrich Schuchardt
2023-02-21 19:41 ` Simon Glass
2023-02-26 14:56 ` Simon Glass
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=Y+5hdpP54Y54OU6x@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=alpernebiyasak@gmail.com \
--cc=andre.przywara@arm.com \
--cc=cJ-uboot@zougloub.eu \
--cc=heinrich.schuchardt@canonical.com \
--cc=hws@denx.de \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=yanhong.wang@starfivetech.com \
/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