Re: [edk2] [PATCH 3/5] MdeModulePkg/UefiBootManagerLib: report EDKII_OS_LOADER_DETAIL status code

2017-11-23 Thread Ni, Ruiyu
Sent from a small-screen device 在 2017年11月24日，上午1:08，Laszlo Ersek > 写道： On 11/23/17 15:53, Ni, Ruiyu wrote: Comments below. -Original Message- From: Laszlo Ersek [mailto:ler...@redhat.com] Sent: Thursday, November 23, 2017 10:03 PM To: Ni,

Re: [edk2] [PATCH 3/5] MdeModulePkg/UefiBootManagerLib: report EDKII_OS_LOADER_DETAIL status code

2017-11-23 Thread Laszlo Ersek
On 11/23/17 15:53, Ni, Ruiyu wrote: > Comments below. > >> -Original Message- >> From: Laszlo Ersek [mailto:ler...@redhat.com] >> Sent: Thursday, November 23, 2017 10:03 PM >> To: Ni, Ruiyu ; edk2-devel-01 >> Cc: Ard Biesheuvel

Re: [edk2] [PATCH 3/5] MdeModulePkg/UefiBootManagerLib: report EDKII_OS_LOADER_DETAIL status code

2017-11-23 Thread Laszlo Ersek
Hello Ray, (CC Mark Doran for the last part of my email) On 11/23/17 06:21, Ni, Ruiyu wrote: > Laszlo, > When booting a boot option, UefiBootManagerBoot() sets a Boot variable > and saves to BootCurrent variable. > So all the details (except the EDKII_OS_LOADER_DETAIL.Status) can be

Re: [edk2] [PATCH 3/5] MdeModulePkg/UefiBootManagerLib: report EDKII_OS_LOADER_DETAIL status code

2017-11-22 Thread Ni, Ruiyu
Laszlo, When booting a boot option, UefiBootManagerBoot() sets a Boot variable and saves to BootCurrent variable. So all the details (except the EDKII_OS_LOADER_DETAIL.Status) can be retrieved from reading Boot variable. 4 more comments below. Thanks/Ray > -Original

[edk2] [PATCH 3/5] MdeModulePkg/UefiBootManagerLib: report EDKII_OS_LOADER_DETAIL status code

2017-11-22 Thread Laszlo Ersek
The EfiBootManagerBoot() function reports progress codes about LoadImage() preparation and failure, and StartImage() preparation and failure. These codes are flat (scalar) constants. Extend this by "broadcasting" the Boot option number, description, device path, and -- on load / start failure