Branch: refs/heads/master
  Home:   https://github.com/tianocore/edk2
  Commit: 5de2a54b2cfdb9cb3a1a564c85e99aa6b06b5dba
      
https://github.com/tianocore/edk2/commit/5de2a54b2cfdb9cb3a1a564c85e99aa6b06b5dba
  Author: Pierre Gondois <pierre.gond...@arm.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    M ArmPkg/ArmPkg.dec
    M ArmPkg/Library/PlatformBootManagerLib/PlatformBm.c
    M ArmPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf

  Log Message:
  -----------
  ArmPkg/PlatformBootManagerLib: Add path to boot UEFI Shell over UiApp

The UEFI Shell is a non-active boot option, at the opposite of UiApp.
If no valid boot option is found, UiApp is selected. UiApp requires a
human interaction. When installing a new EDKII image in CIs or when
scripting is required, this is problematic.

If no valid boot option is discovered, add a path to directly go to
the UEFI Shell where the startup.nsh script is automatically executed.
The UEFI Shell is launched after connecting possible devices, but
before the reset that is meant to automatically make them visible.

The new PcdUefiShellDefaultBootEnable must be set to TRUE to enable
this behaviour. The Pcd is set to false by default.

Signed-off-by: Pierre Gondois <pierre.gond...@arm.com>
Tested-by: Patrik Berglund <patrik.bergl...@arm.com>


  Commit: 8d59bbf47ea09bbf599bcc1da5e9923a456c0a52
      
https://github.com/tianocore/edk2/commit/8d59bbf47ea09bbf599bcc1da5e9923a456c0a52
  Author: Oliver Steffen <ostef...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    A OvmfPkg/Include/Dsc/OvmfPkg.dsc.inc
    M OvmfPkg/OvmfPkgIa32.dsc
    M OvmfPkg/OvmfPkgIa32X64.dsc
    M OvmfPkg/OvmfPkgX64.dsc
    M OvmfPkg/OvmfXen.dsc

  Log Message:
  -----------
  OvmfPkg: allow setting Firmware Version from build command line

Initialize gEfiMdeModulePkgTokenSpaceGuid.PcdFirmwareVersionString with
with the value of the variable "FIRMWARE_VER", if is is defined. Applies
to all flavors of OvmfPkg.

This behavior is already implemented in ArmVirtXen.dsc. It allows
specifying the firmware version string on the build command line with
-D FIRMARE_VER=...

Introduce a common include file to be used in the .dsc files for the
different OVMF flavors, and add the changes there.  (ArmVirtPkg already
has such a file).

Signed-off-by: Oliver Steffen <ostef...@redhat.com>


  Commit: a818a873e5381726c16470fa452d76fbbd5b200e
      
https://github.com/tianocore/edk2/commit/a818a873e5381726c16470fa452d76fbbd5b200e
  Author: Oliver Steffen <ostef...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    M ArmVirtPkg/ArmVirt.dsc.inc
    M ArmVirtPkg/ArmVirtXen.dsc

  Log Message:
  -----------
  ArmVirtPkg: allow setting Firmware Version from build command line

ArmVirtXen.dsc initializes
gEfiMdeModulePkgTokenSpaceGuid.PcdFirmwareVersionString with with the
value of the variable "FIRMWARE_VER".

Move that functionality to ArmVirt.dsc.inc to make it available to all
ArmVirt packages, and make it conditional: only set the PCD string if
FIRMWARE_VER is actually defined.

This allows specifying the firmware version string on the build command
line with -D FIRMARE_VER=...

Signed-off-by: Oliver Steffen <ostef...@redhat.com>
Reviewed-by: Sami Mujawar <sami.muja...@arm.com>


  Commit: 92da8a154fc0a1b0f42ab0ec4aee7dd2933f1a0a
      
https://github.com/tianocore/edk2/commit/92da8a154fc0a1b0f42ab0ec4aee7dd2933f1a0a
  Author: Gerd Hoffmann <kra...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    M OvmfPkg/CloudHv/CloudHvX64.dsc
    M OvmfPkg/IntelTdx/IntelTdxX64.dsc
    M OvmfPkg/Library/NvVarsFileLib/NvVarsFileLib.c
    M OvmfPkg/Library/NvVarsFileLib/NvVarsFileLib.inf
    M OvmfPkg/Microvm/MicrovmX64.dsc
    M OvmfPkg/OvmfPkg.dec
    M OvmfPkg/OvmfPkgIa32.dsc
    M OvmfPkg/OvmfPkgIa32X64.dsc
    M OvmfPkg/OvmfPkgX64.dsc
    M OvmfPkg/PlatformPei/Platform.c
    M OvmfPkg/PlatformPei/PlatformPei.inf

  Log Message:
  -----------
  OvmfPkg: replace SECURE_BOOT_FEATURE_ENABLED with PcdSecureBootSupported

