Skip to content

android: Add option to ignore artificial limitations

Chris Spencer requested to merge spencercw/mesa:android-strict into main

What does this MR do and why?

Some capabilities are artificially disabled on Android to avoid running afoul of the CTS. Make this behaviour opt-out so devices that don't need strict conformance can take advantage of the full capabilities of the driver.

Right now this is only used for lifting restrictions on advertised Vulkan versions and extensions. Not sure if there is anything on the GL side that might benefit from this.

I'm being intentionally vague here about what precisely we are being conformant with. The CDD doesn't actually have a lot to say about limiting Vulkan capabilities. The video extensions are explicitly banned for example, but that's about the extent of it.1 As I understand it, the bigger problem is that the CTS doesn't get updated, so if we expose everything then the CTS starts complaining about unknown extensions. So really, android-strict=true means try to pass the CTS on the targeted version of Android.

  1. https://source.android.com/docs/compatibility/13/android-13-cdd#7142_vulkan

Merge request reports