I updated the subject to include the time (8AM PST). I also updated the calendar invite. So everybody's calendar should be updated with the google meet link instead of Zoom. FYI: The calendar in group

Just for reference: https://github.com/riscv/riscv-platform-specs/blob/master/riscv-unix.adoc - Paul

On Thu, Sep 24, 2020 at 7:50 AM Al Stone <ahs3@...> wrote: On 22 Sep 2020 21:51, Greg Favor wrote: > On Tue, Sep 22, 2020 at 9:02 AM Al Stone <ahs3@...> wrote: > We should make sure there is a clear w

The nice thing about standards is that you have so many to choose from. - attributed to Andy Tanenbaum Western Digital engineers have proposed that the RISC-V Unix platform specification working group

Hi All, Here's the agenda for first hypervisor sync-up call: 1. KVM RISC-V TODO list (20 mins) 2. Suggestions on priorities and future directions for KVM RISC-V software efforts 3. Open floor In gener

The following files have been uploaded to the Files area of the tech-unixplatformspec@... group. /RISC-V Platform Spec (2020-09-24 at 08 05 GMT-7).mp4 By: Al Stone Description: Recording of the Platfo

Some key items to note: we will be experimenting with Google Meet this meeting to improve inclusivity; that means the Zoom meeting will NOT be used. Second, I think we need to step up the meeting cade

Hi Anup, I have gained a lot from your information. Thank you very much. > 1. SBI HSM HART SUSPEND call (with a parameter to specify platform specific CPU idle power mode) In addition to "power_state"

Hi ALL, Since there is no extension in the specification that can apply to the cpuidle module now, I propose adding a new extension as Aunp also mentioned in the linux mailing list. The new extension

Hi All, Here are the high-level points discussed in the meeting: 1. General idea behind hypervisor sync-up call 2. Detailed KVM RISC-V TODO list (mention below for reference) 3. The KVM RISC-V can onl

Based on the survey, it looks like 09:00 PST (16:00 UTC) on Monday is a "reasonable" time to hold the TG meetings, for various definitions of reasonable. So, I've changed the calendar entry in tech gr

Here's the latest proposal for the Platform Spec charter; it can also be found at: https://github.com/riscv/riscv-platform-specs/wiki/Draft-Charter A little wordier than I'd like, I suppose, but I thi

While a README is not required, github uses them to provide a nice way to describe the basic purpose of the repository. This proposal is to just add a simple one; the text to be added is below, in mar

This is really just an etiquette question: do the folks on this mailing list prefer things inline or as attachments? I was just getting ready to send out a 202 line asciidoc file as a proposal for the

# Platform Spec Task Group Agenda: 12 Oct 2020 ## Meeting Info: weekly on Mondays (09:00 PST, 16:00 UTC) https://meet.google.com/nox-fhqz-owe Details: https://sites.google.com/a/riscv.org/risc-v-staff

Now that there's a makefile, add a .gitignore to make it simpler to see only the artifacts pertinent to the repo. Signed-off-by: Al Stone <ahs3@...> --- .gitignore | 4 ++++ 1 file changed, 4 insertion

Given the .adoc file, transform it into PDF, markdown, and HTML formats. Provide targets for cleaning up afterwards, as well as for installing useful packages (NB: the package install targets are not

Start filling in some of the blanks in the original asciidoc structure such as document title, author, and revision information. NB: this always seems to look better in PDF format; the others are fine

This will be autogenerated when the document is built. Signed-off-by: Al Stone <ahs3@...> --- riscv-platform-spec.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/riscv-platform-spec.adoc b/r

Move licensing and copyright information out of the primary document file. The idea is make it easier to patch the document in the future. Signed-off-by: Al Stone <ahs3@...> --- Makefile | 2 +- licens