Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
W
weston
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 273
    • Issues 273
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 118
    • Merge Requests 118
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • weston
  • Issues
  • #375

Closed
Open
Opened Mar 11, 2020 by Pekka Paalanen@pqMaintainer

Use cursor plane also with Pixman-renderer on DRM-backend

Currently the DRM-backend depends on GBM for cursor planes, more specifically for the buffers for cursor planes. This means that cursor planes can be used only if GBM is initialized, which means using GL-renderer. Hence when using Pixman-renderer, cursor plane is not used.

It might be nice to be able to use the cursor plane also with Pixman-renderer. Repainting for only cursor motion with Pixman has a cost that could be avoided.

Should there be an alternative path to GBM, or should the GBM path be replaced completely?

Why did we use GBM for cursor buffers?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: wayland/weston#375