From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 02/10] efi: add Barebox GUID
Date: Wed, 5 Nov 2014 08:21:32 +0100 [thread overview]
Message-ID: <20141105072132.GI30369@pengutronix.de> (raw)
In-Reply-To: <1415094176-26435-2-git-send-email-l.stach@pengutronix.de>
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@pengutronix.de>
> ---
> 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?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-11-05 7:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 9:42 [PATCH 01/10] efi: add proper reset hook Lucas Stach
2014-11-04 9:42 ` [PATCH 02/10] efi: add Barebox GUID Lucas Stach
2014-11-05 7:21 ` Sascha Hauer [this message]
2014-11-05 9:03 ` Lucas Stach
2014-11-04 9:42 ` [PATCH 03/10] fs: efivar: cosmetic changes Lucas Stach
2014-11-04 9:42 ` [PATCH 04/10] fs: efivar: switch to standard list implementation Lucas Stach
2014-11-04 9:42 ` [PATCH 05/10] fs: efivar: move variable discovery into probe Lucas Stach
2014-11-04 9:42 ` [PATCH 06/10] lib: add wchar strdup Lucas Stach
2014-11-04 9:42 ` [PATCH 07/10] fs: efivar: preserve more info in inode Lucas Stach
2014-11-04 9:42 ` [PATCH 08/10] fs: efivar: don't store attributes in file Lucas Stach
2014-11-04 9:42 ` [PATCH 09/10] fs: efivar: implement write support Lucas Stach
2014-11-04 9:42 ` [PATCH 10/10] efi: mount efivarfs by default if enabled Lucas Stach
2014-11-05 7:21 ` [PATCH 01/10] efi: add proper reset hook Sascha Hauer
2014-11-05 9:00 ` Lucas Stach
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=20141105072132.GI30369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.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