linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <Christoph.Hellwig@wdc.com>
To: "sw-dev@groups.riscv.org" <sw-dev@groups.riscv.org>,
	"palmer@sifive.com" <palmer@sifive.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"hw-dev@groups.riscv.org" <hw-dev@groups.riscv.org>,
	"isa-dev@groups.riscv.org" <isa-dev@groups.riscv.org>
Cc: Atish Patra <Atish.Patra@wdc.com>
Subject: Re: [isa-dev] Re: UNIX-Class Platform Specification Working Group
Date: Sun, 7 Apr 2019 07:36:22 +0000	[thread overview]
Message-ID: <c1ea959e9114929b72f5b3d687e70429a3737d25.camel@wdc.com> (raw)
In-Reply-To: <CANs6eMn4+6XGaSOGyWoD5RK2DjQo2SUUHphqmL_dwQD-Xu-omQ@mail.gmail.com>

On Fri, 2019-04-05 at 08:43 -0700, Palmer Dabbelt wrote:
> Sorry for the delay, but it appears we now have a mailing list set
> up!  I managed to announce the group right in the middle of the
> workspace -> groups.io transition, which means we're the first group
> to try out the new infrastructure.  As a result there may be some
> wrinkles, but at least a handful of us can get into the group so with
> any luck it'll work for anyone else.
> 
> You should be able to join here: 
> https://lists.risc-v.org/g/tech-unixplatformspec/topics .  Just like
> the other RISC-V specs, you'll need to be a member of the RISC-V
> foundation to contribute to the platform specification -- sorry if
> there was some confusion in my original email.

So in the past the way to join was through workspace.riscv.org - but
login in there just returns an internal server error.  Has lists.risc-
v.org replaced the above infrastructure or is it in addition?

> 
> On Tue, Apr 2, 2019 at 9:50 AM Palmer Dabbelt <palmer@sifive.com>
> wrote:
> > Atish and I have approval from the RISC-V technical committee and
> > board to 
> > start a group to manage the UNIX-class platform specification. 
> > This working 
> > group will start by defining a subset of this platform
> > specification that both 
> > allows compatibility with existing implementations and
> > extensibility for the 
> > future needs.  The contents of this first platform specification
> > will include:
> > 
> > * A versioning scheme for future versions of the UNIX-class
> > platform 
> >   specification.
> > * A specification for a platform-level interrupt controller that is
> > compatible 
> >   with existing implementations of SiFive's PLIC.
> > * A specification for a standard SBI that is compatible with the
> > current 
> >   implementation in Linux as well being extensible for future
> > needs.
> > * An SBI extension for CPU power management.
> > * A specification of the interface between a bootloader and
> > supervisor-mode 
> >   software.
> > 
> > Since this working group mostly consists of standardizing existing 
> > implementations, I hope it can progress quickly.  As such, I'd like
> > to set a 
> > 6-month deadline between when the working group is started (ie,
> > today) and when 
> > a specification enters the 45-day review period.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2019-04-07  7:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 16:50 UNIX-Class Platform Specification Working Group Palmer Dabbelt
2019-04-02 17:38 ` [isa-dev] " Luke Kenneth Casson Leighton
     [not found] ` <CABwTF4UW8YePYr9Ad65VSvef4-Y42VEvNUs=hPWyWcyH295zCw@mail.gmail.com>
2019-04-03  0:31   ` [hw-dev] " Luke Kenneth Casson Leighton
2019-04-03  2:43     ` Palmer Dabbelt
2019-04-03  3:34       ` Luke Kenneth Casson Leighton
2019-04-03  4:13       ` Luke Kenneth Casson Leighton
2019-04-03  4:48         ` Luke Kenneth Casson Leighton
2019-04-03  1:53   ` Palmer Dabbelt
2019-04-03  2:39     ` Luke Kenneth Casson Leighton
     [not found] ` <CANs6eMn4+6XGaSOGyWoD5RK2DjQo2SUUHphqmL_dwQD-Xu-omQ@mail.gmail.com>
2019-04-07  7:36   ` Christoph Hellwig [this message]
2019-04-07 15:30     ` [isa-dev] " Jim Wilson
2019-04-08  6:50     ` Atish Patra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c1ea959e9114929b72f5b3d687e70429a3737d25.camel@wdc.com \
    --to=christoph.hellwig@wdc.com \
    --cc=Atish.Patra@wdc.com \
    --cc=hw-dev@groups.riscv.org \
    --cc=isa-dev@groups.riscv.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=sw-dev@groups.riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).