Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • xserver xserver
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 934
    • Issues 934
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • xorg
  • xserverxserver
  • Merge requests
  • !496

Closed
Created Aug 19, 2020 by Aleksander Miera@alagner
  • Report abuse
Report abuse

modesetting: workaround for stride/pitch mismatch

  • Overview 7
  • Commits 1
  • Pipelines 2
  • Changes 1

This helps for the cases where buffer stride is miscalculated, the most notable example being 1366x768 resolution. From what I understand the code, the stride calculation should distinguish between any pixmap and the one used for FB, which is not the case and everything is calculated in glamor/glamor.c:227.

Fixes: #889 (closed) Signed-off-by: Aleksander Miera ammiera@hotmail.com

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: stride-mismatch-workaround