Am Mittwoch, den 05.11.2014, 08:21 +0100 schrieb Sascha Hauer: > On Tue, Nov 04, 2014 at 10:42:48AM +0100, Lucas Stach wrote: > > A proper GUID is needed to namespace all sorts of > > things, most prominently persistent variables. > > > > Signed-off-by: Lucas Stach <l.stach@xxxxxxxxxxxxxx> > > --- > > include/efi.h | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/include/efi.h b/include/efi.h > > index 70fe254dbafa..507115881b55 100644 > > --- a/include/efi.h > > +++ b/include/efi.h > > @@ -468,6 +468,10 @@ extern efi_runtime_services_t *RT; > > #define EFI_VLANCONFIGDXE_INF_GUID \ > > EFI_GUID(0xe4f61863, 0xfe2c, 0x4b56, 0xa8, 0xf4, 0x08, 0x51, 0x9b, 0xc4, 0x39, 0xdf) > > > > +/* barebox specific GUIDs */ > > +#define EFI_BAREBOX_VENDOR_GUID \ > > + EFI_GUID(0x5b91f69c, 0x8b88, 0x4a2b, 0x92, 0x69, 0x5f, 0x1d, 0x80, 0x2b, 0x51, 0x75) > > Can we just make up our own? > Yes we do. I've looked into this a while and it seems that every EFI vendor/user is expected to just make up his own GUIDs. There is no central registry or something except for the GUIDs that are standardized in the EFI spec. The expectation here seems to be that GUIDs carry enough entropy to not run into any collision problems. Regards, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
