The partition type GUID was generated randomly. Having a defined GUID should reduce the risk of collisions in the future. A dedicated GUID could also allow us to implement a fallback in case no state backend property is defined. This could then look for a GPT partition with this partition type GUID and use that as the backend. dt-utils could do the same in userspace. This would be similar to [1]. [1] https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ Signed-off-by: Bastian Krause <bst@xxxxxxxxxxxxxx> --- Documentation/user/state.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/user/state.rst b/Documentation/user/state.rst index 54aa396257..a0e27d4fe8 100644 --- a/Documentation/user/state.rst +++ b/Documentation/user/state.rst @@ -579,6 +579,9 @@ content, its backend-type and *state* variable layout. }; }; +If the *state* variable set is set to be located in a GPT partition, use +``4778ed65-bf42-45fa-9c5b-287a1dc4aab1`` as the partition type GUID. + SRAM #### -- 2.30.0 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
