> I believe it used to be there.
Hm yeah, there was a certain time frame where we used EGL+GLES for the check on all platforms. Before that we always used GLX+GL, after it EGL+GL - and then, with the mentioned commit, preferring GLES on arm64 again. So acceleration was never deliberately supported on devices like this with GLES 2.0 but no GL 2.0 support - and the breaking commit was earlier than the one mentioned.
I see two possible solutions here:
- prefer GLES on armhf as well.
- extend the fallback path in glxtest to trying both APIs.
Bug 1812016 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> I believe it used to be there.
Hm yeah, there was a certain time frame where we used EGL+GLES for the check on all platforms. Before that we always used GLX+GL, after it EGL+GL - and then, with the mentioned commit, preferring GLES on arm64 again. So acceleration was never deliberately supported on devices like this with GLES 2.0 but no GL 2.0 support - and the breaking commit was earlier than the one mentioned.
I see two possible solutions here:
1. prefer GLES on armhf as well.
2. extend the fallback path in glxtest to trying both APIs.
P.S.: the later approach has the advantage of also allowing Intel Gen 3?/4? devices to have some WebGL support.