From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: "Discussão do LibrePlanet" <libreplanet-discuss@libreplanet.org>
Cc: Linux on small ARM machines <arm-netbook@lists.phcomp.co.uk>,
Libresilicon-developers@list.libresilicon.com,
Libre-RISCV General Development
<libre-riscv-dev@lists.libre-riscv.org>
Subject: NLNet Funding Proposals for the Libre RISC-V SoC: call for participation
Date: Mon, 23 Sep 2019 14:56:31 +0800 [thread overview]
Message-ID: <CAPweEDxP5TqB5Tn8_D0t8TCUTBF2+zSBrDRgVpe=0hRrcYtTmw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2814 bytes --]
[please do remove all but libre-riscv-dev when replying, thx]
https://libre-riscv.org/nlnet_proposals/
A series of funding proposals, each for EUR 50,000, have been submitted to
NLNet. These are for charitable donations and may be given to either
individuals or to Universities (not to Corporations) for completion of an
allotted milestone.
The basic idea is to think through and plan for commercial completion all
of the tasks that will make the Libre RISC-V SoC a success. It's a lot! We
have the following:
- a second Vulkan 3D driver, which will be a port of AMDVLK. similar to
swiftshader, for the Libre RISCV SoC, except taking into account the
Vectorisation, predication and custom accelerated opcodes.
- a video acceleration initiative: with NEON assembler being up to the
job of decoding 720p video on recent ARM64 processors, the idea is to
design instructions that will do the job and then follow through getting
the code upstream.
- two related proposals which, in combination, will result in an actual
180nm ASIC being taped out at TSMC.
- a formal mathematical proof of the hardware design, proving inviolate
guarantees of its correctness. this because although auditing the code is
possible, it is both laborious, error prone, and could be compromised.
mathematical proofs may be run by anyone and are inviolate.
- an augmentation of gcc to support the processor’s parallel and
vectorisation capabilities.
Yes, really: 180nm ASICs only cost around EUR 600 per square millimetre,
and with around 20 or so mm^2 it is completely within the realm of
possibility for an NLNet Grant to fund a test ASIC. With each square
millimetre being around 40,000 gates in 180nm, that's around 800,000 gates,
which is enormous.
We would then have a proven ASIC, and moving up to 40nm or below, which
would require around the USD 2m mark, is a far less risky proposition.
The irony is that whilst these funding proposals are quite easy to write,
we also need to find people willing to do the work! In particular, we need
at least one EU Citizen per project. They do not have to be permanently
resident in the EU, they do however need an EU residence. Yes this includes
the UK at the time of writing.
This is an extremely important strategic project that puts you - software
libre developers - in the driving seat of modern technology instead of
picking up the reverse engineering crumbs that fall from the Corporate
table with at least a 2 year delay.
If you would like to help and actually receive donations (directly
transferred) from NLNet for doing so, please do contact me directly or on
libre-riscv-dev.
L.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
[-- Attachment #1.2: Type: text/plain, Size: 3010 bytes --]
[please do remove all but libre-riscv-dev when replying, thx]
[1]https://libre-riscv.org/nlnet_proposals/
A series of funding proposals, each for EUR 50,000, have been submitted
to NLNet. These are for charitable donations and may be given to
either individuals or to Universities (not to Corporations) for
completion of an allotted milestone.
The basic idea is to think through and plan for commercial completion
all of the tasks that will make the Libre RISC-V SoC a success. It's a
lot! We have the following:
* a second Vulkan 3D driver, which will be a port of AMDVLK. similar
to swiftshader, for the Libre RISCV SoC, except taking into account
the Vectorisation, predication and custom accelerated opcodes.
* a video acceleration initiative: with NEON assembler being up to
the job of decoding 720p video on recent ARM64 processors, the idea
is to design instructions that will do the job and then follow
through getting the code upstream.
* two related proposals which, in combination, will result in an
actual 180nm ASIC being taped out at TSMC.
* a formal mathematical proof of the hardware design, proving
inviolate guarantees of its correctness. this because although
auditing the code is possible, it is both laborious, error prone,
and could be compromised. mathematical proofs may be run by anyone
and are inviolate.
* an augmentation of gcc to support the processor’s parallel and
vectorisation capabilities.
Yes, really: 180nm ASICs only cost around EUR 600 per square
millimetre, and with around 20 or so mm^2 it is completely within the
realm of possibility for an NLNet Grant to fund a test ASIC. With each
square millimetre being around 40,000 gates in 180nm, that's around
800,000 gates, which is enormous.
We would then have a proven ASIC, and moving up to 40nm or below, which
would require around the USD 2m mark, is a far less risky proposition.
The irony is that whilst these funding proposals are quite easy to
write, we also need to find people willing to do the work! In
particular, we need at least one EU Citizen per project. They do not
have to be permanently resident in the EU, they do however need an EU
residence. Yes this includes the UK at the time of writing.
This is an extremely important strategic project that puts you -
software libre developers - in the driving seat of modern technology
instead of picking up the reverse engineering crumbs that fall from the
Corporate table with at least a 2 year delay.
If you would like to help and actually receive donations (directly
transferred) from NLNet for doing so, please do contact me directly or
on libre-riscv-dev.
L.
--
---
crowd-funded eco-conscious hardware:
[2]https://www.crowdsupply.com/eoma68
References
1. https://libre-riscv.org/nlnet_proposals/
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 reply other threads:[~2019-09-23 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 6:56 Luke Kenneth Casson Leighton [this message]
2019-09-23 8:48 ` [Libre-silicon-devel] NLNet Funding Proposals for the Libre RISC-V SoC: call for participation 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
2019-09-24 13:43 ` [Libre-silicon-devel] " 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='CAPweEDxP5TqB5Tn8_D0t8TCUTBF2+zSBrDRgVpe=0hRrcYtTmw@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=Libresilicon-developers@list.libresilicon.com \
--cc=arm-netbook@lists.phcomp.co.uk \
--cc=libre-riscv-dev@lists.libre-riscv.org \
--cc=libreplanet-discuss@libreplanet.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
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).