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] Markdown on the wiki?
Date: Sat, 18 Jul 2020 03:39:26 +0100
Message-ID: <CAPweEDxVHBDzw8J99oPsvup0FF=mnw6DAAWfsDZX9-CuAr0jQw@mail.gmail.com> (raw)
In-Reply-To: <CAEz=son7=jtCP-XsJOR15e65zy4dSe93OmjZc-YhV8B8KeNMYA@mail.gmail.com>

On Saturday, July 18, 2020, Samuel Falvo II <sam.falvo@gmail.com> wrote:

>
> I can appreciate why people say that being "retired" is exhausting.  ;)


my aunt kicked my uncle out, told him to go back to work when he retired.
he was too annoying :)


> Yeah, and I'm getting a lot of ideas for my future KCP53000
> refinements as well.  In *theory*, it should be possible to use the
> exact same combinatorial building blocks in a single-issue design as
> it would in a pipelined, multi-issue design;


precisely.  increase the number of pipelines, increase the register ports
and data bandwidth and aside from deoendency tracking that's pretty much it.


>
> only the wiring between
> the blocks would need to be handled differently.


i originally designed a way to use the same blocks for FSMs as well as
pipelines.  it was difficult to maintain, unfortunately.

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: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEz=somu-i6og_eQZ51WbbLSe8spGAzEHiXUiDAY6=gdx1vFOg@mail.gmail.com>
2020-07-15 10:05 ` Luke Kenneth Casson Leighton
2020-07-15 10:47   ` Luke Kenneth Casson Leighton
2020-07-15 17:12     ` Luke Kenneth Casson Leighton
2020-07-18  1:19       ` Samuel Falvo II
2020-07-18  2:39         ` 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='CAPweEDxVHBDzw8J99oPsvup0FF=mnw6DAAWfsDZX9-CuAr0jQw@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