<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add OpenGL ES (GLES) 1.0, 1.1 and 2.0 to docs/features.txt"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111478#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add OpenGL ES (GLES) 1.0, 1.1 and 2.0 to docs/features.txt"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111478">bug 111478</a>
from <span class="vcard"><a class="email" href="mailto:robclark@freedesktop.org" title="Rob Clark <robclark@freedesktop.org>"> <span class="fn">Rob Clark</span></a>
</span></b>
<pre>(In reply to dllud from <a href="show_bug.cgi?id=111478#c2">comment #2</a>)
<span class="quote">> Yes indeed. GLES 1.1</span >
(In reply to russianneuromancer from <a href="show_bug.cgi?id=111478#c1">comment #1</a>)
<span class="quote">> > It would be rather useful to add GLES into docs/features.txt in order to be able to track the status of these drivers.
>
> <a href="https://gitlab.freedesktop.org/mesa/mesa/blob/">https://gitlab.freedesktop.org/mesa/mesa/blob/</a>
> 3a7e92dac538e1ad76b42590beeaada28e79bb07/docs/features.txt#L243
>
> <a href="https://mesamatrix.net">https://mesamatrix.net</a>
>
> As I can see GLES3.1 and GLES3.2 is already there. Freedreno and etnaviv
> supported features is already filled.
>
> So what missing is GLES2.0, GLES3.0, Panfrost and Lima, right?</span >
Is it really possible to advertise anything less than gles2? gallium (mesa
state tracker) implements fixed function gl1/gles1 in terms of programmable
pipeline. There isn't much in the way of features that gles1 has that doesn't
exist in gles2 (maybe user-clip-planes, and there is a lowering pass to support
that for hw that doesn't support it natively.. since a lot of modern hw dropped
support for that).
So I think the only thing to do is just add panfrost and lima.
And now that we are using drm_shim to run shader-db in CI for a few drivers
(freedreno and vc4), I'm secretly hoping someone comes up w/ a way to generate
features.txt (at least for drivers w/ drm_shim support) by running glxinfo in
CI, since features.txt requires that developers remember to actually update it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>