Hi, It seems this patch has been pushed recently. This is causing me problems on a multi gpu configuration. It is a laptop with intel and nvidia, graphic hardwares.
1: intel vaapi driver: vainfo 2: st/va,nouveau: DRI_PRIME=1 LIBVA_DRIVER_NAME=gallium vainfo with that patch 0c0f841e5de27d01312f8857641668ca439b1ab1 " st/va: hardlink driver instances to gallium_drv_video.so" the case 2 does not work anymore. Ah I just realized that it does work by setting: LIBVA_DRIVER_NAME=nouveau Is it the expected behavior ? Cheers Julien On 21 April 2016 at 14:20, Emil Velikov <emil.l.veli...@gmail.com> wrote: > Hi Stefan, > > On 21 April 2016 at 14:05, Stefan Dirsch <sndir...@suse.de> wrote: > > From: Jimmy Berry <ji...@boombatower.com> > > > > Removes the need to set LIBVA_DRIVER_NAME=gallium for supported targets > and is > > consistent with vdpau and general gallium drivers. > There are two options here afaict: > - Use an updated libva which already handles "gallium_drv.so" > - Chip-in on the following topic [1] and working from there. > > Personally I'd opt for the former, because (as you know) hardlinking > things is a bit nasty. > > Speaking of which you guys are the only ones building multiple drivers > at once (thus a megablob is created) yet still shiping the identical > file as separate drivers. > > Suggestion - you can merge the separate packages into one or build > mesa separate times to produce binaries similar to before megadriver. > > Emil > > [1] https://patchwork.freedesktop.org/patch/58540/ > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
