From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] Function Units "patch-up" linking to Comp Unit code
Date: Sat, 23 May 2020 19:23:05 +0100
Message-ID: <CAPweEDyo_FNgRXAEt2x0ZY0aaCbH9ukVKh_PEsLkPhTfGtbYMQ@mail.gmail.com> (raw)
right. finally. with regspecs in place, and the pipelines in place,
*finally* we can link them up together:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/compunits.py;hb=HEAD
MultiCompUnit has been "morphed" to be completely FSM / Pipeline
agnostic. it knows *nothing* about the data it's dealing with: names
or quantity of input signals, names or quantity of output signals,
absolutely nothing. (oh, Cesar, Michael: except for the fact that RA
can be zero, and RB can be an immediate).
the *only* way to tell MultiCompUnit the information about the ALU
it's been asked to look after: regspecs. i've documented the format,
here:
https://libre-soc.org/3d_gpu/architecture/regfile/
any questions please ask.
l.
_______________________________________________
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: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAPweEDyo_FNgRXAEt2x0ZY0aaCbH9ukVKh_PEsLkPhTfGtbYMQ@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