From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.100; helo=mga07.intel.com; envelope-from=vincent.zimmer@intel.com; receiver=edk2-devel@lists.01.org Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 83A7A202E616C for ; Wed, 18 Oct 2017 16:35:01 -0700 (PDT) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga105.jf.intel.com with ESMTP; 18 Oct 2017 16:38:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,398,1503385200"; d="scan'208";a="164274874" Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by fmsmga005.fm.intel.com with ESMTP; 18 Oct 2017 16:38:38 -0700 Received: from orsmsx105.amr.corp.intel.com ([169.254.2.105]) by ORSMSX108.amr.corp.intel.com ([169.254.2.242]) with mapi id 14.03.0319.002; Wed, 18 Oct 2017 16:38:38 -0700 From: "Zimmer, Vincent" To: "Shah, Tapan" , "edk2-devel@lists.01.org" CC: "Spottswood, Jason" Thread-Topic: OSRecovery boot options Thread-Index: AdNIUbB0sCR/KD65SGKAki05wDQTogADiObwAAJ0qxAAAB3cgA== Date: Wed, 18 Oct 2017 23:38:38 +0000 Message-ID: <76DE84138CBE89489874B70B432D8F9BAAB74DE3@ORSMSX105.amr.corp.intel.com> References: <76DE84138CBE89489874B70B432D8F9BAAB74BCC@ORSMSX105.amr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDQ4M2IzNmUtNGZlZC00MTU0LWE1MGEtNmI3NTA3ZjE0MzIxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlBRRUYrbnJWcUNQSjdBZUVwRVdwS0pJVE5Pb1BtYXE4XC9YT0RKTHM4MUJzPSJ9 x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Subject: Re: OSRecovery boot options X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 23:35:01 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable #1 Since there isn't an open source example, I'm not aware of any OS's consumi= ng this. #2 Let me know your github ID and I'll grant you access to the repo. Vincent -----Original Message----- From: Shah, Tapan [mailto:tapandshah@hpe.com]=20 Sent: Wednesday, October 18, 2017 4:37 PM To: Zimmer, Vincent ; edk2-devel@lists.01.org Cc: Spottswood, Jason Subject: RE: OSRecovery boot options Thanks Vincent! # 1: Are you aware of any specific OS revision that already has this suppor= t added? #2: Are you sure that's the correct URL? I keep getting this error message:= 404 - This is not the web page you are looking for. Thanks, Tapan -----Original Message----- From: Zimmer, Vincent [mailto:vincent.zimmer@intel.com]=20 Sent: Wednesday, October 18, 2017 5:58 PM To: Shah, Tapan ; edk2-devel@lists.01.org Cc: Spottswood, Jason Subject: RE: OSRecovery boot options 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/uefipr= oto/tree/master/OsRecovery=20 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 p= ublic, 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 Subject: [edk2] OSRecovery boot options Hi All, I am looking at EDK2 implementation for OS Recovery boot options but cou= ld not find a code in EDK2 which handles OSRecovery#### option creation and= a code to parse OSRecoveryOrder variable and launch OS Recovery boot optio= ns. Questions: 1. Who is responsible to create OSRecovery#### boot options and OSRec= overyOrder variable? Is UEFI platform owner or OS vendor responsible to cre= ate? 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