Hi Pierre,
Thanks for reviewing this patch series. Please find my reply inline.
Regards,
Pranav
> -Original Message-
> From: Pierre Gondois
> Sent: Tuesday, June 21, 2022 2:15 PM
> To: devel@edk2.groups.io; Pranav Madhu ;
> Thomas Abraham
> Cc: Sami Mujawar ; Ard Biesheuvel
> ; nd
>
Hi Pierre,
Thanks for reviewing the patch series. IORT table has separate specification
document and not included as a part of ACPI 6.4. That was the reason for
excluding IORT from this series. If required, it will be updated in a separate
patch.
I've posted V3 of this patch, no major
On June 20, 2022 7:01 PM, Gerd Hoffman wrote:
>
> > + UINT8 *CfvBase;
> > + UINT32CfvSize;
> >
> >DEBUG ((DEBUG_INFO, "EMU Variable FVB Started\n"));
> >
> > @@ -774,6 +776,23 @@ FvbInitialize (
> >
> >mEmuVarsFvb.BufferPtr = Ptr;
> >
> > + //
> > + //
++ James
-Original Message-
From: Guo, Gua
Sent: Monday, June 20, 2022 9:56 AM
To: devel@edk2.groups.io
Cc: Guo, Gua ; Dong, Guo ; Ni, Ray
Subject: [PATCH] UefiPayloadPkg: UniversalPayloadBuild.py to support --pcd
feature
From: Gua Guo
REF:
I'm facing the same issue with latest EDK2 repo pull, using VS2019, NASM 2.15.
Somehow, got EmulatorPkg build working, but MdeModulePkg build fails with same
above error.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#90664):
From: Gua Guo
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3955
Currently, UPL freezed all PCD and only known UPL hob can hook DXE
Drivers behavior, add optional feature on UniversalPayloadBuild.py to
have another way to hook PCD value.
Cc: Guo Dong
Cc: Ray Ni
Signed-off-by: Gua Guo
Patch merged via:
PR - https://github.com/tianocore/edk2/pull/2997
Commit -
https://github.com/tianocore/edk2/commit/b97243dea3c95ad923fa4ca190940158209e8384
Best Regards,
Hao Wu
> -Original Message-
> From: devel@edk2.groups.io On Behalf Of Wu, Hao
> A
> Sent: Monday, June 20, 2022
*Reminder: TianoCore Bug Triage - APAC / NAMO*
*When:*
06/21/2022
6:30pm to 7:30pm
(UTC-07:00) America/Los Angeles
*Where:*
Consume the host-provided specification of PCI host bridges if
available. Using the DxeHardwareInfoLib, populate a list of
hardware descriptors based on the content of the "hardware-info"
fw-cfg file, if provided. In the affirmative case, use the
resources and attributes specified by the
Read the "hardware-info" item from fw-cfg to extract specifications
of PCI host bridges and analyze the 64-bit apertures of them to
find out the highest 64-bit MMIO address required which determines
the address space required by the guest, and, consequently, the
FirstNonAddress used to calculate
Define the HardwareInfoLib API and create the PeiHardwareInfoLib
which implements it, specifically for Pei usage, supporting
only static accesses to parse data directly from a fw-cfg file.
All list-like APIs are implemented as unsupported and only a
fw-cfg wrapper to read hardware info elements is
Increased control is provided in Ovmf platforms to define and configure
the specifications of multiple PCI host bridges in the hypervisor. The
host propagates this information to the guest, initially through fw-cfg
interface.
In some AWS EC2 platforms, we expose a PCI topology including several
Reviewed-by: Guo Dong
-Original Message-
From: Benjamin Doron
Sent: Sunday, June 5, 2022 5:55 PM
To: devel@edk2.groups.io
Cc: Dong, Guo ; Ni, Ray ; Maurice Ma
; You, Benjamin ; Rhodes, Sean
Subject: [PATCH v3] UefiPayloadPkg: Add support for logging to CBMEM console
Writes
Hello Pranav,
The definitions for the IORT table are still at 6_0,
(IORT revision=0):
MdePkg/Include/IndustryStandard/IoRemappingTable.h
and the definitions are used at:
Platform/ARM/SgiPkg/AcpiTables/Iort.aslc
The IORT spec is now at the version E.d (revision=5).
Does the IORT need to be
Hello everyone,
The UEFI specification states that Global Boot Services functions are
available on all platforms. Does that mean that we can assume that the
pointer to the functions of "global" boot services functions will be
valid if the SystemTable pointer and the BootServices pointer are
Hello Pranav,
Would it be possible to extend this change to the Juno aswell as the
platform has a Null Residency Counter and doesn't support OS Initiated LPI ?
Another remark is that for RdV1MC, RdN2, RdV1 and RdN2Cfg1 platforms,
CPUs don't need to be encapsulated anymore in cluster objects
Cf:
On 21/06/2022 07:04, Ayush Singh wrote:
1. Initialize the pointers needed for a module to work early on and
keep them local to the module. This will mean that the allocator
module will store the `allocate_pool` and `free_pool` pointers in a
static private to the module which will be initialized
Hello everyone,
I wanted to discuss and get ideas about how I should implement the
various services (like allocator and stdin) for UEFI in Rust. I have
come up with two approaches:
1. Initialize the pointers needed for a module to work early on and
keep them local to the module. This will mean
18 matches
Mail list logo
