summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ArmVirtPkg: turn off debug logging for VirtioSerialDxeGerd Hoffmann2025-01-311-1/+4
| | | | | | | | | | When running the verbose builds on arm for development and testing it is quite convenient to use virtio serial to interact with the system because console and logging are separated then. Except that the virtio serial driver spams the debug log in that case. Set the debug level for the driver to zero to avoid that. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* Maintainers: update my email addressAndrei Warkentin2025-01-311-2/+2
| | | | | | I'm no longer at Intel. Signed-off-by: Andrei Warkentin <andyw@imsa.edu>
* BaseTools/Pccts: set C standardGerd Hoffmann2025-01-312-2/+2
| | | | | | | | The prehistoric code base doesn't build with ISO C23. Set the C standard to C11 (for both clang and gcc) so it continues to build with gcc 15 (which uses C23 by default). Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* MdePkg/BaseFdtLib: fix build with gcc 15Gerd Hoffmann2025-01-311-9/+13
| | | | | | | | gcc 15 switched to use the new ISO C23 standard by default. 'bool', 'true' and 'false' are keywords in C23, so do not try to define them. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* MdePkg: Add SM3 crypto algorithm GUID definitionLiming Gao2025-01-312-0/+39
| | | | | | | UEFI 2.11 has been published on https://uefi.org/specifications It defines SM3 crypto algorithm GUID and structure. Signed-off-by: Liming Gao <gaoliming@byosoft.com.cn>
* Devcontainer: Use latest Fedora 40 imageOliver Steffen2025-01-311-1/+1
| | | | | | | Since the CI is now running on Fedora 40, let's also switch over VSCode Devcontainer to use the same. Signed-off-by: Oliver Steffen <osteffen@redhat.com>
* .github/codeql.yml: Drop ArmPkg IA32 and X64 from build matrixMichael Kubacki2025-01-301-2/+0
| | | | | | | These archs are not supported by ArmPkg so we can save agent resources by not attempting to schedule their CodeQL build. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
* ArmVirtPkg: Drop reference to ArmDisassemblerLibArd Biesheuvel2025-01-301-1/+0
| | | | | | ArmDisassemblerLib is going away ... Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg: Stop using ArmDisassemblerLibArd Biesheuvel2025-01-305-35/+1
| | | | | | | | | | | | | | | | | | | | ArmDisassemblerLib is used to pretty print the instruction that triggered an unhandled exception, but it was never implemented for AARCH64, and according to the existing file comment, Thumb2 support (which is used predominantly when building EDK2 for 32-bit ARM due to its smaller size) is incomplete. The DEBUG diagnostics that are produced on an unhandled exception are generally sufficient to dump the entire executable that triggered it, and so this disassembly is of limited value, especially because it doesn't work on AARCH64. So let's start getting rid of it, by dropping references to it in code and in the various .INF and .DSC files. Once out-of-tree platforms have been allowed to catch up, we can remove the library implementation and its class definition entirely. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg,ArmPkg/ArmExceptionLib: drop vector relocation variant/supportLeif Lindholm2025-01-309-252/+21
| | | | | | | | | | | | There were several bugs in the vector table relocation code which means it can't really have been used by anyone on AArch64 in the last decade or so. So delete the support code from the library, as well as the ArmRelocateExceptionLib.inf file. This gets rid of PcdDebuggerExceptionSupport (including a duff reference in CpuDxe), PcdCpuVectorBaseAddress and PcdRelocateVectorTable. Signed-off-by: Leif Lindholm <leif.lindholm@oss.qualcomm.com>
* ArmVirtPkg/ArmVirtQemu: Reduce MMIO region mapped by defaultArd Biesheuvel2025-01-301-7/+7
| | | | | | | | | | | | Currently, the ArmVirtQemu startup code maps a 128 MiB of MMIO space, as it knows that the UART, GIC and RTC live there. Now that the GIC driver maps its MMIO registers itself, there is no need for this region to cover its MMIO space. And there are other regions here that don't need to be mapped by default: the only ones that need to be mapped are the UARTS, the RTC, the fw_cfg MMIO interface and the virtio-mmio regions, all of which live in a 32 MiB window starting at address 0x900_0000. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Map GIC MMIO regions before useArd Biesheuvel2025-01-303-11/+62
| | | | | | | | | | | | | | | The GIC driver itself has intimate knowledge of the hardware, and so it is the best suited to create the mappings of the MMIO control regions, in case they have not been mapped yet by the platform code. So call in the the CPU arch protocol to map the CPU interface, distributor and redistributor regions as they are discovered by the GIC driver startup code. Note that creating these mappings has no effect if the regions in question have already been mapped with the correct attributes. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Remove pointless passing around of MMIO addressesArd Biesheuvel2025-01-301-29/+12
| | | | | | | | The GIC distributor and redistributor addresses that are passed into the interrupt enable and disable routines are always the same, so just use the global variables directly. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Avoid pointless repeated iteration over GIC framesArd Biesheuvel2025-01-301-46/+13
| | | | | | | | | The GIC DXE driver only runs on the boot CPU, and so there is really no point in iterating over all the redistributor frames every time an interrupt is enabled, disabled or its state tested. Instead, do this only at load time. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Replace CpuArch registration event with DEPEXArd Biesheuvel2025-01-305-66/+20
| | | | | | | | | | | | Instead of relying on a protocol notification event to register the core IRQ interrupt handler with CPU arch protocol once it becomes available, use a DEPEX to ensure that the GIC driver is not dispatched at all until the CPU arch protocol has turned up. This will allow the GIC driver to use other CPU arch protocol methods, such as the ones needed to map the GIC MMIO regions at driver startup. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Replace DEPEX on h/w protocol with event notificationArd Biesheuvel2025-01-302-4/+106
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, ArmPkg's CpuDxe DEPEXes on the hardware interrupt protocol, to ensure that it is not dispatched before the GIC driver. This way, the CpuDxe driver is guaranteed not to enable interrupts on the CPU side before the GIC driver has had the opportunity to configure the interrupts on the distribution side. However, this prevents the GIC driver from using any of the CPU arch protocol interfaces, such as mapping memory, which it may need to do on platforms where the GIC MMIO regions are not mapped yet when the driver is started. So instead, use a protocol notification on the hardware interrupt protocol, which is installed by the GIC driver (as well as other existing interrupt controller drivers for platforms that do not implement a GIC) after it starts up and deasserts and disables all incoming interrupts. Manipulate the interrupt state as usual only after this notification has been received. Before that, keep track of the caller's intent regarding the interrupt enabled state in a shadow variable, but do not actually enable interrupt delivery to the CPU just yet. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Remove rudimentary vector handoff logicArd Biesheuvel2025-01-303-43/+5
| | | | | | | | | | | | | | | | There is some fossilized code in the CpuDxe driver startup code that permits a vector table to be inherited from the PEI stage, but this code is essentially dead on ARM platforms, given that the VectorInfo argument passed to InitializeCpuExceptionHandlers() is ignored, and no code appears to exist that would result in the gEfiVectorHandoffTableGuid configuration table ever being populated. Also, due to prior refactoring, the code that disables and re-enables IRQs and FIQs is completely pointless, and can simply be removed. That, in turn, allows the CPU arch protocol parameter to be dropped from the prototype of InitializeExceptions(). Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Use STATIC linkage where possibleArd Biesheuvel2025-01-302-1/+10
| | | | | | | | Use static linkage for variables and routines that are not referenced from other objects. This is generally preferred, because it gives the compiler more freedom for optimization. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Fix error handling in driver initializationArd Biesheuvel2025-01-301-4/+10
| | | | | | | | | | | | | | | | | | | Failure to install the CPU arch protocol is a fatal error, so treat it as such, rather than ignore it, even though we won't get very far if this driver fails to dispatch - at least, we will get an error in a DEBUG build rather than a mysterious failure due to unsatisfied DEPEXes. Failure to install the idle loop event handler is not a fatal error, and it should not cause the driver to exit with an error, as this will unload the driver and keep the installed CPU arch protocol pointer dangling. So keep the ASSERT() on the return value, but return EFI_SUCCESS once we're past the point where the CPU arch protocol has been installed. Since the protocol is never uninstalled, make the CPU handle function local, as there is no point in keeping its value around. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* Maintainers.txt: Update EmulatorPkg maintainersMichael Kubacki2025-01-291-0/+2
| | | | | | Add Oliver Smith-Denny and Michael Kubacki as maintainers. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
* UnitTestFrameworkPkg: Fix false positives from address sanitizerMichael D Kinney2025-01-291-23/+23
| | | | | | | | | | | | | | | | | | | | | | PR #6408 introduced a host specific NORETURN function to resolve false positives from the address sanitizer when LongJump() is called and the stack is reset to a previous stack frame. This approach was discussed here: https://github.com/tianocore/edk2/pull/6408/files#r1918810499 False positives are still being observed with this initial solution. The address sanitizer provides __asan_handle_no_return() to clean up shadow memory before a NORETURN function is called and provides a simpler implementation for this issue without having to introduce a host specific NORETURN function. https://github.com/llvm/llvm-project/blob/main/compiler-rt/include/sanitizer/asan_interface.h Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
* MdePkg/BasePeCoffLib: Remove DEBUG() statements from runtime codeArd Biesheuvel2025-01-291-2/+6
| | | | | | | | | | | | | PeCoffLoaderRelocateImageForRuntime() executes after boot services, and so it should not use DEBUG() prints at all, given that these may rely on MMIO mappings or other boot time facilities that are no longer available. So revert the changes in aedcaa3df8a2 ("MdePkg: Fix overflow issue in PeCoffLoaderRelocateImageForRuntime") that replaced code comments with DBEUG() statements. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ShellPkg: fix warnings about uninitialized variableMike Maslenkin2025-01-291-10/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dmem.c: In function 'GetImageExecutionInfo': Dmem.c:241:10: error: 'Status' may be used uninitialized in this function [-Werror=maybe-uninitialized] return Status; ^~~~~~ Dmem.c:284:35: note: 'Status' was declared here EFI_STATUS Status; ^~~~~~ Dmem.c: In function 'ShellCommandRunDmem': Dmem.c:586:27: error: 'ConformanceProfileTableAddress' may be used uninitialized in this function [-Werror=maybe-uninitialized] ShellStatus = DisplayConformanceProfiles (ConformanceProfileTableAddress); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dmem.c:582:27: error: 'ImageExecutionTableAddress' may be used uninitialized in this function [-Werror=maybe-uninitialized] ShellStatus = DisplayImageExecutionEntries (ImageExecutionTableAddress); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dmem.c:578:27: error: 'RtPropertiesTableAddress' may be used uninitialized in this function [-Werror=maybe-uninitialized] ShellStatus = DisplayRtProperties (RtPropertiesTableAddress); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* OvmfPkg: fix warning about uninitialized variableMike Maslenkin2025-01-291-0/+1
| | | | | | | | | | | | | | | | | | | | | | | GenericQemuLoadImageLib.c: In function 'QemuLoadKernelImage': GenericQemuLoadImageLib.c:323:5: error: 'CommandLine' may be used uninitialized in this function [-Werror=maybe-uninitialized] UnicodeSPrintAsciiFormat ( ^~~~~~~~~~~~~~~~~~~~~~~~~~ KernelLoadedImage->LoadOptions, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ KernelLoadedImage->LoadOptionsSize, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "%a%a", ~~~~~~~ (CommandLineSize == 0) ? "" : CommandLine, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (InitrdSize == 0) ? "" : " initrd=initrd" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ); ~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* SecurityPkg/RngDxe: fix warning about uninitialized variableMike Maslenkin2025-01-291-1/+5
| | | | | | | | | | | | ArmTrng.c: In function 'GenerateEntropy': ArmTrng.c:40:15: error: 'Status' may be used uninitialized in this function [-Werror=maybe-uninitialized] EFI_STATUS Status; ^~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* MdeModulePkg: NvmExpressDxe: fix warning about uninitialized variableMike Maslenkin2025-01-291-0/+2
| | | | | | | | | | | | NvmExpressMediaSanitize.c: In function 'NvmExpressMediaClear': NvmExpressMediaSanitize.c:337:29: error: 'Status' may be used uninitialized in this function [-Werror=maybe-uninitialized] EFI_STATUS Status; ^~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* MdeModulePkg: fix warning about uninitialized variableMike Maslenkin2025-01-291-0/+2
| | | | | | | | | | | Handle.c:1302:24: error: 'Prot' may be used uninitialized in this function [-Werror=maybe-uninitialized] *Interface = Prot->Interface; ~~~~^~~~~~~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* MdeModulePkg: PeiMain: fix warning about uninitialized variableMike Maslenkin2025-01-291-5/+5
| | | | | | | | | | Dispatcher.c:1639:34: error: 'FvMigrationFlags' may be used uninitialized in this function [-Werror=maybe-uninitialized] (((FvMigrationFlags & FLAGS_FV_MIGRATE_BEFORE_PEI_CORE_REENTRY) == 0) || ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* OvmfPkg/QemuKernelLoaderFsDxe: use SIZE_OF_EFI_FILE_INFOGerd Hoffmann2025-01-281-1/+1
| | | | Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* Resolved Coverity Issues in Http DxeSanthosh Kumar V2025-01-282-10/+35
| | | | | | | | | | | | | | | | 1.HttpResponseWorker(DEADCODE) The result of pointer arithmetic "HttpHeaders+AsciiStrLen("HTTP/1.1") + 1" is never null. 2.HttpsSupport.c (NULL_RETURNS) NetbufAlloc might return null pointer ,so assigning "NULL" to "PacketOut" and "DataOut" pointer. Solution: 1.Removed the NULL Check for "StatusCodeStr" 2.Added Null Check for PacketOut and returned EFI_OUT_OF_RESOURCES on NULL case. Signed-off-by: santhosh kumar V <santhoshkumarv@ami.com>
* MdePkg: Fix Clang Build ErrorINDIA\sachinganesh2025-01-281-5/+2
| | | | | | | Fixed Clang build error introduced by unintialized variables in https://github.com/tianocore/edk2/commit/6278bbb89822c598fcd0637ae74174e367895c84 Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* OvmfPkg: make legacy direct kernel loader code nx cleanGerd Hoffmann2025-01-271-1/+1
| | | | | | kernel pages are code not data. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* BaseTools: Fix NoneType parent reference in FMMT operationsAshraf Ali S2025-01-271-3/+12
| | | | | | | | | | | | | | | | | | This patch addresses an issue in the FMMT operations where the parent reference is not checked for NoneType. This oversight can lead to an AttributeError: 'NoneType' object has no attribute 'Name' when attempting to access the parent reference. The fix involves adding a check for NoneType before accessing the parent reference to ensure that the operations handle such cases gracefully. The affected functions include: - AddNewFfs - ReplaceFfs - ExtractFfs These functions now include proper checks to prevent the AttributeError. Signed-off-by: Ashraf Ali S <ashraf.ali.s@intel.com>
* OvmfPkg/XenPvBlkDxe: Update disk size calculationAnthony PERARD2025-01-272-6/+10
| | | | | | | | | | | | | | | | | The specification wasn't clear and even contradict itself regarding the calculation of the disk size. This have been clarified by Xen commit 221f2748e8da ("blkif: reconcile protocol specification with in-use implementations"). https://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=221f2748e8dabe8361b8cdfcffbeab9102c4c899 The value from the xenstore node "sectors" must be multiplied by 512 to have the size of the disk. Calculation of LastBlock is now the same for both CD-ROM case and generic case. Signed-off-by: Anthony PERARD <anthony.perard@vates.tech>
* OvmfPkg/IndustryStandard/Xen: Update io/blkif.hAnthony PERARD2025-01-271-12/+160
| | | | | | Import the latest version of blkif.h header from Xen. Signed-off-by: Anthony PERARD <anthony.perard@vates.tech>
* MdeModulePkg PeiMain: Remove return for PeiCoreBuildHobHandoffInfoTable()Star Zeng2025-01-262-10/+4
| | | | | | | | PeiCoreBuildHobHandoffInfoTable() always returns EFI_SUCCESS, and also its return is not consumed at all, so this patch removes return for PeiCoreBuildHobHandoffInfoTable(). Signed-off-by: Star Zeng <star.zeng@intel.com>
* UnitTestFrameworkPkg: Add SafeIntLib to Common IncludesINDIA\sachinganesh2025-01-261-0/+1
| | | | | | | SafeIntLib has been added to UnitTestFrameworkPkg Common Includes DSC for usage in host and target based tests. Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* MdePkg: Use SafeIntLib to handle overflowINDIA\sachinganesh2025-01-261-7/+13
| | | | | | | Used SafeIntLib to handle the overflow check in PeCoffLoaderRelocateImage Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* MdePkg: Fix overflow issue in PeCoffLoaderRelocateImageForRuntimeINDIA\sachinganesh2025-01-262-12/+14
| | | | | | | | | | RelocDir->Size is a UINT32 value, and RelocDir->VirtualAddress is also a UINT32 value. The current code in PeCoffLoaderRelocateImageForRuntime does not check for overflow when adding RelocDir->Size to RelocDir->VirtualAddress. This patch uses SafeIntLib to ensure that the addition does not overflow. Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* UefiPayloadPkg: Add 4KB align to CLANGDWARF build.Chasel Chiu2025-01-251-0/+1
| | | | | | | | | | After commit aca75d3 the PayloadEntry ELF header will miss dynamic section which caused PEI_ASSERT in PayloadLoader rebasing code. This commit adding common-page-size=0x1000 to CLANGDWARF_DLINK_FLAGS to overcome the ELF header generation issue. Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
* EmulatorPkg PlatformBm: Fix duplicate BootManagerMenuApp boot option issueYang Gang2025-01-241-1/+1
| | | | Signed-off-by: Yang Gang <yanggang@byosoft.com.cn>
* ShellPkg Http.c: Remove extra `\n` when using `-m` paramYang Gang2025-01-241-1/+1
| | | | | | | | There is already `PRINT_HII (STRING_TOKEN (STR_GEN_CRLF), NULL);` after `DownloadFile()`, remove this extra `\n` to avoid printing extra blank lines. Signed-off-by: Yang Gang <yanggang@byosoft.com.cn>
* OvmfPkg/GenericQemuLoadImageLib: fix cmdline + initrd handlingGerd Hoffmann2025-01-241-2/+10
| | | | | | | | | | | | | | Commit 459f5ffa24ae ("OvmfPkg/QemuKernelLoaderFsDxe: rework direct kernel boot filesystem") has a small change in behavior: In case there is no data the file is not created and attempts to open file return EFI_NOT_FOUND. Old behavior was to add a zero-length file to the filesystem. Fix GenericQemuLoadImageLib to handle EFI_NOT_FOUND correctly for 'initrd' and 'cmdline'. Reported-by: Srikanth Aithal <sraithal@amd.com> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* OvmfPkg/QemuKernelLoaderFsDxe: root directory name should be ""Gerd Hoffmann2025-01-241-1/+1
| | | | | | | | | UEFI spec says so, fix it. https://uefi.org/specs/UEFI/2.11/13_Protocols_Media_Access.html#efi-file-info Reported-by: Laszlo Ersek <laszlo.ersek@posteo.net> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* Maintainers.txt: Add Star as UefiCpuPkg reviewerStar Zeng2025-01-241-1/+1
| | | | | | Jiaxin has been maintainer, replace his reviewer line with Star. Signed-off-by: Star Zeng <star.zeng@intel.com>
* UefiCpuPkg LocalApicLib: Correct typo LINT0 to LINT1Star Zeng2025-01-242-2/+2
| | | | | | In ProgramVirtualWireMode(), correct typo LINT0 to LINT1. Signed-off-by: Star Zeng <star.zeng@intel.com>
* OvmfPkg/OvmfXen: use PeiPcdLib for PEI_COREAnthony PERARD2025-01-241-0/+1
| | | | | | | | | | | Commit d64d1e195ceb ("MdeModulePkg: PeiMain: Introduce implementation of delayed dispatch") introduced a new usage of the TimerLib which uses a dynamic PCD in OvmfXen platform. But PeiMain has only access to a NULL version of PcdLib, so OvmfXen can't start. Introduce PeiPcdLib for PEI_CORE so PeiMain can read dynamic PCDs. Signed-off-by: Anthony PERARD <anthony.perard@vates.tech>
* command drvcfg ASSERTzhu rui2025-01-241-6/+0
| | | | | | | | | | REF: https://github.com/tianocore/edk2/issues/10626 Issue command drvcfg directly, system halt Signed-off-by: "Zhu, Cliff" <Cliff.zhu@intel.com> Cc: Liming Gao <gaoliming@byosoft.com.cn> Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
* DynamicTablesPkg: Adds X64 FACS generator libraryAbdul Lateef Attar2025-01-248-6/+538
| | | | | | | | | | | | Adds a library to generate the ACPI FACS table for X64 architecture. It gathers the necessary FACS information from the configuration manager. Additionally, it includes an event to update the hardware signature in the FACS table, where the hardware signature is the CRC of all ACPI table's CRC Cc: Sami Mujawar <Sami.Mujawar@arm.com> Cc: Pierre Gondois <pierre.gondois@arm.com> Signed-off-by: Abdul Lateef Attar <AbdulLateef.Attar@amd.com>
* OvmfPkg/RiscVVirtQemu.dsc: enable VGA supportHeinrich Schuchardt2025-01-232-0/+2
| | | | | | | | | | | | QEMU enables VIRTIO_VGA by default. Libvirt falls back from virtio-gpu-pci to virtio-vga if made available by QEMU. We need to enable VGA support to get video output for EDK II in virt-manager. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
generated by cgit (git 2.34.1) at 2025-02-24 01:30:58 +0000