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