Skip to content

glx: Claim to support more GL versions in __glX_send_client_info

Adam Jackson requested to merge ajax/mesa:glx-send-more-client-info into master

It's a little unclear from the GLX_ARB_create_context spec whether the list of supported extensions means what the client supports at all, or what it knows an indirect GLX encoding for. You'd think it could only really matter for indirect, since the only way the server would know about GL commands (as opposed to GLX commands) is if the context was indirect. However, when drisw creates a context that includes sending the GLX request, which means the server needs to believe the named version is supported. Apparently NVIDIA's GLX will take the clientinfo into account for this even for drisw's "direct" contexts, which means zink / llvmpipe / etc get clamped to 3.0.

So go ahead and claim to support everything. This is something of a lie, since we do not in fact have GLX encoding beyond GL 1.4 yet, but a) that limit gets enforced elsewhere and b) there's no GLX encoding even defined beyond 3.0 yet anyway.

cc @idr for having written __glX_send_client_info originally.

Note that drisw doesn't actually work on NVIDIA yet for fbconfig matching reasons (see !1648 (merged)), but if you do hack the fbconfig setup enough to work you'd run into this.

Merge request reports