From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 329] New: coriolis2 experiment layout for Dependency Matrices
Date: Wed, 20 May 2020 12:18:35 +0000
Message-ID: <bug-329-13@https.bugs.libre-soc.org/> (raw)
https://bugs.libre-soc.org/show_bug.cgi?id=329
Bug ID: 329
Summary: coriolis2 experiment layout for Dependency Matrices
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Hardware Layout
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
Created attachment 57
--> https://bugs.libre-soc.org/attachment.cgi?id=57&action=edit
quick preliminary test ilang from soc/scoreboard/test_mem_fu_matrix.py
we need a quick example to demonstrate how the Dependency Matrices would
look so that coriolis2 can do the layout in a regular fashion. this
even though they may convert from DFF to SRNAND, so the layout needs to
be dynamic, rather than explicit naming of cells.
also, some of the cells may be augmented by additional "setting" logic
that needs to go into every row (not yet written), so any explicit
manually-created layout that hunts for explicit cell names is going to
have to be redone, and not only redone, duplicated manual work several
times.
this is why the idea exists to identify sub-groups of cells by way of
netlist path analysis, and have them placed by Etesian in regular grid
fashion.
--
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: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 12:18 bugzilla-daemon [this message]
2020-05-20 12:20 ` [libre-riscv-dev] [Bug 329] " bugzilla-daemon
2020-05-20 12:20 ` bugzilla-daemon
2020-05-20 12:30 ` bugzilla-daemon
2020-05-20 12:33 ` bugzilla-daemon
2020-05-20 12:33 ` bugzilla-daemon
2020-05-20 12:34 ` bugzilla-daemon
2020-05-20 12:41 ` bugzilla-daemon
2020-05-22 11:13 ` bugzilla-daemon
2020-05-22 13:35 ` bugzilla-daemon
2020-05-22 13:53 ` bugzilla-daemon
2020-06-03 22:00 ` bugzilla-daemon
2020-06-03 22:18 ` bugzilla-daemon
2020-06-06 10:41 ` bugzilla-daemon
2020-06-06 11:20 ` bugzilla-daemon
2020-06-06 11:23 ` bugzilla-daemon
2020-06-06 12:23 ` bugzilla-daemon
2020-06-06 12: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-329-13@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.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