Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 351] New: create a "block" (mass) regfile port (read and write) onto an array-based regfile
Date: Mon, 25 May 2020 14:07:14 +0000
Message-ID: <bug-351-13@https.bugs.libre-soc.org/> (raw)

https://bugs.libre-soc.org/show_bug.cgi?id=351

            Bug ID: 351
           Summary: create a "block" (mass) regfile port (read and write)
                    onto an array-based regfile
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            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: ---

see soc.regfile.RegFileArray

for the Condition Regfile and for the XER Regfile, a "mass-hit" read/write
port is required that looks like a standard read_port (or write_port) however
permits writing to the *entire* regfile, all at once.

this can be done as a virtual port, as follows:

* create 8x read (or write) ports
* join all 8 data together as if they were a single thing
* join all 8 "enable" lines together as if they were a single thing

it will however be critical to ensure that the alternative "view" is not
used at the same time.

-- 
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

             reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 14:07 bugzilla-daemon [this message]
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
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@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