Hi Sami,
On Mon, Jan 22, 2024 at 05:15:44PM +, Sami Mujawar wrote:
> Hi All,
>
> DynamicTablesPkg currently supports Arm architecture, and we welcome the
> adoption by other architectures.
>
> Following is my proposal for moving forward.
>
> Goals:
> - reuse common code
> - streamline the
Hi All,
DynamicTablesPkg currently supports Arm architecture, and we welcome the
adoption by other architectures.
Following is my proposal for moving forward.
Goals:
- reuse common code
- streamline the adoption by other architectures
- minimise the impact on migration of the existing platforms
> > It looks like instead of moving the common code to
> EObjNameSpaceStandard namespace or a new (Arch? Common?) namespace,
> you're renaming the entire EObjNameSpaceArm namespace to
> EObjNameSpaceArch. It seems to me that if ARM code vs. common code is
> being separated out, then the EObjNameSpa
Hi Jeshua,
On Tue, Jan 09, 2024 at 06:37:43PM +, Jeshua Smith wrote:
> > From: devel@edk2.groups.io On Behalf Of Sunil V L
> > via groups.io
> > Sent: Tuesday, January 9, 2024 9:29 AM
> > DynamicTablesPkg can be used by RISC-V platforms to generate ACPI tables
> > from FDT passed from previou
> From: devel@edk2.groups.io On Behalf Of Sunil V L
> via groups.io
> Sent: Tuesday, January 9, 2024 9:29 AM
> DynamicTablesPkg can be used by RISC-V platforms to generate ACPI tables
> from FDT passed from previous stage FW. However, DynamicTablesPkg
> currently is ARM specific even though severa
DynamicTablesPkg can be used by RISC-V platforms to generate ACPI tables
from FDT passed from previous stage FW. However, DynamicTablesPkg
currently is ARM specific even though several parsers and ACPI
generators can be used across architectures. For ex: SSDT (PCIe), SSDT
(CPU), MCFG, SPCR, DBG2, F
