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 12:34:26 -0700
Message-ID: <0220ADD2-E2B5-4DEB-A7CF-3E33F506BD4F@getmailspring.com> (raw)
In-Reply-To: <CAPweEDy9K+qhLMoet5s=_yCHp1m5ay7FcKL+VK8PVffH1axRRg@mail.gmail.com>
On May 20 2020, at 8:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Wed, May 20, 2020 at 3:51 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
>> Yesterday I learned another valuable lesson on the merits of the KISS
>> philosophy.
>
> funny man :)
>
>> Today I plan on integrating the Bpermd module into the
>> logical pipeline, with tests.
>
> fooocuuuus :) adding the module to Logical main_stage.py should be
> around... maximum 10 lines of code. really. not. difficult. link
> the inputs. link the outputs. err... that's it.
>
> btw as a third (incremental) step, after integrating it and putting in
> the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
> actually be able to integrate the formal proof into the Logical
> pipeline as well.
Will copy this to and comment on it at https://bugs.libre-soc.org/show_bug.cgi?id=316.
>> > * talked with Marketnext about the resource requirements for the May
>> > 30 Hackathon.
>>
>> Is there a document about this on the wiki?
>
> there isn't. there should be. however it is up to Marketnext. the
> issue is that i am not sure if they understand quite how high the
> resource requirements are, and consequently how long it will take
> people in India (and other places across the world) to install the
> development environment.
Ah that's an interesting constraint. Would it be possible (or even
desirable) to provide them with a compressed archive of all the
necessary repos, tools, etc in a frozen state?
>> If not would you mind
>> briefly explaining what the parameters and the objectives of the
>> hackathon are?
>
> to introduce over 15 different groups / teams / individuals to
> Libre-SOC development.
That's pretty darn cool!
>> > * 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?
>
> their review is a mandatory requirement as part of the NLNet funding.
> i did point out to them that asking to have a private conversation
> about their role is not exactly very transparent :)
>
> l.
Oh, very happy that this turns out to be a mandatory NLNet funding
requirement. I agree that their request for private conversation is odd
given the context.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent 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
2020-05-20 15:14 ` Luke Kenneth Casson Leighton
2020-05-20 19:34 ` Cole Poirier [this message]
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=0220ADD2-E2B5-4DEB-A7CF-3E33F506BD4F@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