Dose this mean if the amdgpu_dri.so is compatible with GBM DRI backend, it will also compatible with libGL.so and xserver libglx.so (do these use same loader/DRI-ABI as GBM DRI backend)?
Regards, Qiang ________________________________________ From: Michel Dänzer <mic...@daenzer.net> Sent: Monday, February 6, 2017 2:28:21 PM To: Yu, Qiang; Emil Velikov; Mao, David Cc: ML mesa-dev Subject: Re: [Mesa-dev] [PATCH] gbm: add support for loading third-party backend On 06/02/17 02:58 PM, Yu, Qiang wrote: > >> * The ImgTec guys were able to tweak their binary which combined with >> a bit of mesa glue produces a DRI module. >> This in itself lead of a number of nice improvements and fixes that >> landed in Mesa. Have you/others considered that option ? > [yuq] You mean make amdgpu_dri.so a DRI compatible module which can > be used with the current default GBM DRI backend? But this still need a way > to select which vendor's DRI module because amdgpu_dri.so overlap support > cards with radeonsi_dri.so and the current GBM DRI backend always load > radeonsi_dri.so from a PCIID-DRI table lookup. https://patchwork.freedesktop.org/patch/136822/ allows overriding the driver name via an environment variable. It should be possible to make this persistently configurable at a per-system, per-user and per-application level via the drirc mechanism. > Also not sure if the ABI is stable for different mesa versions? Yes, it's backwards compatible, i.e. older driver binaries can work with newer loader versions. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
