[Mesa-dev] [PATCH 1/3] vl/dri3: use external texture as back buffers

Andy Furniss adf.lists at gmail.com
Tue Oct 25 20:13:39 UTC 2016


Leo Liu wrote:
>
>
> On 10/25/2016 02:42 PM, Andy Furniss wrote:
>> Christian K├Ânig wrote:
>>> Nice work, have you been able to fix all the issues you mentioned on
>>> your last mail?
>>>
>>> Additional to that make sure that this set also keeps DRI2 working, in
>>> patch #2 it looks like you call the new function without checking if
>>> it's available or not.
>>>
>>> Keep in mind that we possible compile both DRI2 and DRI3 into the
>>> driver, but it can happen that we fallback to DRI2 on runtime.
>>
>> Patch 2 for me is corrupted fullscreen.
>>
>> Seems I have a mix of DRI2 and 3 according to below anyway.
>>
>> Am I supposed to be compiling xserver, amdgpu (ddx) or mesa in some
>> way that avoids this?
>>
>> grep DRI /var/log/Xorg.0.log
>> [ 35587.890] (II) glamor: EGL version 1.4 (DRI2):
>> [ 35588.093] (II) AMDGPU(0): [DRI2] Setup complete
>> [ 35588.093] (II) AMDGPU(0): [DRI2]   DRI driver: radeonsi
>> [ 35588.093] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi
>> [ 35588.093] (==) AMDGPU(0): DRI3 enabled
>> [ 35588.246] (II) GLX: Initialized DRI2 GL provider for screen 0
>
> That's nothing wrong. X set up services for both DRI2 and DRI3, so you
> have seen messages for both.

Thanks, I thought I'd better ask, just in case I was doing something 
stupid somewhere.

> You need check your client side if DRI3 is enabled.
> For mesa, run `LIBGL_DEBUG=verbose glxinfo > /dev/null', then should see
> something like "using DRI3 for screen..."
> If no, then rebuild mesa

libGL: Using DRI3 for screen 0




More information about the mesa-dev mailing list