search for: renderd129

...> For the DRM/rendernodes "platform", it will just take whatever fd it > is given. vainfo appears to give it a fixed device: > > > https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 > > However it looks like you can pass in --device /dev/dri/renderD129 or > whatever the right one is, which should pass in the right render node, > as seen here: > > https://github.com/intel/libva-utils/blob/master/common/va_display.c#L80 > > Note that I've never tried this, just did a few google searches to > find this stuff. > > Brill...

Hi, Try: DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --display drm --device /dev/dri/renderD129 Also try with and without the --device option, the important one is --display drm Cheers Julien On Tue, Sep 1, 2020 at 10:49 AM Analabha Roy <hariseldon99 at gmail.com> wrote: > > > On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > >> On T...

> > It does indicate a config problem, but why do you want to use the > nvidia GPU for video accel? I'd rely on intel to provide acceleration > as this also reduces power consumption of the entire system. Also I > think vaapi on the secondary GPU is pretty much untested. Well you've got a point there. It's just that the dang nvidia is pretty much sitting there on its

...lium/frontends/va/context.c#n111 For the DRM/rendernodes "platform", it will just take whatever fd it is given. vainfo appears to give it a fixed device: https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 However it looks like you can pass in --device /dev/dri/renderD129 or whatever the right one is, which should pass in the right render node, as seen here: https://github.com/intel/libva-utils/blob/master/common/va_display.c#L80 Note that I've never tried this, just did a few google searches to find this stuff. Cheers, -ilia