From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Bi, Dandan" <dandan.bi@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [patch 2/2] MdeModulePkg/BdsDxe: Report Status Code when booting from BootOrder list
Date: Mon, 26 Jun 2017 06:18:05 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5B9A46A6@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1498456237-71796-3-git-send-email-dandan.bi@intel.com>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
Thanks/Ray
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Dandan Bi
> Sent: Monday, June 26, 2017 1:51 PM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>
> Subject: [edk2] [patch 2/2] MdeModulePkg/BdsDxe: Report Status Code
> when booting from BootOrder list
>
> Report Status Code to indicate BDS starts attempting booting from the UEFI
> BootOrder list.
>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Dandan Bi <dandan.bi@intel.com>
> ---
> MdeModulePkg/Universal/BdsDxe/BdsEntry.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/MdeModulePkg/Universal/BdsDxe/BdsEntry.c
> b/MdeModulePkg/Universal/BdsDxe/BdsEntry.c
> index b5e6ef6..ac5f908 100644
> --- a/MdeModulePkg/Universal/BdsDxe/BdsEntry.c
> +++ b/MdeModulePkg/Universal/BdsDxe/BdsEntry.c
> @@ -3,11 +3,11 @@
> When this module was dispatched by DxeCore, gEfiBdsArchProtocolGuid
> will be installed
> which contains interface of BdsEntry.
> After DxeCore finish DXE phase, gEfiBdsArchProtocolGuid->BdsEntry will be
> invoked
> to enter BDS phase.
>
> -Copyright (c) 2004 - 2016, Intel Corporation. All rights reserved.<BR>
> +Copyright (c) 2004 - 2017, Intel Corporation. All rights reserved.<BR>
> (C) Copyright 2016 Hewlett Packard Enterprise Development LP<BR>
> (C) Copyright 2015 Hewlett-Packard Development Company, L.P.<BR> This
> program and the accompanying materials are licensed and made available
> under the terms and conditions of the BSD License which accompanies this
> distribution. The full text of the license may be found at @@ -368,10 +368,15
> @@ BootBootOptions (
> )
> {
> UINTN Index;
>
> //
> + // Report Status Code to indicate BDS starts attempting booting from the
> UEFI BootOrder list.
> + //
> + REPORT_STATUS_CODE (EFI_PROGRESS_CODE,
> (EFI_SOFTWARE_DXE_BS_DRIVER |
> + EFI_SW_DXE_BS_PC_ATTEMPT_BOOT_ORDER_EVENT));
> +
> + //
> // Attempt boot each boot option
> //
> for (Index = 0; Index < BootOptionCount; Index++) {
> //
> // According to EFI Specification, if a load option is not marked
> --
> 1.9.5.msysgit.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-06-26 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 5:50 [patch 0/2] Add new Status Code "EFI_SW_DXE_BS_PC_ATTEMPT_BOOT_ORDER_EVENT" Dandan Bi
2017-06-26 5:50 ` [patch 1/2] MdePkg/PiStatusCode: Add new Status Code for BDS when attempting BootOrder Dandan Bi
2017-06-26 6:18 ` Ni, Ruiyu
2017-06-26 7:45 ` Wang, Sunny (HPS SW)
2017-06-26 5:50 ` [patch 2/2] MdeModulePkg/BdsDxe: Report Status Code when booting from BootOrder list Dandan Bi
2017-06-26 6:18 ` Ni, Ruiyu [this message]
2017-06-26 7:46 ` Wang, Sunny (HPS SW)
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=734D49CCEBEEF84792F5B80ED585239D5B9A46A6@SHSMSX104.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