Some enhancements to vainfo

[xhaihao]

3 commits

• add '--device' option to specify device name if the current display is drm.
• add '--help' option to show available options
• replace abort() with exit(1)

[dbermond]

Works fine for me to show information about /dev/dri/renderD129:

$ vainfo --display drm --device /dev/dri/renderD129
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.40 (libva )
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 1.8.4.pre1 (glk-alpha-71-gc3110dc)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      : VAEntrypointVLD
      VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
      VAProfileH264StereoHigh         : VAEntrypointVLD
      VAProfileH264StereoHigh         : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileJPEGBaseline           : VAEntrypointVLD

[xhaihao]

@dbermond Thanks for trying the patch and the feedback.

[pengche1]

LGTM

[kyse]

Any thoughts on an environment variable to specify the device similar to LIBVA_DRIVER_NAME.

Ive been trying to get setup with a working solution on a vm server where the systemd daemon making use of vainfo to query quick sync support. Problem is the /dev/dri/renderD128 points to the esxi vmwgfx device.

I'm hoping I can just setup an environment variable in the systemd script to get it to process properly.

[Brainiarc7]

Hello @kyse ,

It may be possible to set up a udev rule pointing to an alias for the correct device name.

Let me see how that would be implemented.

[Kabouik]

Have you found a way @Brainiarc7?

I would also be interested in specifying a device with an environment variable to use the Intel VA driver (i965) instead of the radeon driver (radeonsi), because the latter comes with some bugs for my use, while i965 works perfectly (tried temporarily after rebooting without my AMD GPU). Yet, I do not want to uninstall the AMD GPU permanently because it has other uses than decoding video. See #186 and #264, as well as your own #120 issue.

[Brainiarc7]

@Kabouik not yet.

Still looking into a dirty hack with a udev rule.

Look, all we're asking for is a reasonable environment variable that would allow for device selection (optional, in the same way that a device driver for vaapi can be specified). It would solve a lot of headaches with vaapi.

[MartinX3]

I have a similiar problem.

I use my iHD intel gpu to display everything
My nvidia card is used with prime-run

Sadly the 128 dri device is the nvidia-drm
The 129 dri is the i915

But it seems that devices like parole wants to use the 128 with the vaapi in gstreamer to run the movie on the intel gpu card, which is wrong