From: Andreas Schwab <schwab@linux-m68k.org>
To: u-boot@lists.denx.de
Subject: [RESEND PATCH v5 1/6] riscv: Add boot hartid to Device tree
Date: Sun, 19 Apr 2020 18:52:55 +0200 [thread overview]
Message-ID: <87imhvwh7c.fsf@igel.home> (raw)
In-Reply-To: <20200418060758.4839-2-atish.patra@wdc.com> (Atish Patra's message of "Fri, 17 Apr 2020 23:07:53 -0700")
On Apr 17 2020, Atish Patra wrote:
> Linux booting protocol mandates that register "a0" contains the hartid.
> However, U-boot can not pass the hartid via a0 during via standard UEFI
s/during via/during/
Andreas.
--
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-04-19 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 6:07 [RESEND PATCH v5 0/6] RISC-V DT related fixes for reserved memory & UEFI Atish Patra
2020-04-18 6:07 ` [RESEND PATCH v5 1/6] riscv: Add boot hartid to Device tree Atish Patra
2020-04-18 12:24 ` Bin Meng
2020-04-19 16:52 ` Andreas Schwab [this message]
2020-04-18 6:07 ` [RESEND PATCH v5 2/6] fdtdec: Fix boundary check Atish Patra
2020-04-18 12:24 ` Bin Meng
2020-04-18 6:07 ` [RESEND PATCH v5 3/6] riscv: Provide a mechanism to fix DT for reserved memory Atish Patra
2020-04-18 12:24 ` Bin Meng
2020-04-18 6:07 ` [RESEND PATCH v5 4/6] riscv: Setup reserved-memory node for FU540 Atish Patra
2020-04-18 12:25 ` Bin Meng
2020-04-18 6:07 ` [RESEND PATCH v5 5/6] riscv: Copy the reserved-memory nodes to final DT Atish Patra
2020-04-18 6:07 ` [RESEND PATCH v5 6/6] riscv: Move all fdt fixups together Atish Patra
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=87imhvwh7c.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=u-boot@lists.denx.de \
/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