public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Andrew Fish <afish@apple.com>, "David F." <df7729@gmail.com>
Cc: edk2-devel@lists.01.org
Subject: Re: Boot####, Key####
Date: Fri, 8 Sep 2017 00:12:11 +0200	[thread overview]
Message-ID: <ae4ff45b-f7c3-99dd-0c63-c33ffd3d0577@redhat.com> (raw)
In-Reply-To: <D30458DF-1FA6-412A-B522-2E9F400E25AA@apple.com>

On 09/07/17 22:32, Andrew Fish wrote:
> 
>> On Sep 7, 2017, at 1:01 PM, David F. <df7729@gmail.com> wrote:
>>
>> Hi,
>>
>> Implementing support for UEFI inside different OS environments, I
>> don't see anything in the spec about being able to find the various
>> Boot#### and Key#### values without trying 0-0xFFFF which is slow
>> (takes 10+ seconds).    What's the better way?
>>
> 
> Usually there is another variable that implies the Boot#### value that is in use, like BootOrder. 

There's also GetNextVariableName() -- iterating through, say, ~50
variables that all exist is likely faster than querying ~65500 that don't.

Laszlo


      reply	other threads:[~2017-09-07 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGRSmLunzkLoNGU6T6bGN9KGbTHyiZ3fBeVCi+xAgRnpNJZJpQ@mail.gmail.com>
2017-09-07 20:01 ` Boot####, Key#### David F.
2017-09-07 20:32   ` Andrew Fish
2017-09-07 22:12     ` Laszlo Ersek [this message]

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-list 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=ae4ff45b-f7c3-99dd-0c63-c33ffd3d0577@redhat.com \
    --to=devel@edk2.groups.io \
    /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