Skip to content
GitLab
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 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • 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
  • drm-hwcomposer
  • drm-hwcomposer
  • Issues
  • #43
Closed
Open
Issue created Oct 08, 2020 by Roman Stratiienko@roman.stratiienkoMaintainer

Discuss correct way to get per-plane FD using mapper metadata API.

Approach 0:
(Used by mesa3d EGL importer for as generic solution for some time)
Use buffer_handle_t->data[plane_idx or 0] as FD.

Approach 1:

One approach is having each vendor define their custom metadata to access the fds. For drm_hwcomposer this would mean having to support all these different ways of retrieving the fds. In this case, we would indeed not have a custom AIDL in drm_hwcomposer, but would have to support the ones each customer provides.

Approach 2:

To have drm_hwcomposer define its custom metadata. Interested vendors can then add support for drm_hwcomposer in their Gralloc implementations.

Edited Oct 09, 2020 by Roman Stratiienko
Assignee
Assign to
Time tracking