From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 351] create a "block" (mass) regfile port (read and write) onto an array-based regfile
Date: Tue, 26 May 2020 01:45:41 +0000
Message-ID: <bug-351-13-lZsxkrIkf6@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-351-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=351
Cole Poirier <colepoirier@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |colepoirier@gmail.com
--- Comment #4 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=HEAD
>
> saw this.
Thanks! I'm trying to get something down, so I don't freeze because there are
multiple things I don't understand.
>
> i think... actually... the list of ports in the constructor, have to be
> done manually, then those wired via a mux to the "real" ports
>
> so a for loop adds RecordObjects
>
> ren=1, data=bitwidth/nregs
>
> then appends an *extra* on
> ren=nregs, data=bitwidth
Pushed a commit with this change, not sure if it's exactly right yet.
>
> then in the constructor:
>
> * test port[-1].ren == 0
>
> * if zero then for all ports 0 to nregs, connect *internal* port to external
> port
>
> * else put bitwidth/nregs bits of port[-1].data onto port[loopindex].data
> and also do same with enable bits.
Can you help me undestand how I should set the interal and external ports up in
the __init__() function? I'm lost here as to how these should be represented in
code.
--
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 prev parent reply index
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 14:07 [libre-riscv-dev] [Bug 351] New: " bugzilla-daemon
2020-05-25 23:55 ` [libre-riscv-dev] [Bug 351] " bugzilla-daemon
2020-05-26 1:18 ` bugzilla-daemon
2020-05-26 1:34 ` bugzilla-daemon
2020-05-26 1:45 ` bugzilla-daemon [this message]
2020-05-26 2:03 ` bugzilla-daemon
2020-05-26 2:08 ` bugzilla-daemon
2020-05-26 2:09 ` bugzilla-daemon
2020-05-26 4:07 ` bugzilla-daemon
2020-05-26 12:54 ` bugzilla-daemon
2020-05-26 16:01 ` bugzilla-daemon
2020-05-26 16:41 ` bugzilla-daemon
2020-05-26 22:20 ` bugzilla-daemon
2020-05-26 23:17 ` bugzilla-daemon
2020-05-26 23:20 ` 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-351-13-lZsxkrIkf6@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