Fix Vulkan null driver
authorPyry Haulos <phaulos@google.com>
Thu, 18 May 2017 22:42:53 +0000 (15:42 -0700)
committerPyry Haulos <phaulos@google.com>
Thu, 18 May 2017 22:42:53 +0000 (15:42 -0700)
commit1872fd5ceb9cfd131db5669ab5f9147fbf560103
tree634d47ca03c93a6122e406cc67093026d28d4dd0
parent2f442619367e349e42f041ca094bbdc6b9699bca
Fix Vulkan null driver

Vulkan platform was changed to use vkGetInstanceProcAddr(NULL, pName)
for loading all platform-level functions, except vkGetInstanceProcAddr
itself, in commit bbd3dce44fafaa4b1952b63564022f19b3a65ca3. Null
driver was not adjusted for that change and that resulted calling into
null function pointer early in the initialization code.

Additionally, null driver now advertises HOST_COHERENT memory.

Change-Id: I65c8b37722950de08e337d7df95aa46a0e826c7b
external/vulkancts/framework/vulkan/vkNullDriver.cpp