From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 215] New: evaluate minerva for base in libre-soc
Date: Wed, 11 Mar 2020 14:31:19 +0000
Message-ID: <bug-215-13@http.bugs.libre-riscv.org/> (raw)
http://bugs.libre-riscv.org/show_bug.cgi?id=215
Bug ID: 215
Summary: evaluate minerva for base in libre-soc
Product: Libre Shakti M-Class
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
https://github.com/lambdaconcept/minerva
looks really good: clean design, uses wishbone to the L1 caches and
to the main core. this will help when it comes to adding SMP down
the line. the decoder is also very clean.
the only non-obvious bit is how the core works, with source/sink
being created in class "Stage" (which is fine), and with the
inter-transfer layouts being the same (source on previous stage
equals sink on the next stage), that's obvious: the bit that's
not obvious is what-gets-connected-to-what.
i think this is because "sinks" are set up at the start of core.py
whilst "sources" are set up much further down. in the libre-soc
pipeline code, the layouts are done via objects, and the modules
"take care" of placing data into the "output" inherently. here,
it's messy, and the separation makes understanding difficult.
other than that, though, it's pretty damn good.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 14:31 bugzilla-daemon [this message]
2020-03-11 14:36 ` [libre-riscv-dev] [Bug 215] " bugzilla-daemon
2020-03-11 14:50 ` bugzilla-daemon
2020-03-11 15:06 ` bugzilla-daemon
2020-03-11 15:37 ` bugzilla-daemon
2020-03-11 19:25 ` bugzilla-daemon
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=bug-215-13@http.bugs.libre-riscv.org/ \
--to=bugzilla-daemon@libre-riscv.org \
--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