Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in / Register
F
ffmpeg
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Packages
    • Packages
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • submodule
  • ffmpeg
  • Repository

Switch branch/tag
  • ffmpeg
  • libavutil
  • hwcontext_vaapi.c
Find file
BlameHistoryPermalink
  • Mark Thompson's avatar
    hwcontext_vaapi: Only accept a render node when deriving from DRM device · bc9b6358
    Mark Thompson authored Feb 16, 2020
    If we are given a non-render node, try to find the matching render node and
    fail if that isn't possible.
    
    libva will not accept a non-render device which is not DRM master, because
    it requires legacy DRM authentication to succeed in that case:
    <https://github.com/intel/libva/blob/master/va/drm/va_drm.c#L68-L75>.  This
    is annoying for kmsgrab because in most recording situations DRM master is
    already held by something else (such as a windowing system), leading to
    device derivation not working and forcing the user to create the target
    VAAPI device separately.
    bc9b6358
hwcontext_vaapi.c 56.1 KB
EditWeb IDE

Replace hwcontext_vaapi.c

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.