Question regarding "boot-hartid" DT node
Sunil V L
sunilvl at ventanamicro.com
Mon Jan 17 20:47:04 PST 2022
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 at 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.
More information about the linux-riscv
mailing list