There should be no reason to install vulkan-wsi-layer on Linux at this
time AFAIK, mesa drivers provide their own WSI.
they do.
but whether they're sufficient depends on your use case.
comparing implicit-layer-loaded vulkan-wsi-layer vs MESA native-WSI
a minimal-instance test (vk-feature-query) checking for capability, with layer
installed/auto-enabled
$ VK_DRIVER_FILES=.../intel_icd.x86_64.json ./vk-feature-query
swapchainMaintenance1 : true # layer implemented
presentWait2 : true # layer implemented
presentTiming : true # layer-only (Mesa: false)
presentAtAbsoluteTime : true # layer-only (Mesa: false)
presentAtRelativeTime : true # layer-only (Mesa: false)
presentModeFifoLatestReady: true # layer-only (Mesa: false)
and disabled
$ DISABLE_WSI_LAYER=1 VK_DRIVER_FILES=.../intel_icd.x86_64.json
./vk-feature-query
swapchainMaintenance1 : true # Mesa native
presentWait2 : true # Mesa native
presentTiming : false
presentAtAbsoluteTime : false
presentAtRelativeTime : false
presentModeFifoLatestReady: false
iiuc layer *exclusively* provides:
presentTiming
presentAtAbsoluteTime
presentAtRelativeTime
presentModeFifoLatestReady
useful when an app needs to
- control exactly when frames appear on screen
- show the freshest frame at each vblank without tearing
e.g., video sync, VR, real-time imaging/control ...
but, fair point. may not be of interest to the distro's packaging.
local build/install solves the functionality issue here.
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
