On 25.03.2016 20:24, Andy Furniss wrote:
> Andy Furniss wrote:
>> Michel Dänzer wrote:
>>> From: Michel Dänzer
>>>
>>> This reverts commit cd94248ffa7d8fe0b57476f79e7e860dee66d1b0.
>>>
>>> It broke VDPAU<->GL interop with DRI3 enabled, because the Gallium VDPAU
>>> code doesn't support DRI3 yet. W
Andy Furniss wrote:
Michel Dänzer wrote:
From: Michel Dänzer
This reverts commit cd94248ffa7d8fe0b57476f79e7e860dee66d1b0.
It broke VDPAU<->GL interop with DRI3 enabled, because the Gallium VDPAU
code doesn't support DRI3 yet. We can consider re-enabling this once
there is a Mesa release wher
Michel Dänzer wrote:
From: Michel Dänzer
This reverts commit cd94248ffa7d8fe0b57476f79e7e860dee66d1b0.
It broke VDPAU<->GL interop with DRI3 enabled, because the Gallium VDPAU
code doesn't support DRI3 yet. We can consider re-enabling this once
there is a Mesa release where the Gallium VDPAU c
On Thu, Mar 24, 2016 at 10:54 PM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> This reverts commit cd94248ffa7d8fe0b57476f79e7e860dee66d1b0.
>
> It broke VDPAU<->GL interop with DRI3 enabled, because the Gallium VDPAU
> code doesn't support DRI3 yet. We can consider re-enabling this once
> ther
From: Michel Dänzer
This reverts commit cd94248ffa7d8fe0b57476f79e7e860dee66d1b0.
It broke VDPAU<->GL interop with DRI3 enabled, because the Gallium VDPAU
code doesn't support DRI3 yet. We can consider re-enabling this once
there is a Mesa release where the Gallium VDPAU code supports DRI3.
Bug