bug 1244: separate frame for linked list image

[libreriscv.git] / nlnet_2019_amdvlk_port.mdwn

diff --git a/nlnet_2019_amdvlk_port.mdwn b/nlnet_2019_amdvlk_port.mdwn
index 6a804b86c38afdb118a778e5784ff9c870b34596..07e2f0a03f5d16c2e3032776ec8ba29e4dd3aa4e 100644 (file)
--- a/nlnet_2019_amdvlk_port.mdwn
+++ b/nlnet_2019_amdvlk_port.mdwn
@@ -1,4 +1,8 @@
-# NL.net proposal
+# NL.net proposal 2019-10-042
+
+* [[questions]]
+* NLNet Project page <https://nlnet.nl/project/LibreSoC-3Ddriver/>
+* Top Level bugreport <http://bugs.libre-riscv.org/show_bug.cgi?id=140>
 
 ## Project name
 
@@ -158,6 +162,10 @@ efforts to introduce "mainline" LLVM patches on an ongoing piecemeal
 basis, and at the same time *add our own assembler back-end* into the
 same fast-moving target.
 
+Whereas with RADV it is upstreamed in MESA, and has much wider community
+support, it will need very careful detailed evaluation to ensure that it meets
+the needs of the Libre RISC-V Vector Engine.
+
 ## Describe the ecosystem of the project, and how you will engage with relevant actors and promote the outcomes?
 
 As mentioned in the 2018 submission, the Libre RISC-V
@@ -180,3 +188,6 @@ all picked up the story.  The list is updated and maintained here:
 * <https://salsa.debian.org/Kazan-team/kazan>
 * <https://github.com/mesa3d/mesa/tree/master/src/amd/vulkan>
 
+# Management Summary
+
+The Libre-SOC Project core is funded from an initial 2018 proposal. This includes a 3D Driver, called Kazan, and its purpose is to provide a Vulkan compliant hybrid hardware-software API.  Given the complex nature of 3D driver development, and because Kazan is a novel approach (written in rust, for security reasons) a second oroposal was submitted to develop a Mesa3D driver (in c++). A second more traditional (c++) 3D Driver allows for increased transparency and collaboration on this ambitious project.