Public review of RISC-V UEFI Protocol Specification

Public review of RISC-V UEFI Protocol Specification

[Sunil V L]

This is to announce the start of the public review period for
the RISC-V UEFI Protocol specification. This specification is 
considered as frozen now as per the RISC-V International policies.

The review period begins today, Wednesday March 23, and ends on Friday
May 6 (inclusive).

The specification can be found here
https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc3/RISCV_UEFI_PROTOCOL-spec.pdf

which was generated from the source available in the following GitHub
repo:
https://github.com/riscv-non-isa/riscv-uefi

The specification is also attached in this email.

To respond to the public review, please either reply to this email or
send comments to the platform mailing list[1] or add issues to the
GitHub repo[2]. We welcome all input and appreciate your time and
effort in helping us by reviewing the specification.

During the public review period, corrections, comments, and
suggestions, will be gathered for review by the Platform HSC members.
Any minor corrections and/or uncontroversial changes will be
incorporated into the specification. Any remaining issues or proposed changes
will be addressed in the public review summary report. If there are no
issues that require incompatible changes to the public review
specification, the platform HSC will recommend the updated
specifications be approved and ratified by the RISC-V Technical
Steering Committee and the RISC-V Board of Directors.

Thanks to all the contributors for all their hard work.

[1] tech-unixplatformspec@lists.riscv.org
[2] https://github.com/riscv-non-isa/riscv-uefi/issues

Regards
Sunil


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

Re: [RISC-V] [tech-unixplatformspec] Public review of RISC-V UEFI Protocol Specification

[Anup Patel]

(Resending for RISC-V ISA-DEV and RISC-V SW-DEV because previous email
was not received on these lists.)

On Wed, Mar 23, 2022 at 9:46 PM Sunil V L <sunilvl@ventanamicro.com> wrote:
>
> This is to announce the start of the public review period for
> the RISC-V UEFI Protocol specification. This specification is
> considered as frozen now as per the RISC-V International policies.
>
> The review period begins today, Wednesday March 23, and ends on Friday
> May 6 (inclusive).
>
> The specification can be found here
> https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc3/RISCV_UEFI_PROTOCOL-spec.pdf
>
> which was generated from the source available in the following GitHub
> repo:
> https://github.com/riscv-non-isa/riscv-uefi
>
> The specification is also attached in this email.
>
> To respond to the public review, please either reply to this email or
> send comments to the platform mailing list[1] or add issues to the
> GitHub repo[2]. We welcome all input and appreciate your time and
> effort in helping us by reviewing the specification.
>
> During the public review period, corrections, comments, and
> suggestions, will be gathered for review by the Platform HSC members.
> Any minor corrections and/or uncontroversial changes will be
> incorporated into the specification. Any remaining issues or proposed changes
> will be addressed in the public review summary report. If there are no
> issues that require incompatible changes to the public review
> specification, the platform HSC will recommend the updated
> specifications be approved and ratified by the RISC-V Technical
> Steering Committee and the RISC-V Board of Directors.
>
> Thanks to all the contributors for all their hard work.
>
> [1] tech-unixplatformspec@lists.riscv.org
> [2] https://github.com/riscv-non-isa/riscv-uefi/issues
>
> Regards
> Sunil
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#1694): https://lists.riscv.org/g/tech-unixplatformspec/message/1694
> Mute This Topic: https://lists.riscv.org/mt/89979471/6366717
> Group Owner: tech-unixplatformspec+owner@lists.riscv.org
> Unsubscribe: https://lists.riscv.org/g/tech-unixplatformspec/unsub [anup@brainfault.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

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

[PATCH] Fix typos in introduction for RISCV_EFI_BOOT_PROTOCOL

[Heinrich Schuchardt]

UEFI uses to talk of configuration tables not of firmware tables.

Add missing 'the', 'and'.

Enhance readability of sentence concerning ExitBootServices().

Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
---
 boot_protocol.adoc | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/boot_protocol.adoc b/boot_protocol.adoc
index 12846b6..5c56edd 100644
--- a/boot_protocol.adoc
+++ b/boot_protocol.adoc
@@ -1,7 +1,7 @@
 [[boot_protocol]]
 == RISCV_EFI_BOOT_PROTOCOL
 Either Device Tree (DT) or Advanced Configuration and Power Interface (ACPI)
-firmware tables are used to convey the information about hardware to the
+configuration tables are used to convey the information about hardware to the
 Operating Systems. Some of the information are known only at boot time and
 needed very early before the Operating Systems/boot loaders can parse the
 firmware tables. 
@@ -9,16 +9,17 @@ firmware tables.
 One example is the boot hartid on RISC-V systems. On non-UEFI systems, this is
 typically passed as an argument to the kernel (in a0). However, UEFI systems need
 to follow UEFI application calling conventions and hence it can not be passed in
-a0. There is an existing solution which uses /chosen node in DT based systems to
-pass this information. However, this solution doesn't work for ACPI based
+a0. There is an existing solution which uses the /chosen node in DT based systems
+to pass this information. However, this solution doesn't work for ACPI based
 systems. Hence, a UEFI protocol is preferred for both DT and ACPI based systems.
 
 This UEFI protocol for RISC-V systems provides early information to the
-bootloaders or Operating Systems. Firmwares like EDK2/u-boot need to implement
-this protocol on RISC-V UEFI systems.
+bootloaders or Operating Systems. Firmwares like EDK2 and u-boot need to
+implement this protocol on RISC-V UEFI systems.
 
-This protocol is typically used by the bootloaders before *ExitBootServices()*
-call and pass the information to the Operating Systems.
+This protocol is typically called by the bootloaders before invoking
+*ExitBootServices()*. They then pass the information to the Operating
+Systems.
 
 The version of RISCV_EFI_BOOT_PROTOCOL specified by this specification is
 0x00010000. All future revisions must be backwards compatible. If a new version
-- 
2.34.1


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