loader: Add images to interface Doc
diff --git a/images/chain_skipping_layers.png b/images/chain_skipping_layers.png
new file mode 100644
index 0000000..0eca54e
--- /dev/null
+++ b/images/chain_skipping_layers.png
Binary files differ
diff --git a/images/get_proc_addr.png b/images/get_proc_addr.png
new file mode 100644
index 0000000..a11c164
--- /dev/null
+++ b/images/get_proc_addr.png
Binary files differ
diff --git a/images/instance_call_chain.png b/images/instance_call_chain.png
new file mode 100644
index 0000000..848b726
--- /dev/null
+++ b/images/instance_call_chain.png
Binary files differ
diff --git a/images/instance_dispatch.png b/images/instance_dispatch.png
new file mode 100644
index 0000000..5922b74
--- /dev/null
+++ b/images/instance_dispatch.png
Binary files differ
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.
+
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.
+
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.
+
+
Vulkan Installable Client Driver interface with the loader
----------------------------------------------------------
