[Mesa-dev] Remove classic drivers or fork src/mesa for gallium?
hoegsberg at gmail.com
Mon Mar 30 15:40:39 UTC 2020
On Mon, Mar 30, 2020, 7:59 AM Adam Jackson <ajax at redhat.com> wrote:
> On Sun, 2020-03-29 at 09:45 -0700, Kristian Høgsberg wrote:
> > As for loading, doesn't glvnd solve that?
> It could. It does not. Right now there's not a (good) way for the DDX
> driver to communicate a preferred implementation name to the GLX
> client. xserver's glx just knows it needs an implementation named mesa,
> and nvidia's glx, nvidia. Not a hard thing to wire up, and in fact you
> can give multiple names and the client side will try them in sequence
> so fallback stands a chance of working.
> Now, if we're doing that, we should maybe consider using glvnd's
> libGLdispatch directly, as I think right now we have an ugly double-
> indirection between glHamSandwichEXT and _mesa_HamSandwichEXT if you're
> building for glvnd. The only thing in the world besides Mesa that cares
> about glapi and what a DRI driver interface is is xserver, and that's a
> detail I'd like to eliminate and the new EGL-backed GLX in Xwayland
> gets really close to eliminating it. But if nobody else gets excited
> that much about fixing GLX, I completely understand.
Yeah it would make sense to disable the double dispatch and it would be
tempting to get rid of dri driver loading entirely then...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mesa-dev