On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99@xxxxxxxxx> wrote: > Any suggestions on how to trace the config issues? Do I have to debug the va_openDriver() function? My guess, without reading any code, is that DRI_PRIME isn't doing what you want it to, and the nouveau driver is being handed an intel device. This does not work well. Fixing this will require tracing through the va winsys code which to figure out how it invokes the loader. https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/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 _______________________________________________ Nouveau mailing list Nouveau@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/nouveau
