- [RISC-V] [software] Add SBI extension space for firmware code base implementation
Re: [RISC-V] [software] Add SBI extension space for firmware code base implementation
Abner Chang <abner.chang@...>
toggle quoted messageShow quoted text
Got it, Software ML removed.
Johnathan, do you mean to define it as below?
Firmware Base Extension, Extension ID: 0xxxxxxxxx (FWBE) , and the SBI functions definition is firmware code base implementation-specific.
This also works for me and better than to reserve a range of IDs.
From: software@... [mailto:software@...]
On Behalf Of Jonathan Behrens
Sent: Friday, April 10, 2020 12:39 AM
To: Chang, Abner (HPS SW/FW Technologist) <abner.chang@...>
Cc: Atish Patra <Atish.Patra@...>; Anup Patel <anup.patel@...>; Schaefer, Daniel (DualStudy) <daniel.schaefer@...>; software@...; tech-unixplatformspec@...
Subject: Re: [RISC-V] [software] Add SBI extension space for firmware code base implementation
To address the PR itself, I'd personally prefer to have this space allocated based on SBI implementation IDs analogously to how the vendor space is allocated. It also probably makes sense to pick a different address range so experimental
extension space doesn't have to move.
On Thu, Apr 9, 2020 at 4:39 AM Abner Chang via
Seems opensbi ML is no longer exist? Use
Hi Atish and Anup,
We are working on some edk2-specific SBI extension which intends to be used by upper layer edk2 drivers. We originally consider to use Vendor Extension space however vendor may
have its own proprietary SBI extension as well. In order to prevent from the conflicts of SBI extension space, we propose to have a range for firmware code base. The changes look like the PR below,
How do you think?
Join firstname.lastname@example.org to automatically receive all group messages.