Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow EGL 1.5 implementations without GL_KHR_robustness #480

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rmader
Copy link
Contributor

@rmader rmader commented Aug 15, 2024

Driver may want to expose a minimal implementation of EGL_EXT_create_context_robustness - i.e. a dummy implementation without corresponding GL_KHR_robustness support - in order to support EGL 1.5.

When requesting a context with EGL_CONTEXT_OPENGL_ROBUST_ACCESS_EXT -> EGL_TRUE on such a driver, it has to create a EGL_BAD_CONFIG error - and unfortunately there's no way to check for GL_KHR_robustness in advance.

Thus handle that case gracefully.


This should allow Mesa to expose 1.5 support for all drivers on all hardware generations.

Related:

Driver may want to expose a minimal implementation of
EGL_EXT_create_context_robustness - i.e. a dummy implementation
without corresponding GL_KHR_robustness support - in order to
support EGL 1.5.

When requesting a context with EGL_CONTEXT_OPENGL_ROBUST_ACCESS_EXT
-> EGL_TRUE on such a driver, it has to create a EGL_BAD_CONFIG error
 - and unfortunately there's no way to check for GL_KHR_robustness in
advance.

Thus handle that case gracefully.
@CLAassistant
Copy link

CLAassistant commented Aug 15, 2024

CLA assistant check
All committers have signed the CLA.

m_testCtx.setTestResult(QP_TEST_RESULT_FAIL, "Fail");
}
return STOP;
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If preferred I can move this into a function in order to avoid duplication.

@fooishbar
Copy link
Contributor

Specifically, this still allows querying of device reset status, without robust buffer access guarantees.

@rmader rmader marked this pull request as draft August 16, 2024 22:02
@rmader
Copy link
Contributor Author

rmader commented Aug 16, 2024

There are a few more places that need to be covered.

@rmader rmader marked this pull request as ready for review August 17, 2024 06:47
@rmader
Copy link
Contributor Author

rmader commented Aug 17, 2024

Nevermind and sorry for the noise - there were just some more issues in Mesa making tests fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants