Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update, 21jul2020
Date: Tue, 21 Jul 2020 14:33:27 -0700
Message-ID: <CAEg7hu=rbqS=tjmW=OBGw5fYaixLr=LOcsvnJ09aO-uh4VVwLA@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDxiv-YfodPv6ZaU9o5D2Hm+ui7tbf4T3jhXbiZ82XRqFA@mail.gmail.com>

Last week:

* worked on coriolis2 chroot setup script (very slow going as it
requires >5 GIGAbytes of downloads each test)

Today:

* finish coriolis2 chroot setup script and HDL_Workflow/coriolis2 wiki
documentation
* work on finishing the setup CI testing on jacob's build server so we
know pretty quickly when there are dependency and version problems

Jacob, what is left to do in order to get the build server into a
shape that we will be happy with/will be useful?

I referred back to the original bug report "Bug 190 - Setup Gitlab CI
Runner for Kazan on a computer"
<https://bugs.libre-soc.org/show_bug.cgi?id=190> but the last comment
on that seems to be from before gitlab was even setup on the server.
Can you either point me to the current bug report for this, or leave a
comment on this old one with the steps I need to complete to finish
setting up our testing infrastructure?

Cole

On Tue, Jul 21, 2020 at 10:02 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> tasks:
>
> https://bugs.libre-soc.org/showdependencytree.cgi?id=383&maxdepth=1&hide_resolved=1
>
> yesterday:
>
> * nmigen bi-weekly meeting, went well.
> * reviewed trap with help from samuel
> * set up core to be better started from litex
> * did a first cut litex core.py with help from florian
> * re-ran cxxsim, confirmed a bug with help from cesar.
>
> today:
>
> * helped JeanPaul get up-to-date
> * fixed missing exception MSR bit setting
> * decided to move both MSR and CIA into "state"
> * found a bug in CompALUMulti when it has no regs to read.
>
> this latter will need a special test case for, and some investigation.  so
> that is the rest of the day.
>
> 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

_______________________________________________
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: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 17:02 Luke Kenneth Casson Leighton
2020-07-21 21:33 ` Cole Poirier [this message]
2020-07-22  9:08   ` Luke Kenneth Casson Leighton
2020-07-22 22:36     ` Cole Poirier
2020-07-22 23:43       ` 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='CAEg7hu=rbqS=tjmW=OBGw5fYaixLr=LOcsvnJ09aO-uh4VVwLA@mail.gmail.com' \
    --to=colepoirier@gmail.com \
    --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