From 7f409438b630a032875cc5faedd7a44d04d67bcd Mon Sep 17 00:00:00 2001 From: Chia-I Wu Date: Fri, 22 Apr 2016 08:12:19 +0800 Subject: [PATCH] doc: remove rules on vkEnumerate*Properties for layers --- loader/LoaderAndLayerInterface.md | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/loader/LoaderAndLayerInterface.md b/loader/LoaderAndLayerInterface.md index 8a35cba..5d706ca 100644 --- a/loader/LoaderAndLayerInterface.md +++ b/loader/LoaderAndLayerInterface.md @@ -1057,19 +1057,8 @@ indirectly from its upper layers. When a layer requires host memory, it is free to scope the allocations to itself, bypassing the provided allocators entirely. -`vkEnumerateInstanceLayerProperties` must always fail with -`VK_ERROR_LAYER_NOT_PRESENT`. - -`vkEnumerateInstanceExtensionProperties` must always fail with -`VK_ERROR_LAYER_NOT_PRESENT`, including when `pLayerName` is `NULL`. - -`vkEnumerateDeviceLayerProperties` must always fail with -`VK_ERROR_LAYER_NOT_PRESENT`. - -`vkEnumerateDeviceExtensionProperties` must always fail with -`VK_ERROR_LAYER_NOT_PRESENT`, except when `pLayerName` is `NULL`. It must -handle the case where `pLayerName` is `NULL`, usually by chaining to other -layers. +`vkEnumerateDeviceExtensionProperties` must handle the case where `pLayerName` +is `NULL`, usually by chaining to other layers. `vkGetInstanceProcAddr` can intercept a command by returning a function pointer different from what would be returned through chaining. -- 2.7.4