From: "Arend van Spriel" <arend@broadcom.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: linux-efi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: access efi variables
Date: Fri, 13 Sep 2013 18:39:26 +0200 [thread overview]
Message-ID: <52333FBE.2080206@broadcom.com> (raw)
In-Reply-To: <52333139.6020203@broadcom.com>
On 09/13/2013 05:37 PM, Arend van Spriel wrote:
> I need to obtain a uefi variable so I went looking at the API in
> include/linux/efi.h. I found the following definition:
>
> /*
> * The maximum size of VariableName + Data = 1024
> * Therefore, it's reasonable to save that much
> * space in each part of the structure,
> * and we use a page for reading/writing.
> */
>
> struct efi_variable {
> efi_char16_t VariableName[1024/sizeof(efi_char16_t)];
> efi_guid_t VendorGuid;
> unsigned long DataSize;
> __u8 Data[1024];
> efi_status_t Status;
> __u32 Attributes;
> } __attribute__((packed));
>
> But according to the specs the variable I need to obtain is 2k bytes.
Maybe clarify that "the specs" is basically the feature information I
received internally here.
> Should I expect trouble :-p
>
> Regards,
> Arend
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-09-13 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:37 access efi variables Arend van Spriel
2013-09-13 16:39 ` Arend van Spriel [this message]
[not found] ` <52333139.6020203-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-09-13 22:37 ` H. Peter Anvin
[not found] ` <5233939B.3020401-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-09-14 17:01 ` Arend van Spriel
[not found] ` <5234965F.3050404-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-09-17 15:46 ` Matt Fleming
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=52333FBE.2080206@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.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;
as well as URLs for NNTP newsgroup(s).