From: "Zimmer, Vincent" <vincent.zimmer@intel.com>
To: "Shah, Tapan" <tapandshah@hpe.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Spottswood, Jason" <jason.spottswood@hpe.com>
Subject: Re: OSRecovery boot options
Date: Wed, 18 Oct 2017 22:57:52 +0000 [thread overview]
Message-ID: <76DE84138CBE89489874B70B432D8F9BAAB74BCC@ORSMSX105.amr.corp.intel.com> (raw)
In-Reply-To: <CS1PR84MB0024CA8EAB4AFD48435CCE43D44D0@CS1PR84MB0024.NAMPRD84.PROD.OUTLOOK.COM>
For #1.
Typically the OS. The platform already has its own PlatformRecovery.
For #2
There's a prototype available to UEFI members that was used to vet some of the changes during UEFI 2.7 deliberations at https://github.com/UEFI/uefiproto/tree/master/OsRecovery
You can request access as a UEFI member to the repo if interested near-term. This needs to move to EDKII staging since the 2.7 specification is now public, though.
Vincent
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Shah, Tapan
Sent: Wednesday, October 18, 2017 1:52 PM
To: edk2-devel@lists.01.org
Cc: Spottswood, Jason <jason.spottswood@hpe.com>
Subject: [edk2] OSRecovery boot options
Hi All,
I am looking at EDK2 implementation for OS Recovery boot options but could not find a code in EDK2 which handles OSRecovery#### option creation and a code to parse OSRecoveryOrder variable and launch OS Recovery boot options.
Questions:
1. Who is responsible to create OSRecovery#### boot options and OSRecoveryOrder variable? Is UEFI platform owner or OS vendor responsible to create?
2. Is there an existing BDS implementation out there to manage/launch OS Recovery boot options?
Thanks,
Tapan
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-10-18 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:51 OSRecovery boot options Shah, Tapan
2017-10-18 22:57 ` Zimmer, Vincent [this message]
2017-10-18 23:36 ` Shah, Tapan
2017-10-18 23:38 ` Zimmer, Vincent
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=76DE84138CBE89489874B70B432D8F9BAAB74BCC@ORSMSX105.amr.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