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] [Bug 178] first coriolis2 tutorial, workflow and "test project" page
Date: Fri, 13 Mar 2020 09:21:24 -0700
Message-ID: <5FCB1EF4-D26B-4BB9-96B7-91BB8C51669D@gmail.com> (raw)
In-Reply-To: <bug-178-13-wRaOniTOh1@http.bugs.libre-riscv.org/>

> On Mar 12, 2020, at 10:26 AM, bugzilla-daemon@libre-riscv.org wrote:
> 
> http://bugs.libre-riscv.org/show_bug.cgi?id=178
> 
> --- Comment #210 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> for this one, i'm going to suggest:
> 
> * EUR 250 to jock for the (crucial) questions and for helping get to buster 
> * EUR 200 to tobias for the early checking of the tutorial
> * EUR 700 to be donated to LIP6.fr for the huge amount of bugfixing by JP
> * EUR 150 to Staf for his insights
> * EUR 1200 to me for the persistent head-banging against brick walls
> 
> Cole, as long as you are in Europe, you helped find some early bugs in the
> tutorial page, and made some useful edits, however if you are outside of
> Europe, most of what NLNet would transfer to you would go in banking fees.  we
> can if you like work something out.

Thank you for the consideration Luke, even though I have yet to add my discoveries to the wiki. I reside in Vancouver, Canada so a donation to me would be a waste of the funding we have, in addition I really don’t want to be paid for anything unless it is a substantial contribution to the core of the project (i.e. something that will end up in silicon). Apologies for my lack of communication, I recently started my first career-level job and I’m still in the process acclimating to my new circumstances. That being said, I was able to progress further with the coriolis2 tutorial last weekend, and I plan on trying to repeat this and document it tomorrow. I will edit the wiki with my successful installation steps, and reply here when I inevitably get stuck. Additionally, I plan on setting up and configuring Jacob’s gitlab dev server this weekend. I will leave a reply on the relevant thread.

Best,
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: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-178-13@http.bugs.libre-riscv.org/>
2020-03-11 12:35 ` bugzilla-daemon
2020-03-11 12:45 ` bugzilla-daemon
2020-03-11 12:59 ` bugzilla-daemon
2020-03-11 14:51 ` bugzilla-daemon
2020-03-11 15:35 ` bugzilla-daemon
2020-03-12 11:23 ` bugzilla-daemon
2020-03-12 11:48 ` bugzilla-daemon
2020-03-12 16:15 ` bugzilla-daemon
2020-03-12 17:14 ` bugzilla-daemon
2020-03-12 17:25 ` bugzilla-daemon
2020-03-13 16:21   ` Cole Poirier [this message]
2020-03-15 19:57 ` bugzilla-daemon
2020-03-18 14:38 ` bugzilla-daemon
2020-03-18 15:18 ` bugzilla-daemon
2020-03-18 22:47 ` bugzilla-daemon
2020-03-18 23:41 ` bugzilla-daemon
     [not found] <bug-178-13@https.bugs.libre-soc.org/>
2020-04-21 21:00 ` bugzilla-daemon
2020-04-21 21:09 ` bugzilla-daemon
2020-04-21 21:15 ` bugzilla-daemon
2020-04-21 21:28 ` bugzilla-daemon
2020-04-21 21:30   ` Luke Kenneth Casson Leighton
2020-04-21 21:35     ` 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=5FCB1EF4-D26B-4BB9-96B7-91BB8C51669D@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