<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c6">Comment # 6</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 <a class="email" href="mailto:romain.failliot@foolstep.com" title="Creak <romain.failliot@foolstep.com>"> Creak</a> <pre>(In reply to Rob Clark from <a href="show_bug.cgi?id=111478#c4">comment #4</a>) > 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. I took a look at drm_shim [1] and it seems that this tool helps faking the driver at the kernel level, is that it? If it is, what I'm not so sure is how that tool works. Looking at the readme, I don't understand the backend options. I was hoping to see the same drivers as the ones listed in features.txt. So.. apparently I'm missing something.. Could you explain it to me? (you can PM me if you'd rather not go too off topic on this thread). [1] <a href="https://gitlab.freedesktop.org/anholt/drm-shim">https://gitlab.freedesktop.org/anholt/drm-shim</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>