[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEEQ3wkJB5CKm33mHXUOPX5makYOHF8By6FYGnNzRkM-Mo72OQ@mail.gmail.com>
Date: Wed, 26 Apr 2023 17:34:55 +0800
From: 运辉崔 <cuiyunhui@...edance.com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, rafael@...nel.org,
lenb@...nel.org, jdelvare@...e.com, cujomalainey@...omium.org,
yc.hung@...iatek.com, angelogioacchino.delregno@...labora.com,
allen-kh.cheng@...iatek.com, pierre-louis.bossart@...ux.intel.com,
tinghan.shen@...iatek.com, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, rminnich@...il.com
Subject: Re: [External] Re: [PATCH] firmware: added a firmware information
passing method FFI
Hi Ard,
On Wed, Apr 26, 2023 at 3:09 PM Ard Biesheuvel <ardb@...nel.org> 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.
> 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.
Thanks,
Yunhui
Powered by blists - more mailing lists