Robert Mader f83e34640e Bug 1870180 - [VA-API] Silence some vaapitest warnings, r=stransky ... The library not being installed or initialization failing - for example because no VA driver is available - is common and expected on an increasing number of setups, notably most ARM devices with V4L2 decoders. Thus tone down the warnings. The logs are still available when setting `MOZ_GFX_DEBUG=1`. Also fix a typo - searching for `sVaGetDisplayDRM` will be rather disappointing. Note that some users also run into the `failed to open renderDeviceFD` case. That's an actual bug, however, and only happens when we guessed a wrong path. The affected devices (ignoring setups with very old Mesa) are split display/render SoCs where `EGL_EXT_device_drm_render_node` is not exposed yet - which is finally fixed in Mesa 23.3. Differential Revision: https://phabricator.services.mozilla.com/D196525		2023-12-15 10:22:50 +00:00
..
moz.build
vaapitest.cpp	Bug 1870180 - [VA-API] Silence some vaapitest warnings, r=stransky	2023-12-15 10:22:50 +00:00