Linux2022 name is going to change and its just a placeholder for now. The platform specs builds upon the ISA level profiles A and M. Linux2022 corresponds to A profile (RVA2022) where we are

Atish Patra <Atish.Patra@...> 於 2021年4月22日 週四 上午5:33寫道： Don't get me wrong. I also agree with this point. I never thought to spec Linuxboot out in platform spec at this moment. I

Agreed. There are lot of moving pieces with LinuxBoot for RISC-V at this moment. I would suggest to have the Linux-2022 version with UEFI. We can include LinuxBoot in the future version as an

EDK II is available for RISC-V. So there is at least one compliant UEFI implementation. LinuxBoot might be used to boot into a Linux via kexec instead of UEFI but kexec excludes running any other

I'm not sure I follow #1. How can I write an operating system for the Server2022 platform without knowing what firmware framework will be in use? Jonathan

Hi Abner, Just to clarify, PLIC + CLINT is still required for the base spec (section 1.13) since there are platforms out there. ACPI is mandatory only for the server extension. For this class

Yes, Sunil. I think you and your company is the owner of ACPI of APLIC for AIA. :) PLIC could be the low-cost interrupt controller for the small platform (maybe not server) which also runs the ACPI

Hi all, I would like to give clarifications to some of the discussions in this week's meeting. 1. UEFI as the mandatory firmware. I brought up this because it is not necessary to mention we must

My reviews are inline below which is apart from the below recommendations if you don't think that is better. We have Linux2022 as the base feature set for all kinds of platform, however, there are

Hi Abner, We are mandating APLIC for AIA for server extension with ACPI. So, legacy PLIC is not required for ACPI. Thanks Sunil

Hi Abner, We don’t have an owner for the PLIC + CLINT section 1.1.3. Please go ahead and send out a patch to the mailing list for review. Regards Kumar

Hi all, Do we currently have an owner for section 1.1.3 PLIC + CLINT?https://github.com/riscv/riscv-platform-specs/blob/main/riscv-platform-spec.adoc#113-interrupt-controller If no, could I send the

Hi Abner, Meeting recordings will be uploaded @ https://github.com/riscv/riscv-platform-specs/wiki. Regards, Sunil

Initial changes for the Base Boot & Runtime requirements. The sections which are currently in-progress are marked as TBD. These changes can serve as the starting point and more details/changes can be

Hi Anup and Sunil, I think I missed the meeting this week. I thought it is Tuesday 11pm my time, however it is Monday actually. I was confused by the time zone. Sorry about that, I should get on

Merged Regards Kumar

Ping! >

Hi All, The next platform meeting is scheduled on Monday Apr 19th 8AM PST. Here are the details: Agenda and minutes kept on the github wiki: https://github.com/riscv/riscv-platform-specs/wiki Here

Hi Anup, thanks for giving me this information. Yes, I did miss most of the meetings. Sorry about I am not able to join this meeting in the past. Now I get more understanding of the organization of

Hi Abner, I think you missed lot of previous discussions/meetings. The RISC-V platform spec will define various classes of platforms targeting different use-cases. This particular patch adds