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 13jul2020
Date: Mon, 13 Jul 2020 12:47:12 -0700
Message-ID: <CAEg7humyhx=ymYgyJoWjaE1KaVe3+JMmL7JEF5GFxxsOX_+mQg@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD5-QHbzEp774PGTZF7=hPsV4PS2Y5Qx6vfTBXKtZyLSfw@mail.gmail.com>

Yesterday:

* Updated dev-env-setup/hdl-dev-repos script to correctly set up nmigen-soc
* Started working on bringing
https://libre-soc.org/HDL_workflow/coriolis2/ up to date with
dev-env/setup/coriolis2-chroot

Today:

Continue working on updating the wiki documentation for setup of dev
environments. Luke I plan on also working on the alliance and
alliance-check-toolkit sections, as well as creating a section for
documenting our soclayout workflow. As far as I can tell this isn't
documented on the wiki, and I think it's important to have it well
documented as we are now ramping up the layout work with JP. I've
mostly been able to iron out the bugs in that workflow, but I may need
some help with configuration parameters, so I will comment on 'Bug 291
- HDL Workflow and Coriolis2 chroot automated setup scripts'
<https://bugs.libre-soc.org/show_bug.cgi?id=291> with my questions.

Cole

_______________________________________________
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: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 15:40 Luke Kenneth Casson Leighton
2020-07-13 18:36 ` Tobias Platen
2020-07-13 19:35   ` Jacob Lifshay
2020-07-13 19:47     ` Cole Poirier [this message]
2020-07-13 22:09       ` Luke Kenneth Casson Leighton
  -- strict thread matches above, loose matches on Subject: below --
2020-06-13 14:48 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='CAEg7humyhx=ymYgyJoWjaE1KaVe3+JMmL7JEF5GFxxsOX_+mQg@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