From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Staf Verhaegen <staf@fibraservi.eu>
Cc: "Linux on small ARM machines" <arm-netbook@lists.phcomp.co.uk>,
"libresilicon-developers@list.libresilicon.com"
<libresilicon-developers@list.libresilicon.com>,
"Discussão do LibrePlanet" <libreplanet-discuss@libreplanet.org>,
"Libre-RISCV General Development"
<libre-riscv-dev@lists.libre-riscv.org>,
"Hagen SANKOWSKI" <hsank@posteo.de>
Subject: Re: NLNet Funding Proposals for the Libre RISC-V SoC: call for participation
Date: Wed, 25 Sep 2019 17:16:17 +0800 [thread overview]
Message-ID: <CAPweEDxC5=HirMkz4e976iAPRpz3o6KGRnk4HQtXRugrNXwO4Q@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDzK_r1HryWJCX3-q0TZ9MDE__uLgUO5Xji_YXe8TEu61g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 525 bytes --]
https://libre-riscv.org/nlnet_2019_wishbone_streaming/
Hagen we do not have much time left before Oct 1st so I just very quickly
filled in some paragraphs. It is more important to get something in that
is brief and short, they will ask questions during the review process.
If you can let me know, if you are happy with the above, or feel free to
edit it direct?
If anyone has any suggestions on anything else to add do say so [soon!]
L.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
[-- Attachment #1.2: Type: text/plain, Size: 682 bytes --]
[1]https://libre-riscv.org/nlnet_2019_wishbone_streaming/
Hagen we do not have much time left before Oct 1st so I just very
quickly filled in some paragraphs. It is more important to get
something in that is brief and short, they will ask questions during
the review process.
If you can let me know, if you are happy with the above, or feel free
to edit it direct?
If anyone has any suggestions on anything else to add do say so [soon!]
L.
--
---
crowd-funded eco-conscious hardware:
[2]https://www.crowdsupply.com/eoma68
References
1. https://libre-riscv.org/nlnet_2019_wishbone_streaming/
2. https://www.crowdsupply.com/eoma68
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2019-09-25 9:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 6:56 NLNet Funding Proposals for the Libre RISC-V SoC: call for participation Luke Kenneth Casson Leighton
2019-09-23 8:48 ` [Libre-silicon-devel] " David Lanzendörfer
2019-09-24 7:43 ` Luke Kenneth Casson Leighton
2019-09-24 8:54 ` Hagen SANKOWSKI
2019-09-24 11:16 ` Luke Kenneth Casson Leighton
2019-09-24 12:06 ` Staf Verhaegen
2019-09-24 12:12 ` Luke Kenneth Casson Leighton
2019-09-24 12:33 ` Luke Kenneth Casson Leighton
2019-09-25 9:16 ` Luke Kenneth Casson Leighton [this message]
2019-09-24 13:43 ` Staf Verhaegen
2019-09-24 13:53 ` Luke Kenneth Casson Leighton
2020-03-13 0:45 ` Luke Kenneth Casson Leighton
2020-03-13 1:19 ` Adrienne G. Thompson
2020-03-13 1:38 ` [libre-riscv-dev] " Samuel Falvo II
2020-03-13 10:29 ` 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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDxC5=HirMkz4e976iAPRpz3o6KGRnk4HQtXRugrNXwO4Q@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=arm-netbook@lists.phcomp.co.uk \
--cc=hsank@posteo.de \
--cc=libre-riscv-dev@lists.libre-riscv.org \
--cc=libreplanet-discuss@libreplanet.org \
--cc=libresilicon-developers@list.libresilicon.com \
--cc=staf@fibraservi.eu \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).