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 08jun2020
Date: Mon, 8 Jun 2020 14:17:28 -0700
Message-ID: <E0FB3D82-BADB-4C2D-B179-FA45B5FD90D0@getmailspring.com> (raw)
In-Reply-To: <CAPweEDyeAQzR=R3EkAKHnKmHwQmHOmZCokyFN=WxKxCr2tFvRQ@mail.gmail.com>

On Jun 8 2020, at 1:08 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> yesterday:
> 
> * worked with Cole on TRAP
> * fixed the Condition Register MFCR bug
> * started on XER testing
> * reviewed the IoT pitch

Thank you so much for this Luke, the discussion you had on-list with our
less frequently commenting members (because they have full time jobs),
who are incredibly technically capable was phenomenally helpful.
 
> today:
> 
> * dealt with yet another massive headache.
> * fixed XER SO/OV/OV32 handling (simulator and test_core)
> 
> going to take it easy for the rest of the day, return to LDST CompUnit
> testing tomorrow.
> 
> l.

I'm very sorry to hear you're suffering from massive headaches, several
of my family members suffer from migraines, I know it's very unpleasant.

Today I think I need to focus exclusively on the pitch because the
deadline is so close and there is currently so much missing info.

I'm planning on taking the discussion on list, and the comments on the
pitch on the wiki and coming up with a new pitch specific to these
discussions. 

I'm going to spend the next two hours trying to take all of the
technical aspects of the pitch and put them into a coherent form with my
understanding of the technical aspects. Then I'll send this to the list
so that you and others can reply and correct inline.

I'll try to put just a few very specific questions (such as the
advantages/high level summary of Simple-V) for you and other technical
project members to answer. I would try answer this myself given your
present state, but unfortunately I don't think I can understand and
explain something like Simple-V on my own in a day.

Can I ask you to see if you're able to answer some of these questions
today, if your illness permits? I hate to ask you while you're sick, but
I think the pitch will really suffer without your technical input...


Thank you,

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: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 20:08 Luke Kenneth Casson Leighton
2020-06-08 21:17 ` Cole Poirier [this message]
2020-06-08 22:13   ` Luke Kenneth Casson Leighton
2020-06-08 22:29     ` Cole Poirier

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=E0FB3D82-BADB-4C2D-B179-FA45B5FD90D0@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