From: Andrew Jones <ajones@ventanamicro.com>
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-doc@vger.kernel.org,
"Song Shuai" <songshuaishuai@tinylab.org>,
linux-kernel@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 2/3] Documentation: riscv: Add early boot document
Date: Thu, 22 Jun 2023 19:23:56 +0200 [thread overview]
Message-ID: <20230622-4af59422f118ea634836d351@orel> (raw)
In-Reply-To: <20230621-d6da578719f8af903d6746ef@orel>
On Wed, Jun 21, 2023 at 02:19:50PM +0200, Andrew Jones wrote:
> On Wed, Jun 21, 2023 at 09:22:33AM +0200, Alexandre Ghiti wrote:
...
> > +Hardware description
> > +--------------------
> > +
> > +The firmware can pass either a devicetree or ACPI tables to the RISC-V kernel.
> > +
> > +The devicetree is either passed directly to the kernel from the previous stage
> > +using the `$a1` register, or when booting with UEFI, it can be passed using the
> > +EFI configuration table.
> > +
> > +The ACPI tables are passed to the kernel using the EFI configuration table. In
> > +this case, a tiny devicetree is still created by the EFI stub. Please refer to
> > +"EFI stub and devicetree" tree section below for details about this devicetree.
> ^ redundant 'tree' here
>
Can whoever applies this drop this 'tree' I pointed while applying?
Thanks,
drew
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-22 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 7:22 [PATCH v2 1/3] Documentation: arm: Add bootargs to the table of added DT parameters Alexandre Ghiti
2023-06-21 7:22 ` [PATCH v2 2/3] Documentation: riscv: Add early boot document Alexandre Ghiti
2023-06-21 8:15 ` Song Shuai
2023-06-21 9:18 ` Sunil V L
2023-06-21 12:15 ` Conor Dooley
2023-06-21 12:26 ` Alexandre Ghiti
2023-06-22 14:19 ` Conor Dooley
2023-06-21 12:19 ` Andrew Jones
2023-06-22 17:23 ` Andrew Jones [this message]
2023-06-22 17:32 ` Alexandre Ghiti
2023-06-22 17:41 ` Conor Dooley
2023-06-23 8:32 ` Alexandre Ghiti
2023-06-23 8:48 ` Alexandre Ghiti
2023-06-23 9:24 ` Andrew Jones
2023-06-21 13:23 ` Sunil V L
2023-06-22 14:39 ` Palmer Dabbelt
2023-06-21 7:22 ` [PATCH v2 3/3] Documentation: riscv: Update boot image header since EFI stub is supported Alexandre Ghiti
2023-06-22 14:39 ` Palmer Dabbelt
2023-06-22 14:39 ` [PATCH v2 1/3] Documentation: arm: Add bootargs to the table of added DT parameters Palmer Dabbelt
2023-06-23 14:14 ` Ard Biesheuvel
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=20230622-4af59422f118ea634836d351@orel \
--to=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=songshuaishuai@tinylab.org \
/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