Reminder: Unix platform working group meeting (02/05 8AM PST) @ Wed Feb 5, 2020 8am - 9am (PST) When: Wednesday, 5 February 2020, 8:00am to 9:00am, (GMT-08:00) America/Los Angeles Where:webex View Eve

Reminder: Unix platform working group meeting (02/05 8AM PST) @ Wed Feb 5, 2020 8am - 9am (PST) When: Wednesday, 5 February 2020, 8:00am to 9:00am, (GMT-08:00) America/Los Angeles Where:webex View Eve

Unix platform working group meeting (02/05 8AM PST) @ Wed Feb 5, 2020 8am - 9am (PST) When: Wednesday, 5 February 2020 8:00am to 9:00am (GMT-08:00) America/Los Angeles Where: webex Description: Hi All

S-mode software needs a way to know memory used by SBI firmware so that it can correctly mark such memory as reserved. Related discussion: https://github.com/riscv/opensbi/issues/103 Signed-off-by: Bi

This patch adds SBI v0.2 compliant system reboot extension. It defines two functions: 1. sbi_reboot - A system reboot call with reboot type as parameter 2. sbi_shutdown - A system shutdown/poweroff ca

S-mode software needs a way to know memory used by SBI firmware so that it can correctly mark such memory as reserved. This patch was already posted on github as a PR [1], and I was told to send this

This patch adds SBI v0.2 compliant system reboot extension. It defines the sbi_system_reboot function which does different things based on reboot_type parameter: 1. shutdown - Power-off the entire sys

This patch adds SBI v0.2 compliant system reboot extension. It defines the sbi_system_reboot function which does different things based on reboot_type parameter: 1. shutdown - Power-off the entire sys

This patch adds SBI v0.2 compliant system reset extension. It defines the sbi_system_reset function which does different things based on reset_type parameter: 1. shutdown - Power-off the entire system

The SBI HFENCE VVMA calls use current VMID (in HGATP CSR) of calling HART for flushing TLB enteries. This fact is not clearly evident in current documentatation of HFENCE VVMA calls hence this patch i

Hi all, The SBI spec defines a standard set of error codes, which SBI functions can return in case of failure (or success). Each function defined in the SBI spec also defines which error codes it retu

From: Daniel Schaefer <git@...> Hi, I had opened a PR to SBI for adding a README: https://github.com/riscv/riscv-sbi-doc/pull/50 And now I'm also posting it here for people who might not have seen it

Signed-off-by: Daniel Schaefer <daniel.schaefer@...> --- README.adoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 README.adoc diff --git a/README.adoc b/README.adoc new f

Unix platform working group meeting (06/09 8AM PST) @ Tue June 09, 2020 8am - 9am (PST) When: Tuesday, 9 June 2020 8:00am to 9:00am (UTC-07:00) America/Los Angeles Where: webex Description: Hi, The ne

I joined the group recently and not sure that I have all the context yet for what the group's charter and current scope are. However, I was exchanging email with Andrew Waterman about RV32 cores and s

Reminder: Unix platform working group meeting (06/09 8AM PST) @ Tue June 09, 2020 8am - 9am (PST) When: Tuesday, 9 June 2020, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles Where:webex View Event D

Reminder: Unix platform working group meeting (06/09 8AM PST) @ Tue June 09, 2020 8am - 9am (PST) When: Tuesday, 9 June 2020, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles Where:webex View Event D

Hello, This email message is a notification to let you know that the following files have been uploaded to the Files area of the tech-unixplatformspec@... group. /Unix Platform specification working g

Hi All, I would like to start a thread to discuss the topics that should go into the unix platform specification apart from SBI & PLIC. SBI specification is already tagged as v0.2 & PLIC specification

I think tech-unixplatformspec@... might be the right list? To address the PR itself, I'd personally prefer to have this space allocated based on SBI implementation IDs analogously to how the vendor sp