On Wed, Apr 26, 2023 at 05:34:55PM +0800, 运辉崔 wrote: > Hi Ard, > > On Wed, Apr 26, 2023 at 3:09 PM Ard Biesheuvel <ardb@xxxxxxxxxx> wrote: > > > > Hello Yunhui, > > > > I am not sure this is a good idea: this is clearly intended for arm64, > > which cannot use ACPI without the EFI memory map, which it uses to > > cross reference memory opregion accesses, to determine the correct > > memory type attributes. > > > Not only for arm64, but also other arches, such as riscv. > For memory-related nodes, it will be done in the early scan of the device tree. Ard's point is that the device tree doesn't have all the same information (e.g. nothing in DT describes the memory type attributes), and so this isn't sufficient. We'd have to create entirely new ways to pass that information, which is not very desirable. > > What is the use case you are trying to accommodate here? > > > Some bootloaders do not support uefi, such as coreboot, > but need to support acpi, smbios. For arm64 at least, if you need ACPI you must have EFI, and trying to change that will require significant work and long term maintenance. Can you extend coreboot to provide EFI services, or to chain-load an EFI payload? Thanks, Mark.
