Branch: refs/heads/master
  Home:   https://github.com/tianocore/edk2
  Commit: 6bfd52247734c00d78b92d4636545b400e8bfa4a
      
https://github.com/tianocore/edk2/commit/6bfd52247734c00d78b92d4636545b400e8bfa4a
  Author: Luigi Leonardi <leona...@redhat.com>
  Date:   2025-03-13 (Thu, 13 Mar 2025)

  Changed paths:
    M ArmVirtPkg/ArmVirtQemu.dsc
    M ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc
    M ArmVirtPkg/ArmVirtQemuKernel.dsc

  Log Message:
  -----------
  ArmVirtPkg: add BootManagerMenuApp to dependencies.

Add BootManagerMenuApp to all OvmfPkg dependencies.

To make UiApp optional, switch from UiApp to BootManagerMenuApp
as default BootManagerMenu.

Signed-off-by: Luigi Leonardi <leona...@redhat.com>


  Commit: 4e19daa8520f498cb729b1de8d79b58a52fb223b
      
https://github.com/tianocore/edk2/commit/4e19daa8520f498cb729b1de8d79b58a52fb223b
  Author: Luigi Leonardi <leona...@redhat.com>
  Date:   2025-03-13 (Thu, 13 Mar 2025)

  Changed paths:
    M ArmVirtPkg/ArmVirtQemu.dsc
    M ArmVirtPkg/ArmVirtQemuKernel.dsc

  Log Message:
  -----------
  ArmVirtPkg: use BootManagerMenuApp as BootManagerMenu

This is part of the effort to enable/disable firmware configuration
(UiApp) from the QEMU CLI.

Because the UiApp can be disabled at runtime and it's currently the
default BootManagerMenu, change the default from UiApp to
BootManagerMenuApp.

Signed-off-by: Luigi Leonardi <leona...@redhat.com>


  Commit: ca278f14c2fd0d849dfcb80788c919b1f4079611
      
https://github.com/tianocore/edk2/commit/ca278f14c2fd0d849dfcb80788c919b1f4079611
  Author: Luigi Leonardi <leona...@redhat.com>
  Date:   2025-03-13 (Thu, 13 Mar 2025)

  Changed paths:
    M OvmfPkg/Library/PlatformBootManagerLibLight/PlatformBm.c

  Log Message:
  -----------
  OvmfPkg/PlatformBootManagerCommonLib: Disable autoboot for EFI Shell

Setting the LOAD_OPTION_CATEGORY_APP flag for EFI Shell prevents the
boot loader from using it as a fallback if all other entries fail to
boot.

With a boot manager menu available, it can be annoying to enter the EFI
Shell directly, because from the menu, the user can try to boot again
(e.g. temporary network problem) or enter the shell/firmware config only
if necessary.

Signed-off-by: Luigi Leonardi <leona...@redhat.com>


  Commit: dd5cce3e53960d205b53cf437aff196481d49d96
      
https://github.com/tianocore/edk2/commit/dd5cce3e53960d205b53cf437aff196481d49d96
  Author: Luigi Leonardi <leona...@redhat.com>
  Date:   2025-03-13 (Thu, 13 Mar 2025)

  Changed paths:
    M OvmfPkg/Library/PlatformBootManagerLibLight/PlatformBm.c
    M OvmfPkg/Library/PlatformBootManagerLibLight/PlatformBootManagerLib.inf

  Log Message:
  -----------
  OvmfPkg/PlatformBootManagerCommonLib: Set UiApp as an optional boot option

Introduce gUiAppFileGuid: it has the same value of UiApp guid defined in
the .inf file. This is used to register UiApp as a boot entry in the
BootManagerMenu.

This registration is done in PlatformBootManagerBeforeConsole because
it must be done before the hotkeys are registered. This is because
in a system with hotkeys still bound to UiApp, but with firmware disabled,
you can still boot into the latter by hitting ESC or F2 during boot.

UiApp can be enabled/disabled using fw_cfg option FirmwareSetupSupport

Signed-off-by: Luigi Leonardi <leona...@redhat.com>


Compare: https://github.com/tianocore/edk2/compare/f25e3d0d2c55...dd5cce3e5396

To unsubscribe from these emails, change your notification settings at 
https://github.com/tianocore/edk2/settings/notifications


_______________________________________________
edk2-commits mailing list
edk2-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-commits

Reply via email to