summaryrefslogtreecommitdiffstats
path: root/.editorconfig
diff options
context:
space:
mode:
authorPhilip Langdale <philipl@overt.org>2019-12-16 19:23:14 -0800
committerPhilip Langdale <github.philipl@overt.org>2021-11-15 21:07:21 -0800
commitb030cfe05f585234c10337576047bc314b36faef (patch)
tree06cab98a1847b681bd59792645fe13da3747cf2d /.editorconfig
parent3bfc37dcb46b43e44ff4f99d1947ccfd603379b9 (diff)
downloadmpv-b030cfe05f585234c10337576047bc314b36faef.tar.bz2
mpv-b030cfe05f585234c10337576047bc314b36faef.tar.xz
vo_gpu: vulkan: open DRM render fd when using VK_KHR_display
While the basic Vulkan Display context can theoretically drive the display without the involvement of any non-Vulkan code, that prevents us from using VAAPI acceleration. When initialising VAAPI without a window system, we need to provide it with an opened DRM render fd corresponding to the device to use. In the context of using VK_KHR_display, that means we need to identify which DRM device matches the selected Vulkan device, and then open its render fd and set the necessary state that VAAPI expects to find. With that done, the normal VAAPI<->Vulkan interop can kick in and we get working acceleration
Diffstat (limited to '.editorconfig')
0 files changed, 0 insertions, 0 deletions