Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: 运辉崔 <cuiyunhui@bytedance.com>
Cc: Conor Dooley <conor@kernel.org>, <ardb@kernel.org>,
	<palmer@dabbelt.com>, <paul.walmsley@sifive.com>,
	<aou@eecs.berkeley.edu>, <linux-riscv@lists.infradead.org>,
	<rminnich@gmail.com>, <mark.rutland@arm.com>,
	<lpieralisi@kernel.org>, <rafael@kernel.org>, <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@vger.kernel.org>,
	<linux-acpi@vger.kernel.org>, <geshijian@bytedance.com>,
	<weidong.wd@bytedance.com>
Subject: Re: [External] Re: [PATCH v2 3/3] riscv: obtain SMBIOS entry from FFI.
Date: Mon, 3 Jul 2023 09:16:33 +0100	[thread overview]
Message-ID: <20230703-escapist-granny-14faea3ab0ef@wendy> (raw)
In-Reply-To: <CAEEQ3wkaazkV9MrfvWQMSXixtqahgdYVe=GT9ZZJnW-r1AQ1aA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]

On Mon, Jul 03, 2023 at 03:50:57PM +0800, 运辉崔 wrote:
> On Sun, Jul 2, 2023 at 8:42 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > Hey,
> >
> > On Sun, Jul 02, 2023 at 05:57:34PM +0800, Yunhui Cui wrote:
> > > When we bringup with coreboot on riscv, we need to obtain
> > > the entry address of SMBIOS through the FFI scheme.
> >
> > What do you need it for?
> RISC-V will be server-oriented, and the system needs to be managed
> based on SMBIOS.

Really what this commit message is missing is something that explains
why you need the FFI scheme. Say along the lines of:

	Coreboot on RISC-V does not support EFI, and needs to use the
	FDT Firmware Interface (FFI) to pass the entry address of SMBIOS
	to the kernel.

Cheers,
Conor.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-07-03  8:17 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 [this message]
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
     [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=20230703-escapist-granny-14faea3ab0ef@wendy \
    --to=conor.dooley@microchip.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=conor@kernel.org \
    --cc=cuiyunhui@bytedance.com \
    --cc=geshijian@bytedance.com \
    --cc=jdelvare@suse.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