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] CORDIC importance
Date: Tue, 5 May 2020 19:25:04 +0100
Message-ID: <CAPweEDxGb9mrjE4s7g2_E5s9ae=8y8ZEaUWMDcXsjP-Hj53aug@mail.gmail.com> (raw)
In-Reply-To: <e520ea72-aa03-a844-bb54-3d3db177bd99@gmail.com>
On Tue, May 5, 2020 at 6:33 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> Luke,
>
> I know we're tight on time for the tapeout in October. Is there
> something that would be better for me to work on right now than the cordic?
actually probably yes - although we do really need SIN, COS (etc.)
* cyclic buffer for the regfile. https://bugs.libre-soc.org/show_bug.cgi?id=296
* simulator (still needed, to "track" the hardware so i know what to
design!) in particular, the branch unit. which first needs carry-in
and carry-out (CR0 etc.)
* an actual pipelined ALU, that expands on the alu_hier.py concept and
adds more functions - however it also needs to use PartitionedSignal.
this can default to "all off" initially.
* a 128-to-64 Wishbone Arbiter. take in 128 bit read/write requests,
split them into 2 separate 64-bit Wishbone read/write requests, but
use a bit per half (HI-64, LO-64) to indicate "we do or do not" need
this half to go out.
later (not much later) we will need:
* a RADIX MMU lookup system (POWER-compliant)
* a TLB that caches RADIX lookups
you're almost certainly going to find a nmigen or migen Wishbone
Arbiter out there somewhere already, there may even be one in minerva
already.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
prev parent reply index
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 17:33 Michael Nolan
2020-05-05 18:25 ` 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='CAPweEDxGb9mrjE4s7g2_E5s9ae=8y8ZEaUWMDcXsjP-Hj53aug@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