commit ab3a46696dc17db83748262e23d411b9c69a3da8
author Courtney Goeltzenleuchter <courtneygo@google.com> Sun Feb 14 10:48:22 2016 -0700
committer Jon Ashburn <jon@lunarg.com> Mon Feb 15 08:59:29 2016 -0700
tree 6e3731fdec2d0728f091eb62d99156c48f325d6e
parent a1473760b82469066135102b77fdf164306a7eb7

loader: Add images to interface Doc

loader/LoaderAndLayerInterface.md

diff --git a/loader/LoaderAndLayerInterface.md b/loader/LoaderAndLayerInterface.md
index 4901fea..f5a222c 100644
--- a/loader/LoaderAndLayerInterface.md
+++ b/loader/LoaderAndLayerInterface.md
@@ -75,6 +75,7 @@
 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)
 
 This also highlights some of the complexity the loader must manage when using
 instance chains. As shown here, the loader must aggregate information from
@@ -85,6 +86,7 @@
 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)
 
 Application interface to loader
 -------------------------------
@@ -240,6 +242,8 @@
 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)
+
 
 Vulkan Installable Client Driver interface with the loader
 ----------------------------------------------------------