Stefan Zijlstra 7ef64474e3 Xclipse layer: copy any device-chain structure the headers define ...

The chain copy that clears the emulated textureCompressionBC only knew a
handful of structure sizes, so a valid chain such as
VkPhysicalDeviceTimelineSemaphoreFeatures -> VkPhysicalDeviceFeatures2 was
passed on unchanged and the compat layer refused the bit. Size every
structure that may extend VkDeviceCreateInfo from a table generated from the
Vulkan registry (gen_device_chain.py, Vulkan-Headers 1.3.275, the headers
the build compiles with), and copy onto the heap instead of a fixed buffer.
Only a structure newer than those headers still passes the chain unchanged.

Add a regression test that runs the layer between a simulated loader and a
mock driver: the timeline-semaphore chain, pEnabledFeatures, an unknown
structure, the caller's structures left untouched, per-device YCbCr sampler
tracking with handle reuse, and the KHR calibrated-timestamp forwarding. CI
installs libvulkan-dev for it.

2026-10-12 07:32:52 +02:00

..

device_chain.inc

Xclipse layer: copy any device-chain structure the headers define

2026-10-12 07:32:52 +02:00

gen_device_chain.py

Xclipse layer: copy any device-chain structure the headers define

2026-10-12 07:32:52 +02:00

VkLayer_droiddeck_xclipse.json

Experimental Samsung Xclipse support on the system Vulkan path

2026-10-12 05:55:57 +02:00

xclipse_layer.c

Xclipse layer: copy any device-chain structure the headers define

2026-10-12 07:32:52 +02:00