Skip to content

Add driver quirks mechanism

This mechanism comes from ffmpeg vaapi implementation, where they have their own quirks.

A specific driver is identified by a substring present in the vendor string. If that substring is found, a set of bitwise flags are store. These flags can be accessed through the function gst_vaapi_display_has_driver_quirks().

The purpose for this first quirks is to disable the put image try for AMD Gallium driver (see !72 (merged) ), and also, obviously it reenables amd gallium mesa driver in the white list

Merge request reports