From: "Arend van Spriel" <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: access efi variables
Date: Sat, 14 Sep 2013 19:01:19 +0200 [thread overview]
Message-ID: <5234965F.3050404@broadcom.com> (raw)
In-Reply-To: <5233939B.3020401-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
On 09/14/13 00:37, H. Peter Anvin wrote:
> On 09/13/2013 08:37 AM, 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:
>>
>> But according to the specs the variable I need to obtain is 2k bytes.
>> Should I expect trouble :-p
>>
>
> efivarfs doesn't have those limitations.
Thanks, Peter
Looking into efivarfs it seems to use the functions that I looked at in
efi.h so I guess I am misinterpreting the 1024 bytes limitation in the
comment (either that or you are mistaken ;-) ). I need to access the
variable from within a device driver so using efivarfs does not feel
like the way to go here.
Regards,
Arend
WARNING: multiple messages have this Message-ID (diff)
From: "Arend van Spriel" <arend@broadcom.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Matt Fleming" <matt.fleming@intel.com>,
linux-efi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: access efi variables
Date: Sat, 14 Sep 2013 19:01:19 +0200 [thread overview]
Message-ID: <5234965F.3050404@broadcom.com> (raw)
In-Reply-To: <5233939B.3020401@zytor.com>
On 09/14/13 00:37, H. Peter Anvin wrote:
> On 09/13/2013 08:37 AM, 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:
>>
>> But according to the specs the variable I need to obtain is 2k bytes.
>> Should I expect trouble :-p
>>
>
> efivarfs doesn't have those limitations.
Thanks, Peter
Looking into efivarfs it seems to use the functions that I looked at in
efi.h so I guess I am misinterpreting the 1024 bytes limitation in the
comment (either that or you are mistaken ;-) ). I need to access the
variable from within a device driver so using efivarfs does not feel
like the way to go here.
Regards,
Arend
next prev parent reply other threads:[~2013-09-14 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:37 access efi variables Arend van Spriel
2013-09-13 15:37 ` Arend van Spriel
2013-09-13 16:39 ` Arend van Spriel
[not found] ` <52333139.6020203-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-09-13 22:37 ` H. Peter Anvin
2013-09-13 22:37 ` H. Peter Anvin
[not found] ` <5233939B.3020401-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-09-14 17:01 ` Arend van Spriel [this message]
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
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=5234965F.3050404@broadcom.com \
--to=arend-dy08kvg/lbpwk0htik3j/w@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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.