Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D drm-hwcomposer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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
  • drm-hwcomposer
  • drm-hwcomposer
  • Issues
  • #19

Closed
Open
Created Jan 03, 2019 by Amit Pundir@pundiramit

Respect advertised zpos range from kernel

See comment from @alex_g1 below


Commit ea1c5e5a ("drm_hwcomposer: Add z order support") broke hwcomposer on Qcom dragonboards (db410c/db820c) running AOSP and display doesn't come up on boot.

In logcat I see:
E hwc-drm-display-compositor: Commit test failed for display 0, FIXME
E hwc-drm-two: Failed to apply the frame composition ret=-22
E HWComposer: presentAndGetReleaseFences: present failed for display 0: BadParameter (4)

Here is the complete logcat dump: https://pastebin.ubuntu.com/p/3ywBFwRfk8/

Reverting this z-oder patch get AOSP boot to UI again.

Edited Jan 08, 2019 by Sean Paul
Assignee
Assign to
Time tracking