From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] daily kan-ban update 22may2020
Date: Fri, 22 May 2020 16:02:25 +0100
Message-ID: <CAPweEDwtA3H9yP0JGQ2CvoR0ZbT0O2hasTbqam+tw7zQmKJ=Dg@mail.gmail.com> (raw)
little late. yesterday and this morning
* helped Michael go over the Condition Register pipeline reorg. the CR
regfile is to be split into 8 4bit registers rather than one massive 32 bit
one
* sorted new CR register allocation scheme for when we put a CompUnit in
front of it
* described to Cesar the design mod requirements to ALUCompUnit needed: to
add selection of RA being a zero immediate and to bypass RD.REQ[0] when
that happens.
* added a zero_a flag to Decode2ExecuteType to support that
* reorganised the soc.fu code a little after separating out the op subsets
CompBrOpSubset etc
* cookie cut shiftreg and logical to soc.fu.mul and soc.fu.div
respectively, and placed some stub code for replacing with ieee754fpu
pipeline stages, for Jacob
* helped Jean-Paul in understanding the FU-FU Dependency Matrix so he can
do a layout experiment in coriolis2
* attended both OpenPOWER weekly coffee calls which were nice to do,
especially learning about microwatt first boot and also what Cesar does.
both very cool.
y'know... i have to say, i am not often aware at the time because i take
breaks and binge watch series episodes (Stargate SG1 at present, but only
because i ran out of American Ninja Warrior episodes), but each day when
actually written out does seem to be one hell of a lot. this probably
because i don't do anything else, the entire day.
anyway.
todo:
* draw out a new ALUCompUnit diagram for documentation purposes
* keep an eye out for Cole. i couldn't work it out, either. might need
your help, Michael.
* keep thinking through the multi comp unit data structures.
* answer issues as they come up
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
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: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 15:02 Luke Kenneth Casson Leighton [this message]
2020-05-22 15:19 ` Michael Nolan
2020-05-22 15:39 ` Luke Kenneth Casson Leighton
2020-05-22 19:10 ` Cole Poirier
2020-05-22 19:18 ` Tobias Platen
2020-05-22 19:33 ` Luke Kenneth Casson Leighton
2020-05-23 1:56 ` Cesar Strauss
2020-05-23 2:41 ` Luke Kenneth Casson Leighton
2020-05-23 10:24 ` Cesar Strauss
2020-05-23 11:03 ` Luke Kenneth Casson Leighton
2020-05-23 11:53 ` Cesar Strauss
2020-05-23 12:08 ` Luke Kenneth Casson Leighton
2020-05-23 18:16 ` Cole Poirier
2020-05-22 19:59 ` Jacob Lifshay
2020-05-22 20:04 ` Luke Kenneth Casson Leighton
2020-05-22 20:12 ` Luke Kenneth Casson Leighton
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='CAPweEDwtA3H9yP0JGQ2CvoR0ZbT0O2hasTbqam+tw7zQmKJ=Dg@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