Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-good gst-plugins-good
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 646
    • Issues 646
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 71
    • Merge requests 71
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-plugins-goodgst-plugins-good
  • Issues
  • #570
Closed
Open
Issue created Mar 05, 2019 by Philipp Zabel@pH5

v4l2allocator: use v4l2_requestbuffers capabilities to determine allocator flags

There is a new capabilities field in v4l2_requestbuffers that can tell us whether the V4L2 queue supports MMAP, USERPTR, and DMABUF buffers. If any of those flags is set in the first REQBUFS(0) result, we can use those to set allocator flags and stop probing in gst_v4l2_allocator_new.

A kernel header update with the new flags is contained in !136 (merged).

Assignee
Assign to
Time tracking