aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJon Ashburn <jon@lunarg.com>2016-02-15 10:19:26 -0700
committerJon Ashburn <jon@lunarg.com>2016-02-15 10:21:35 -0700
commit8e1b34856d01f837503ac53201f3463e060cec07 (patch)
tree4f24ef5b359241f31db84054e825192c6f57b92a
parentdf0cdc46b31a7bda4ebb7a57fd28a2abf14b7d58 (diff)
downloadusermoji-8e1b34856d01f837503ac53201f3463e060cec07.tar.xz
loader: move doc png file to loader current directory for use of same file in SDK
-rw-r--r--loader/LoaderAndLayerInterface.md6
-rw-r--r--loader/chain_skipping_layers.png (renamed from images/chain_skipping_layers.png)bin17793 -> 17793 bytes
-rw-r--r--loader/get_proc_addr.png (renamed from images/get_proc_addr.png)bin17411 -> 17411 bytes
-rw-r--r--loader/instance_call_chain.png (renamed from images/instance_call_chain.png)bin18868 -> 18868 bytes
-rw-r--r--loader/instance_dispatch.png (renamed from images/instance_dispatch.png)bin46866 -> 46866 bytes
5 files changed, 3 insertions, 3 deletions
diff --git a/loader/LoaderAndLayerInterface.md b/loader/LoaderAndLayerInterface.md
index 3a6e4123..d7965d5a 100644
--- a/loader/LoaderAndLayerInterface.md
+++ b/loader/LoaderAndLayerInterface.md
@@ -77,7 +77,7 @@ first layer’s vkCreateInstance which will call the next finally terminating in
the loader again where this function calls every ICD’s vkCreateInstance and
saves the results. This allows every enabled layer for this chain to set up
what it needs based on the VkInstanceCreateInfo structure from the application.
-![Instance call chain](/images/instance_call_chain.png)
+![Instance call chain](instance_call_chain.png)
This also highlights some of the complexity the loader must manage when using
instance chains. As shown here, the loader must aggregate information from
@@ -88,7 +88,7 @@ Device chains are created at vkCreateDevice and are generally simpler because
they deal with only a single device and the ICD can always be the terminator of
the chain. The below diagram also illustrates how layers (either device or
instance) can skip intercepting any given Vulkan entry point.
-![Chain skipping layers](/images/chain_skipping_layers.png)
+![Chain skipping layers](chain_skipping_layers.png)
Application interface to loader
-------------------------------
@@ -244,7 +244,7 @@ vkGetDeviceProcAddr will only work with the specific VkDevice it was created
for, using it with another device has undefined results. For extensions,
Get\*ProcAddr will often be the only way to access extension API features.
-![Get*ProcAddr efficiency](/images/get_proc_addr.png)
+![Get*ProcAddr efficiency](get_proc_addr.png)
Vulkan Installable Client Driver interface with the loader
diff --git a/images/chain_skipping_layers.png b/loader/chain_skipping_layers.png
index 0eca54ef..0eca54ef 100644
--- a/images/chain_skipping_layers.png
+++ b/loader/chain_skipping_layers.png
Binary files differ
diff --git a/images/get_proc_addr.png b/loader/get_proc_addr.png
index a11c1648..a11c1648 100644
--- a/images/get_proc_addr.png
+++ b/loader/get_proc_addr.png
Binary files differ
diff --git a/images/instance_call_chain.png b/loader/instance_call_chain.png
index 848b726d..848b726d 100644
--- a/images/instance_call_chain.png
+++ b/loader/instance_call_chain.png
Binary files differ
diff --git a/images/instance_dispatch.png b/loader/instance_dispatch.png
index 5922b744..5922b744 100644
--- a/images/instance_dispatch.png
+++ b/loader/instance_dispatch.png
Binary files differ