Downstream: 2501: Merge some downstream changes into upstream

[qaz6750]

Explain

• Merging some changes from downstream to upstream and proposing a Pr is to enable timely improvement in case of problems and avoid too many serious issues when merging to upstream.

Dependency Commit/PR

• 8998: Add Extracted Firmware for Nazgul SurfaceDuoBinaries-fork#8
• Nazgul: Modify and update the ACPI of Nazgul platform acpi_oem_third_party_common#12
• FamilyPkg: RamPartitionDxe: Consider the situation of allocating an area as RAM before 0x80000000 #446

Change

SDM845

• enchilada: Correcting DXE PE32 erroneous references

MSM8998

• Add basic support for MSM8998 and OnePlus 5T.
  • Patching dumpling USBConfigdxe to use Windbg.
• Add initial support for XiaoMi 6 (Sagit).
• Add Windows support for SDM835 platform.

SM8150

• Fix the incorrect use of ASN1X509Dxe.inf.

Common & Project

• Correct the Codenames of msm8998.
• Configure '-march' flags separately for each Silicon.
  • By making this change, each Silicon can be compiled using the corresponding '-march' flags.
• CI: Enable build support for MSM8998 platform and devices.

Notice

• The ACPI of both the dumpling and sagit devices will be updated after re-using the MTP-ACPI transplantation.
• By making this change, each Silicon can be compiled using the corresponding '-march' flags.
  • The UEFI compiled with the "armv9-a+crypto+rcpc" parameter can be used on platforms that support armv9.

Problem

MSM8998

• Currently, it is not possible to boot Windows using the ported UEFI. It will automatically restart after booting to bootmgfw (unknown reason), but Gurb2 starts well.
  • Already fixed
• Memory allocation issue.
  • Already fixed
• Windows fails to restart normally and should be investigated later.

Common

• There are still some minor issues on certain platforms (which are not related to the actual UEFI usage). We hope to resolve them in the future so as to make the project more tidy and standard.

[qaz6750]

Process 1

• We still need to investigate the bootmgfw loading issue and make improvements to some porting details.

Result 1

• Already fixed

[qaz6750]

Process 2

• Loading bootmgfw and restarting is not a memory issue. On the contrary, by changing "- march", it can load.
• Changing the parameter at -march to "armv8-a+crypto+rcpc" instead of "armv8.2-a+crypto+rcpc" can solve the problem, but the sdm835 platform is the only special case that requires this, and we have to consider the impact on other platformsChanging the parameter at -march to "armv8-a+crypto+rcpc" instead of "armv8.2-a+crypto+rcpc" can solve the problem, but the sdm835 platform is the only special case that requires this, and we have to consider the impact on other platforms.

Result 2

• Optimized already.

[gus33000]

MSM8998 and older are never ARMV8.1 or higher but simply ARMv8; such flags should be silicon dependent; and we shouldnt treat that as an exceptional/unique case either.

It should be defined on a per silicon basis. Another modern example are SW5100/SW5200 watch socs that are also ARMv8

but do not change it globally.

[qaz6750]

Process 3

• The testing device has 8g of memory, but after entering Windows, it can recognize a total of 8GB of memory, but only allocates (available) about 4-5g of memory. It is necessary to investigate why the memory has not been fully allocated.

• 6G Memory:

  • RAM Entry 0 : Base 0x0000000040000000 Size 0x00000000C0000000
  • RAM Entry 1 : Base 0x0000000100000000 Size 0x00000000BD8C0000

• 8G Memory:

  • RAM Entry 0 : Base 0x0000000080000000 Size 0x0000000100000000
  • RAM Entry 1 : Base 0x0000000180000000 Size 0x00000000FCCC0000

• How to fully allocate memory is currently a challenge, as the MemoryBase is not the same.

Related Commit and PR

• Add memory until the remaining memory can be automatically allocated.(690ad56)
• FamilyPkg: RamPartitionDxe: Consider the situation of allocating an area as RAM before 0x80000000 #446

Result 3

• For 6G memory devices, we need to test.
• Already fixed.

[qaz6750]

Process 4

• The UEFI port for the SDM835 platform has been basically completed, and efforts will be made to improve other aspects, but Windows Driver support and ACPI fixes will be carried out later(This is not part of the PR's plan).
• At the same time, we must investigate the issue of Windows not being able to restart properly.