From: "Björn Töpel" <bjorn@kernel.org>
To: 运辉崔 <cuiyunhui@bytedance.com>
Cc: Jessica Clarke <jrtc27@jrtc27.com>,
Emil Renner Berthing <emil.renner.berthing@gmail.com>,
Andrew Jones <ajones@ventanamicro.com>,
Ard Biesheuvel <ardb@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv <linux-riscv@lists.infradead.org>,
rminnich@gmail.com, Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
jdelvare@suse.com, 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 <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, geshijian@bytedance.com,
weidong.wd@bytedance.com, graf@amazon.de
Subject: Re: [External] [PATCH v2 1/3] riscv: obtain ACPI RSDP from FFI.
Date: Thu, 06 Jul 2023 10:52:14 +0200 [thread overview]
Message-ID: <87sfa1toap.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <CAEEQ3wnaaMvJ3=7udvAjiP3q36nvqAwb8sh34f+nO8Ua_83yFw@mail.gmail.com>
运辉崔 <cuiyunhui@bytedance.com> writes:
> Hi Björn,
>
> On Wed, Jul 5, 2023 at 10:43 PM Björn Töpel <bjorn@kernel.org> wrote:
>>
>> Jessica Clarke <jrtc27@jrtc27.com> writes:
>>
>> > On 3 Jul 2023, at 19:58, Emil Renner Berthing <emil.renner.berthing@gmail.com> wrote:
>> >>
>> >> On Mon, 3 Jul 2023 at 15:33, 运辉崔 <cuiyunhui@bytedance.com> wrote:
>> >>>
>> >>> Hi drew,
>> >>>
>> >>> On Mon, Jul 3, 2023 at 9:01 PM Andrew Jones <ajones@ventanamicro.com> wrote:
>> >>>>
>> >>>>
>> >>>> (This is a reply to a non-existent cover letter.)
>> >>>
>> >>> This has been discussed many times with Ard, Please refer to :
>> >>> https://patches.linaro.org/project/linux-acpi/patch/20230426034001.16-1-cuiyunhui@bytedance.com/
>> >>
>> >> Hi Yunhui,
>> >>
>> >> From that discussion it was mentioned that that arm supports 3 methods
>> >> of booting:
>> >> direct + devicetree
>> >> EFI + devicetree
>> >> EFI + ACPI
>> >> ..but not
>> >> direct + ACPI
>> >>
>> >> To me it isn't obvious from that or this thread, and since arm seems
>> >> to be doing fine without the 4th option I'm curious why that's
>> >> necessary on riscv?
>> >
>> > If anything we should be removing option 1, because that’s not a
>> > cross-OS standard (though RISC-V’s SBI direct booting is at least not
>> > tied to the OS). Any application-class platform spec is going to
>> > mandate EFI, because, whatever your thoughts of EFI are, that is *the*
>> > standard. And if you’re willing to pick up all the complexity of ACPI,
>> > what’s a bit of EFI (especially if you only go for a minimal one a la
>> > U-Boot)?
>>
>> Well said!
>>
>> Yunhui, why not simply add a minimal UEFI stub to Coreboot (like Jess
>> points out above)?
>
> In fact, in the v1 email, Coreboot's maintainer Ron has made it clear
> that Coreboot does not support EFI, and it is necessary to transmit
> firmware information through DTS on RISC-V.
It clear that Coreboot doesn't support UEFI today. We're "arguing" that
it's less work/verification adding the neccesary minimal UEFI plumbing
for Coreboot, than jumping through hoops in the kernel to work around
it.
I'm getting some UEFI FUD vibes here. I also think that parts of UEFI is
kind of ugly, but it's, as Jess says, *the* spec and honestly, a bit
what's expected (Hi CXL).
UEFI is a specification, and implementing the minimal requirements for
UEFI is not that of a big deal. Look at Alex Graf's (et al) work on
u-boot UEFI. U-boot is small/lean/open *and* manage to support enough
UEFI for ACPI.
The whole "Oh, UEFI is so bad, bloated, and closed" hand-wavery is a bit
tiring. :-(
...these last four sections is more of a beer discussion. I'll take my
"my FW is better than yours" rants elsewhere. ;-)
Björn
next prev parent reply other threads:[~2023-07-06 8:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 9:57 [PATCH v2 1/3] riscv: obtain ACPI RSDP from FFI Yunhui Cui
2023-07-02 9:57 ` [PATCH v2 2/3] firmware: introduce FFI for SMBIOS entry Yunhui Cui
2023-07-02 12:41 ` Conor Dooley
2023-07-03 8:23 ` [External] " 运辉崔
2023-07-03 8:34 ` Conor Dooley
2023-07-03 12:41 ` 运辉崔
2023-07-03 13:02 ` Conor Dooley
2023-07-03 13:26 ` 运辉崔
2023-07-02 9:57 ` [PATCH v2 3/3] riscv: obtain SMBIOS entry from FFI Yunhui Cui
2023-07-02 12:42 ` Conor Dooley
2023-07-03 7:50 ` [External] " 运辉崔
2023-07-03 8:16 ` Conor Dooley
2023-07-02 13:47 ` [PATCH v2 1/3] riscv: obtain ACPI RSDP " Conor Dooley
2023-07-03 4:21 ` Sunil V L
2023-07-03 6:19 ` [External] " 运辉崔
2023-07-03 7:19 ` 运辉崔
2023-07-03 8:12 ` Conor Dooley
2023-07-03 10:16 ` 运辉崔
2023-07-03 12:18 ` Conor Dooley
2023-07-03 13:04 ` 运辉崔
2023-07-03 13:01 ` Andrew Jones
2023-07-03 13:30 ` [External] " 运辉崔
2023-07-03 14:17 ` Andrew Jones
2023-07-03 14:23 ` Conor Dooley
2023-07-03 18:58 ` Emil Renner Berthing
2023-07-03 21:32 ` [External] " Jessica Clarke
2023-07-05 14:42 ` Björn Töpel
2023-07-06 2:24 ` 运辉崔
2023-07-06 8:52 ` Björn Töpel [this message]
[not found] ` <CAP6exY+gTSxU95nDK14z-Y1suKeXPkLzZ_BZqr-vRVGO9qmcxg@mail.gmail.com>
2023-07-07 9:05 ` Björn Töpel
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=87sfa1toap.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=cuiyunhui@bytedance.com \
--cc=emil.renner.berthing@gmail.com \
--cc=geshijian@bytedance.com \
--cc=graf@amazon.de \
--cc=jdelvare@suse.com \
--cc=jrtc27@jrtc27.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rminnich@gmail.com \
--cc=tinghan.shen@mediatek.com \
--cc=weidong.wd@bytedance.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