From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Leif Lindholm <leif@nuviainc.com>
Cc: devel@edk2.groups.io, Pete Batard <pete@akeo.ie>,
Andrei Warkentin <awarkentin@vmware.com>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH] ArmPkg/PlatformBootManagerLib: regenerate boot options on boot failure
Date: Wed, 17 Jun 2020 13:32:36 +0200 [thread overview]
Message-ID: <6a089a72-00cb-f8ce-16d7-50cefed9b47d@arm.com> (raw)
In-Reply-To: <20200617111235.GJ6739@vanye>
On 6/17/20 1:12 PM, Leif Lindholm wrote:
> On Tue, Jun 16, 2020 at 19:48:34 +0200, Ard Biesheuvel wrote:
>> One of the side effects of the recent changes to PlatformBootManagerLib
>> changes to avoid connecting all devices on every boot is that we no
>> longer default to network boot on a virgin boot, but end up in the
>> UiApp menu. At this point, the autogenerated boot options that we used
>> to rely on will be instantiated too,
>
> The passive voice is confusing me a bit here - who does the updating,
> and when specifically?
>
Originally, the ArmPkg PlatformBmLib would always refresh all boot
options, but now, only the UiApp does that upon entry, at which point
your sitting in the menu idly, and so automated network boot no longer
works.
next prev parent reply other threads:[~2020-06-17 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 17:48 [PATCH] ArmPkg/PlatformBootManagerLib: regenerate boot options on boot failure Ard Biesheuvel
2020-06-16 21:40 ` Samer El-Haj-Mahmoud
2020-06-17 11:12 ` Leif Lindholm
2020-06-17 11:32 ` Ard Biesheuvel [this message]
2020-06-17 12:16 ` Leif Lindholm
2020-06-17 12:28 ` Ard Biesheuvel
2020-06-17 12:40 ` Leif Lindholm
2020-06-17 12:59 ` Ard Biesheuvel
2020-06-17 14:35 ` Leif Lindholm
2020-06-17 18:30 ` Ard Biesheuvel
2020-06-17 13:44 ` [edk2-devel] " Laszlo Ersek
2020-06-17 16:21 ` Andrei Warkentin
2020-06-17 18:18 ` Ard Biesheuvel
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=6a089a72-00cb-f8ce-16d7-50cefed9b47d@arm.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