From: "Zeng, Star" <star.zeng@intel.com>
To: Marvin H?user <Marvin.Haeuser@outlook.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Dong, Eric" <eric.dong@intel.com>,
"Ni, Ruiyu" <ruiyu.ni@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: Proposition of a BmEnumerateBootOptions() hook.
Date: Tue, 15 May 2018 05:40:18 +0000 [thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103BAEC287@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <VI1PR0801MB17909D6922DF3A15A7A706A8809C0@VI1PR0801MB1790.eurprd08.prod.outlook.com>
Cc Ray.
Thanks,
Star
From: Marvin H?user [mailto:Marvin.Haeuser@outlook.com]
Sent: Tuesday, May 15, 2018 3:00 AM
To: edk2-devel@lists.01.org
Cc: Zeng, Star <star.zeng@intel.com>; Dong, Eric <eric.dong@intel.com>
Subject: Proposition of a BmEnumerateBootOptions() hook.
Hey Star, Eric and everyone else,
I have seen that some platforms add a Boot Option for the UEFI Shell in "PlatformBootManagerBeforeConsole()", which is called as part of the regular boot flow.
This is surely beneficial for development platforms that are supposed to boot to UEFI Shell by default when no other option has been registered, however for retail platforms it usually makes more sense to show the UEFI Boot Menu, which renders adding the Shell Boot Option as part of the regular boot flow obsolete and just adds up to the boot time. Meanwhile, there is a function in the UefiBootManagerLib, "BmEnumerateBootOptions()", which is called prior to entering the Boot Menu and, in my opinion, would be the perfect place to introduce another PlatformBootManagerLib hook, which retrieves platform-specific boot options, such as an UEFI Shell or other utilities like a Memory Test application.
If you have a few spare minutes, I'll be happy for feedback.
Thanks in advance for your time.
Best regards,
Marvin
next prev parent reply other threads:[~2018-05-15 5:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 19:00 Proposition of a BmEnumerateBootOptions() hook Marvin H?user
2018-05-15 5:40 ` Zeng, Star [this message]
2018-05-15 8:22 ` Laszlo Ersek
2018-05-15 13:02 ` Marvin Häuser
2018-05-15 13:52 ` Laszlo Ersek
2018-05-15 14:49 ` Gabriel L. Somlo
2018-05-15 15:38 ` Marvin Häuser
2018-05-15 16:12 ` Laszlo Ersek
2018-05-15 17:14 ` Marvin Häuser
2018-05-15 18:31 ` Laszlo Ersek
2018-05-17 7:57 ` Ni, Ruiyu
2018-05-17 11:43 ` Marvin Häuser
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=0C09AFA07DD0434D9E2A0C6AEB0483103BAEC287@shsmsx102.ccr.corp.intel.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