From c2dd58b4dc976b639a1e85db029a2452ded81803 Mon Sep 17 00:00:00 2001 From: "pham.michael.98@a029fe8ac2da19fcd7269c492cf0410b2e5fd4cc" Date: Sun, 15 Sep 2019 17:03:04 +0100 Subject: [PATCH] Update Note --- resources.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resources.mdwn b/resources.mdwn index d5af84a35..6161dd693 100644 --- a/resources.mdwn +++ b/resources.mdwn @@ -41,9 +41,9 @@ The Khronos Group creates open standards for authoring and acceleration of graph * OpenCL 2.2 Extension Specification: * OpenCL 2.2 SPIR-V Environment Specification: -Note: I'm not sure what the plan is for OpenGL. Are we doing that in hardware or using Zink to run OpenGL on top of Vulkan? +Note: We are implementing hardware accelerated Vulkan (and possibly OpenCL) while relying on other software projects to translate APIs to Vulkan. E.g. Zink allows for OpenGL-->Vulkan in software. -# Graphics and Computer API Stack +# Graphics and Compute API Stack I found this informative post that mentions Kazan and a whole bunch of other stuff. It looks like *many* APIs can be emulated on top of Vulkan, although performance is not evaluated. -- 2.30.2