Re: SPCR / SSDT generation in the DynamicTablesPkg
To add a little more detail on what we were seeing our 16550 based serial has 4 byte spacing which the SPCR table is generated with correctly but then the dynamic table code creates a SSDT with the standard pnp hid/cid in the ssdt table which at least from my reading of the Linux driver looks like that only uses 1 byte spacing between registers. It is possible I missed something though.
Get Outlook for Android<https://aka.ms/ghei36>
From: Irene Park <firstname.lastname@example.org>
Sent: Wednesday, November 18, 2020 1:16:10 AM
To: email@example.com <firstname.lastname@example.org>; Irene Park <email@example.com>; Sami.Mujawar@arm.com <Sami.Mujawar@arm.com>; firstname.lastname@example.org <email@example.com>; Alexei Fedorov <Alexei.Fedorov@arm.com>; Jeff Brasen <firstname.lastname@example.org>
Subject: RE: [edk2-discuss] SPCR / SSDT generation in the DynamicTablesPkg
Hi Sami, Pierre, Alexei,
I wonder your thought about this topic.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Irene Park
Sent: Tuesday, November 17, 2020 3:28 AM
Subject: [edk2-discuss] SPCR / SSDT generation in the DynamicTablesPkg
External email: Use caution opening links or attachments
The latest patches to the DynamicTablesPkg help an SSDT generated to meet the SBBR requirement when an SPCR generation is desired.
But the auto-generated SSDT might be unable to describe the compatible but custom 16550 device on the non-SBBR compliant platform.
I wonder if an SSDT generation would be manageable when a user doesn't want to.