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>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 20may2020
Date: Wed, 20 May 2020 07:50:54 -0700
Message-ID: <0777688C-B036-4939-8F33-338E05D1B6EC@getmailspring.com> (raw)
In-Reply-To: <CAPweEDxxHh-1kjXtP-ZB-u5AoGE8b1+zt6XmqVVe1fHTtw5bEA@mail.gmail.com>

On May 20 2020, at 7:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> yesterday:
> * more pipeline stuff with michael and cole and jacob.  researched
> TRAP ops in particular

Yesterday I learned another valuable lesson on the merits of the KISS
philosophy. Today I plan on integrating the Bpermd module into the
logical pipeline, with tests.

> * talked with Marketnext about the resource requirements for the May
> 30 Hackathon.

Is there a document about this on the wiki? If not would you mind
briefly explaining what the parameters and the objectives of the
hackathon are?

> * received a message from these guys, they would like to do a review
> https://radicallyopensecurity.com/

Just took a quick perusal of their website, they look like they share
our philosophy about digital rights, as well as having a
'social-benefit-esque' organizational model. I think their doing a
review of our processor's security would be welcome help. Your thoughts?

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: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 14:14 Luke Kenneth Casson Leighton
2020-05-20 14:50 ` Cole Poirier [this message]
2020-05-20 15:14   ` Luke Kenneth Casson Leighton
2020-05-20 19:34     ` Cole Poirier
2020-05-20 19:44       ` Luke Kenneth Casson Leighton
2020-05-20 15:50 ` Michael Nolan
2020-05-20 16:23   ` 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=0777688C-B036-4939-8F33-338E05D1B6EC@getmailspring.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