Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • xserver xserver
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 944
    • Issues 944
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 123
    • Merge requests 123
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • xorgxorg
  • xserverxserver
  • Merge requests
  • !194

Separate per-client vendor mappings for GLXVND

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed Kyle Brenneman requested to merge kbrenneman/xserver:GLXVND-per-client-vendor into master May 08, 2019
  • Overview 13
  • Commits 6
  • Pipelines 3
  • Changes 5

This is an alternative to !179 (closed). This MR provides the same basic functionality, but doesn't make any breaking changes to the GLXVND ABI.

The first part is the same: It adds a separate (screen -> vendor) mapping for each client. It defaults to using the existing global mapping, and there's a new function in GlxServerExports that lets a driver change the mapping for a particular client.

To dispatch a request based on a normal window XID (the only XID's that GLX has to deal with but aren't defined through GLX requests), it'll still use the vendor mapping from the client that sent the request. Since GlxServerExports::getXIDMap doesn't take a ClientPtr argument, though, it has to store the ClientPtr in a global variable instead.

This also doesn't include a new GLX extension, so any driver that wants to use this would need to define its own protocol.

Edited May 15, 2019 by Kyle Brenneman
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: GLXVND-per-client-vendor