public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: 运辉崔 <cuiyunhui@bytedance.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	rafael@kernel.org, lenb@kernel.org, jdelvare@suse.com,
	cujomalainey@chromium.org, yc.hung@mediatek.com,
	angelogioacchino.delregno@collabora.com,
	allen-kh.cheng@mediatek.com,
	pierre-louis.bossart@linux.intel.com, tinghan.shen@mediatek.com,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	rminnich@gmail.com
Subject: Re: [External] Re: [PATCH] firmware: added a firmware information passing method FFI
Date: Wed, 26 Apr 2023 11:07:25 +0100	[thread overview]
Message-ID: <ZEj33QLZqEeL+/y4@FVFF77S0Q05N> (raw)
In-Reply-To: <CAEEQ3wkJB5CKm33mHXUOPX5makYOHF8By6FYGnNzRkM-Mo72OQ@mail.gmail.com>

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@kernel.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.

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.

  reply	other threads:[~2023-04-26 10:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  3:40 [PATCH] firmware: added a firmware information passing method FFI Yunhui Cui
2023-04-26  7:08 ` Ard Biesheuvel
2023-04-26  9:34   ` [External] " 运辉崔
2023-04-26 10:07     ` Mark Rutland [this message]
2023-04-27  3:37       ` 运辉崔
     [not found]         ` <CAP6exY+ydbzh1EkWTFejzwaW+PA-ySVO2Qj+CVJ1XbSMce2S9Q@mail.gmail.com>
2023-04-27 11:24           ` Mark Rutland
2023-04-27 12:52             ` Ard Biesheuvel
2023-04-28  3:17               ` 运辉崔
     [not found]                 ` <CAP6exYK9ytcgqcy2gFyOGvbxd7DPGQNs=m7nNgnfunnh8et9aQ@mail.gmail.com>
2023-04-28 18:03                   ` Ard Biesheuvel
2023-05-04 12:05                     ` 运辉崔
2023-05-04 13:44                       ` Ard Biesheuvel
     [not found]           ` <CAP6exY+tqAU0j1TVEMTzTb18M6_mPH5bWWiAS=94gyDGTY3hyQ@mail.gmail.com>
2023-06-21  8:04             ` 运辉崔
2023-06-24 12:52               ` Ard Biesheuvel
2023-06-25  7:33                 ` 运辉崔
2023-06-25  7:42                   ` Ard Biesheuvel
2023-06-25 11:54                     ` 运辉崔
2023-06-25 13:12                       ` Ard Biesheuvel
     [not found]                         ` <CAP6exYJRE8iM63SX3hQP9_5aKYcnN5x0KOAtZOgeEWU5bwLEBA@mail.gmail.com>
2023-06-26  2:35                           ` 运辉崔
2023-06-26  6:42                             ` Ard Biesheuvel
2023-06-26  8:05                               ` 运辉崔
2023-06-26  8:22                                 ` Ard Biesheuvel
2023-06-26 10:19                                   ` 运辉崔
2023-06-27  7:09                                     ` 运辉崔
2023-06-27  9:50                                     ` Ard Biesheuvel
2023-06-27 12:39                                       ` 运辉崔
2023-04-26  9:21 ` kernel test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZEj33QLZqEeL+/y4@FVFF77S0Q05N \
    --to=mark.rutland@arm.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=ardb@kernel.org \
    --cc=cuiyunhui@bytedance.com \
    --cc=cujomalainey@chromium.org \
    --cc=jdelvare@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rafael@kernel.org \
    --cc=rminnich@gmail.com \
    --cc=tinghan.shen@mediatek.com \
    --cc=yc.hung@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox