<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#c9">Comment # 9</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:robclark@freedesktop.org" title="Rob Clark <robclark@freedesktop.org>"> Rob Clark</a> <pre>(In reply to Creak from <a href="show_bug.cgi?id=111478#c8">comment #8</a>) > (In reply to Rob Clark from <a href="show_bug.cgi?id=111478#c7">comment #7</a>) > > hmm, [1] looks like an older iteration of drm-shim.. have a look at: > > > > ./src/freedreno/drm-shim > > ./src/broadcom/drm-shim > > > > in the mesa src tree. They are an $LD_PRELOAD'd thing to spoof enough of > > the kernel uabi to "run" the driver. Ie. you can't actually do drawing, but > > it is enough to run shader-db. And so I think it should be pretty much > > enough to run glxinfo. > > Thanks! Are broadcom and freedreno the only two drivers having drm-shim? > Because in order to generate entirely features.txt, I guess all the drivers > should have it, right? currently yes perhaps mesamatrix.net could pull data from a different sources for drivers that run glxinfo in CI?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>