[FFmpeg-trac] #7649(avutil:new): FFmpeg QSV initialization fails on KBL HadesCanyon (= both Intel & AMD GPUs) when DISPLAY is set

[FFmpeg]

#7649: FFmpeg QSV initialization fails on KBL HadesCanyon (= both Intel & AMD
GPUs) when DISPLAY is set
------------------------------------+----------------------------------
             Reporter:  eero-t      |                    Owner:
                 Type:  defect      |                   Status:  new
             Priority:  normal      |                Component:  avutil
              Version:  git-master  |               Resolution:
             Keywords:  qsv         |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+----------------------------------

Comment (by lizhong1008):

 Replying to [comment:6 eero-t]:
 > And if on some machine multiple GPUs identify themselves with Intel
 vendor, driver could default to first which
 /sys/class/drm/<rendernode>/device/device ID matches a supported HW ID,
 unless user specifies something else.
 >
 > I guess correct place for these checks would be in the libva backend, as
 it's the one that knows what HW it supports.  If there isn't any support
 for that, could you file a bug about that to appropriate place, and link
 it here as a blocker?
 https://github.com/intel/media-driver is the driver used by MSDK and
 FFmpeg-qsv. You can report an issue there.
 However, I don't think it is helpful When you set a AMD GPU as display
 device but the libva driver is to get a device from a X11 display. The
 only way in my mind is to make FFmpeg connect to a drm device directly,
 this is not a default path and should be set manually (you suggestion is
 just to chose a appropriate default drm device automatically)

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7649#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker