diff options
| author | Nicolai Hähnle <[email protected]> | 2016-09-28 10:54:34 +0200 |
|---|---|---|
| committer | Nicolai Hähnle <[email protected]> | 2016-10-05 15:51:59 +0200 |
| commit | 0cba7b771a40c87e6a47ccf2381f1d300e9217ef (patch) | |
| tree | a66b105909ed6d072209367c1e95d2ec7878c9c4 /src | |
| parent | b5cd7dfe3e9a04bf6edd5d100f7c74b8fcb5c277 (diff) | |
st/mesa: enable GL_KHR_robustness
The difference to the virtually identical ARB_robustness (which is already
enabled unconditionally) is miniscule and handled elsewhere, but this cap
seems like the right thing to require for this extension.
v2: drop the device reset cap requirement (Ilia)
Reviewed-by: Marek Olšák <[email protected]> (v1)
Reviewed-by: Ilia Mirkin <[email protected]>
Reviewed-by: Edward O'Callaghan <[email protected]>
Diffstat (limited to 'src')
| -rw-r--r-- | src/mesa/state_tracker/st_extensions.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/mesa/state_tracker/st_extensions.c b/src/mesa/state_tracker/st_extensions.c index 4f422176ad5..2282dc7486e 100644 --- a/src/mesa/state_tracker/st_extensions.c +++ b/src/mesa/state_tracker/st_extensions.c @@ -1199,6 +1199,8 @@ void st_init_extensions(struct pipe_screen *screen, } } + extensions->KHR_robustness = extensions->ARB_robust_buffer_access_behavior; + /* If we support ES 3.1, we support the ES3_1_compatibility ext. However * there's no clean way of telling whether we would support ES 3.1 from * here, so copy the condition from compute_version_es2 here. A lot of |