blob: 23179f96886cff6830d464beabad248b3f500daa [file] [log] [blame]
Erik Faye-Lund4d066832020-06-12 20:09:42 +02001Conformance Testing
2===================
3
Eric Anholt8ea5d8c2020-06-15 12:02:10 -07004Mesa as a project does not get certified conformant by Khronos for the
5APIs it implements. Rather, individual driver teams run the
6conformance tests and submit their results on a set of hardware on a
Erik Faye-Lundd448bf82021-02-03 12:45:17 +01007particular operating system. The canonical list is at Khronos' list
Eric Anholt8ea5d8c2020-06-15 12:02:10 -07008of `conformant
9products <https://www.khronos.org/conformance/adopters/conformant-products/>`_
10and you can find some reports there by searching for "Mesa",
11"Raspbian" and "RADV" for example.
Erik Faye-Lund4d066832020-06-12 20:09:42 +020012
Eric Anholt8ea5d8c2020-06-15 12:02:10 -070013Submitting conformance results to Khronos
14-----------------------------------------
Erik Faye-Lund4d066832020-06-12 20:09:42 +020015
Eric Anholt8ea5d8c2020-06-15 12:02:10 -070016If your driver team is associated with an organization that is a
17Khronos member and has submitted conformance for your API on another
18software stack (likely you're a hardware company), it will probably be
19easiest to submit your conformance through them.
Erik Faye-Lund4d066832020-06-12 20:09:42 +020020
Eric Anholt8ea5d8c2020-06-15 12:02:10 -070021If you are an individual developer or your organization hasn't
22submitted results for the given API yet, X.Org is a member through
23Software in the Public Interest, and they can help submit your
24conformance results to get added to the list of conformant products.
25You should probably coordinate with board@foundation.x.org for your
26first submission.