Drop the '-D SECURE_BOOT_FEATURE_ENABLED' compile time option,
use a new FeaturePcd instead.

Signed-off-by: Gerd Hoffmann <kra...@redhat.com>


  Commit: 1694b0051138dc121740e47896d165b8b12382c6
      
https://github.com/tianocore/edk2/commit/1694b0051138dc121740e47896d165b8b12382c6
  Author: Gerd Hoffmann <kra...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    A OvmfPkg/Include/IndustryStandard/VirtioSerial.h

  Log Message:
  -----------
  OvmfPkg: add IndustryStandard/VirtioSerial.h

Add header files with structs and defines for the virtio serial device.

The virtio serial device also known as virtio console device because
initially it had only support for a single tty, intended to be used as
console.  Support for multiple streams and named data ports has been
added later on.

https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html#x1-2900003

Signed-off-by: Gerd Hoffmann <kra...@redhat.com>


  Commit: 4d1452c59979b9fcc762db692688b5b3b6573106
      
https://github.com/tianocore/edk2/commit/4d1452c59979b9fcc762db692688b5b3b6573106
  Author: Gerd Hoffmann <kra...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    A OvmfPkg/VirtioSerialDxe/VirtioSerial.c
    A OvmfPkg/VirtioSerialDxe/VirtioSerial.h
    A OvmfPkg/VirtioSerialDxe/VirtioSerial.inf
    A OvmfPkg/VirtioSerialDxe/VirtioSerialPort.c
    A OvmfPkg/VirtioSerialDxe/VirtioSerialRing.c

  Log Message:
  -----------
  OvmfPkg/VirtioSerialDxe: add driver

Add a driver for the virtio serial device.

The virtio serial device also known as virtio console device because
initially it had only support for a single tty, intended to be used as
console.  Support for multiple streams and named data ports has been
added later on.

The driver supports tty ports only, they are registered as SerialIo
UART in the system.

Named ports are detected and logged, but not exposed as devices.  They
are usually used by guest agents to communicate with the host.  It's not
clear whenever it makes sense for the firmware to run such agents and if
so which efi protocol could be to expose the ports.  So leaving that for
another day.

Signed-off-by: Gerd Hoffmann <kra...@redhat.com>


  Commit: c6c43620513e6a3411e68567f10661ee17d02dd8
      
https://github.com/tianocore/edk2/commit/c6c43620513e6a3411e68567f10661ee17d02dd8
  Author: Gerd Hoffmann <kra...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    M OvmfPkg/Microvm/MicrovmX64.dsc
    M OvmfPkg/Microvm/MicrovmX64.fdf
    M OvmfPkg/OvmfPkgIa32.dsc
    M OvmfPkg/OvmfPkgIa32.fdf
    M OvmfPkg/OvmfPkgIa32X64.dsc
    M OvmfPkg/OvmfPkgIa32X64.fdf
    M OvmfPkg/OvmfPkgX64.dsc
    M OvmfPkg/OvmfPkgX64.fdf

  Log Message:
  -----------
  OvmfPkg/VirtioSerialDxe: wire up in OvmfPkg*

Add the driver to the ovmf builds.

Signed-off-by: Gerd Hoffmann <kra...@redhat.com>


  Commit: 4b02045f86d6aac8a617bf3f65f9cb2146630ce3
      
https://github.com/tianocore/edk2/commit/4b02045f86d6aac8a617bf3f65f9cb2146630ce3
  Author: Gerd Hoffmann <kra...@redhat.com>
  Date:   2023-05-04 (Thu, 04 May 2023)

  Changed paths:
    M OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c

  Log Message:
  -----------
  OvmfPkg/PlatformBootManagerLib: setup virtio serial console

In case a virtio-serial device is present in the system register the
first serial port as console.

Signed-off-by: Gerd Hoffmann <kra...@redhat.com>


Compare: https://github.com/tianocore/edk2/compare/d6b42ed7ed1b...4b02045f86d6


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

Reply via email to