From: Sunil V L <sunilvl@ventanamicro.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Atish Patra <atishp@atishpatra.org>,
Anup Patel <anup@brainfault.org>,
Abner Chang <abner.chang@hpe.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jessica Clarke <jrtc27@jrtc27.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
sunil.vl@gmail.com, linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: Question regarding "boot-hartid" DT node
Date: Tue, 18 Jan 2022 10:17:04 +0530 [thread overview]
Message-ID: <20220118044704.GA3734@sunil-ThinkPad-T490> (raw)
In-Reply-To: <CAMj1kXGLLd5tK+rahpMrS+OV+Abmo6bkPUs0e2Z1wZhngoyzAg@mail.gmail.com>
On Thu, Jan 13, 2022 at 11:01:10AM +0100, Ard Biesheuvel wrote:
> On Thu, 13 Jan 2022 at 10:59, Sunil V L <sunilvl@ventanamicro.com> wrote:
> >
> > On Thu, Jan 13, 2022 at 10:50:11AM +0100, Ard Biesheuvel wrote:
> > > > Hi Ard,
> > > > Here is the draft EFI_RISCV_BOOT_PROTOCOL specification.
> > > > https://github.com/riscv-non-isa/riscv-uefi/releases/download/0.3/EFI_RISCV_PROTOCOL-spec.pdf
> > > >
> > > > If you are fine with this, we can freeze this spec. Thanks a lot for
> > > > your help on this.
> > >
> > > Please don't use the EFI_ prefix, it is reserved for protocols that
> > > are defined in the UEFI or PI specifications.
> >
> > Oh OK. I didn't know that. TCG2 protocols also start with EFI prefix. Is
> > that a mistake?
> >
>
> Yes.
>
> > Would "RISCV_EFI_BOOT_PROTOCOL" be better?
> >
>
> Yes, or RISCV_BOOT_PROTOCOL. The EFI is kind of redundant since we are
> dealing with a EFI protocol.
Thanks a lot!, Ard. While I agree EFI is kind of redundant, I still prefer to
keep it. Since RISC-V supports both EFI and non-EFI systems, having EFI
clearly indicates this is for EFI systems.
Thanks
Sunil
>
> > Thanks
> > Sunil
> > >
> > > Other than that, this looks fine to me.
> > >
> > > --
> > > Ard.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-01-18 4:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:05 Question regarding "boot-hartid" DT node Sunil V L
2021-12-02 15:09 ` Heinrich Schuchardt
2021-12-02 15:17 ` Sunil V L
2021-12-02 15:52 ` Heinrich Schuchardt
2021-12-02 16:20 ` Ard Biesheuvel
2021-12-02 16:53 ` Heinrich Schuchardt
2021-12-02 16:58 ` Ard Biesheuvel
2021-12-02 17:04 ` Heinrich Schuchardt
2021-12-02 17:10 ` Ard Biesheuvel
2021-12-02 19:29 ` Atish Patra
2021-12-03 10:13 ` Ard Biesheuvel
2021-12-03 10:53 ` Heinrich Schuchardt
2021-12-03 18:45 ` Heinrich Schuchardt
2021-12-04 0:44 ` Atish Patra
2021-12-04 1:47 ` Heinrich Schuchardt
2021-12-04 4:24 ` Anup Patel
2021-12-04 8:38 ` Heinrich Schuchardt
2021-12-04 14:00 ` Anup Patel
2021-12-04 18:34 ` Atish Patra
2021-12-04 19:03 ` Heinrich Schuchardt
2021-12-04 19:13 ` Ard Biesheuvel
2022-01-13 9:44 ` Sunil V L
2022-01-13 9:50 ` Ard Biesheuvel
2022-01-13 9:59 ` Sunil V L
2022-01-13 10:01 ` Ard Biesheuvel
2022-01-18 4:47 ` Sunil V L [this message]
2021-12-05 13:39 ` Sunil V L
2021-12-05 15:54 ` Jessica Clarke
2021-12-05 16:37 ` Sunil V L
[not found] ` <CAOnJCUJ1jmwj4jrWsL2UnV8Wit_-w2KVnqUxy3gsvzE4ZugHBQ@mail.gmail.com>
2021-12-06 4:26 ` Sunil V L
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=20220118044704.GA3734@sunil-ThinkPad-T490 \
--to=sunilvl@ventanamicro.com \
--cc=abner.chang@hpe.com \
--cc=anup@brainfault.org \
--cc=ardb@kernel.org \
--cc=atishp@atishpatra.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=jrtc27@jrtc27.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=sunil.vl@gmail.com \
--cc=xypron.glpk@gmx.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