Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Needed Subset of POWER
Date: Sun, 3 May 2020 00:34:52 +0100
Message-ID: <CAPweEDxCyrZO1UMUxWR4-_0DbTywmtu8D_nkidZ8Y0tmrDL3Ow@mail.gmail.com> (raw)
In-Reply-To: <C838DC92-64B8-4FD3-A6FE-C45F4444761D@gatech.edu>

On Saturday, May 2, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> Hello all,
>         I’m reading through the Power ISA manual. What subset of POWER are
> we doing for the first single core revision?


not vector, that's for sure.  it's half the 1200 pages.  we do however need
to come up with an interoperability  solution for not having them.


>
> What is the minimal subset of POWER that we can get away with for an
> operational Linux kernel?


a GPIO subsystem, interrupts, MMU (RADIX), integer, branch, LD/ST,
hypervisor, SPRs, and a little bit more.

FP not needed.  see power-gem5 simulator branch.  am on phone. links in
bugzilla somewhere.  search "gem5".


> There are lots and lots of features such as:
>
> ```
> Decimal Floating-Point Support Operations: Add imme- diate forms of DFP
> Test Significance instructions.


not that.  not transactions, either


> ```
>
> Do we have to implement all these “icing” instructions eventually to be
> POWER certified?


i hear this is still being decided.

i do not speak for the Foundation, my understanding is, it will probably be
*guided* by what microwatt can reasonably implement.

asking IBM is unfortunately not quite... how can i put it.... because they
have incrementally got to such a staggering level of functionality over so
many years i'm not quite certain that they are truly aware how high the bar
has become.

microwatt and chiselwatt development will help them to appreciate that.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 22:07 Yehowshua
2020-05-02 23:34 ` Luke Kenneth Casson Leighton [this message]

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=CAPweEDxCyrZO1UMUxWR4-_0DbTywmtu8D_nkidZ8Y0tmrDL3Ow@mail.gmail.com \
    --to=lkcl@lkcl.net \
    --cc=libre-riscv-dev@lists.libre-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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git