[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEEQ3wmDBJkfOeKCQfcnuE+1=1K0D2pzu+Sn+zPEWk+RHs0NFQ@mail.gmail.com>
Date: Thu, 27 Apr 2023 11:37:46 +0800
From: 运辉崔 <cuiyunhui@...edance.com>
To: Mark Rutland <mark.rutland@....com>
Cc: Ard Biesheuvel <ardb@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, rafael@...nel.org,
lenb@...nel.org, jdelvare@...e.com, 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 Mark,
On Wed, Apr 26, 2023 at 6:07 PM Mark Rutland <mark.rutland@....com> wrote:
>
> 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.
The device tree only needs to complete the parse of the memory type attributes,
it should not be very complicated.
>
> We'd have to create entirely new ways to pass that information, which is not
> very desirable.
>
>
> Can you extend coreboot to provide EFI services, or to chain-load an EFI
> payload?
Currently, coreboot does not support UEFI, and it may not support it
in the future.
Hi rminnich, what do you think?
Thanks,
Yunhui
Powered by blists - more mailing lists