As per feedback, reduced basic UEFI requirements to 2.6.1 of the UEFI spec. Added reason to understand why additional protocols need to be supported on top of basic requirements. Signed-off-by: Sunil

EFI_LOAD_FILE2_PROTOCOL is typically used to load from PCIe OptionROM apart from other use cases like loading from RAM. Since we are mandating PCIe, we added this requirement. We can add the clarifica

Hi Aaron, OS-A refers to EBBR which mandates reduced set of UEFI interfaces. Yes, UEFI is mandatory for server OS distros. What "other protocols" which you think not necessary to support server OSs? R

The platform spec will refer to this ACPI requirements document similar to other specifications like SBI etc. Signed-off-by: Sunil V L <sunilvl@...> --- riscv-platform-spec.adoc | 76 +++-

Signed-off-by: Sunil V L <sunilvl@...> --- riscv-platform-spec.adoc | 76 +++------------------------------------- 1 file changed, 5 insertions(+), 71 deletions(-) diff --git a/riscv-platf

Hi Team, As we discussed in the Platform HSC meeting yesterday, I am attaching the snapshot of the slides presented. Please also go through the https://github.com/riscv/riscv-acpi/wiki/ACPI-ASWG-ECR-P

Hi Abner, "," is required before your name here.

Hi Rahul, NIT: specifies -> specify

Hi Abner, My understanding is, these features are introduced to reduce some of the issues with SMM mode in x86. I am not sure whether we will have similar issues in risc-v and need to make this featur

As per my understanding, 1. AIA with both IMSIC and APLIC (Required) 2. PLIC + CLINT (deprecated) I see supporting local interrupts as one of the major goal of the AIA spec. So, I expect APLIC+IMSIC s

I think Block device partition format (GPT) section here is for the storage device where OS is stored to rule out any legacy MBR style partitioning. It is not for the storage where firmware is stored.

Hi Abner, Do we need both words - non-local and global ? Should we just say implementation specific? The last sentence is not clear to me. Could you rephrase it? I think you also need to add yourself

Hi Heinrich, Abner, I did respond to Heinrich https://lists.riscv.org/g/tech-unixplatformspec/message/832 I didn't want to specify "Load from ramdisk" since it can restrict the usage. I think the abil

This specifies mandatory requirements for server class platforms in addition to the requirements in base specification. Many dependencies and granular details are still TBD. But this is a good startin

Signed-off-by: Sunil V L <sunilvl@...> --- contributors.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contributors.adoc b/contributors.adoc index a0a960c..3d194

Signed-off-by: Sunil V L <sunilvl@...> Reviewed-by: Alistair Francis <alistair.francis@...> Reviewed-by: Bin Meng <bmeng.cn@...> --- changelog.adoc | 2 +- contributors.adoc | 4

Hi Abner, I just mentioned here based on a feedback. But I agree Rv128 would need separate target itself. Thanks. I mentioned type 44 under smbios section but please provide the text for its importanc

Hi Heinrich, EFI_LOAD_FILE2_PROTOCOL is required to load from PCIe option ROM. Also, there is a plan to support initrd in edk2 also https://github.com/riscv/riscv-edk2-platforms/issues/6

This specifies mandatory requirements for server class platforms in addition to the requirements in base specification. Many dependencies and granular details are still TBD. But this is a good startin

Signed-off-by: Sunil V L <sunilvl@...> --- contributors.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contributors.adoc b/contributors.adoc index a0a960c..3d194