From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: u-boot@lists.denx.de
Subject: RFC: Partition type GUID for U-Boot environment
Date: Tue, 17 Nov 2020 11:05:36 +0100 [thread overview]
Message-ID: <718cf749-9c73-12cd-c15c-5e794f1749b7@prevas.dk> (raw)
Hi,
Would it make sense to choose a canonical "Partition type GUID" [1] for
partitions used to store a U-Boot environment?
The partition type is mostly informational, but I'm thinking it might
make sense to have some canonical thing to put into an image definition
rather than having the tool use something random or a default which
would often be "Linux filesystem data".
If so, I propose 3de21764-95bd-54bd-a5c3-4abe786f38a8 , which is from
https://www.uuidtools.com/v5 with a namespace of
25cbcde0-8642-47c6-a298-1a3a57cd256b (randomly generated just now, but
should be used for future v5 uuids within U-Boot context [2]) and name
"U-Boot environment" (sans quotes).
[1] https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs
[2]
https://en.wikipedia.org/wiki/Universally_unique_identifier#Versions_3_and_5_(namespace_name-based)
Rasmus
next reply other threads:[~2020-11-17 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 10:05 Rasmus Villemoes [this message]
2020-11-17 12:21 ` RFC: Partition type GUID for U-Boot environment Marcin Juszkiewicz
2020-11-17 12:59 ` Rasmus Villemoes
2020-11-17 18:27 ` Tom Rini
2020-11-20 8:59 ` Rasmus Villemoes
2020-11-20 10:45 ` [PATCH 0/3] add partition " Rasmus Villemoes
2020-11-20 10:45 ` [PATCH 1/3] lib/uuid.c: change prototype of uuid_guid_get_str() Rasmus Villemoes
2021-01-18 13:00 ` Tom Rini
2020-11-20 10:45 ` [PATCH 2/3] doc/README.gpt: define partition type GUID for U-Boot environment Rasmus Villemoes
2021-01-18 13:00 ` Tom Rini
2020-11-20 10:45 ` [PATCH 3/3] doc/README.gpt: reflow partition type GUID table Rasmus Villemoes
2021-01-18 13:00 ` Tom Rini
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=718cf749-9c73-12cd-c15c-5e794f1749b7@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.