On Thu, Feb 15, 2018 at 7:57 AM, Daniel Stone wrote:
> From: Louis-Francis Ratté-Boulianne
>
> If PresentCompleteNotify event says the pixmap was presented
> with mode PresentCompleteModeSuboptimalCopy, it means the pixmap
> could possibly have been flipped instead if allocated with a
> differen
On 2018-02-15 05:17 PM, Daniel Stone wrote:
> Hi Michel,
>
> On 15 February 2018 at 16:14, Michel Dänzer wrote:
>> On 2018-02-15 04:57 PM, Daniel Stone wrote:
>>> @@ -885,6 +901,11 @@ loader_dri3_swap_buffers_msc(struct
>>> loader_dri3_drawable *draw,
>>>if (!loader_dri3_have_image_blit(
Hi Michel,
On 15 February 2018 at 16:14, Michel Dänzer wrote:
> On 2018-02-15 04:57 PM, Daniel Stone wrote:
>> @@ -885,6 +901,11 @@ loader_dri3_swap_buffers_msc(struct
>> loader_dri3_drawable *draw,
>>if (!loader_dri3_have_image_blit(draw) && draw->cur_blit_source != -1)
>> opt
On 2018-02-15 04:57 PM, Daniel Stone wrote:
> From: Louis-Francis Ratté-Boulianne
>
> If PresentCompleteNotify event says the pixmap was presented
> with mode PresentCompleteModeSuboptimalCopy, it means the pixmap
> could possibly have been flipped instead if allocated with a
> different format/m
From: Louis-Francis Ratté-Boulianne
If PresentCompleteNotify event says the pixmap was presented
with mode PresentCompleteModeSuboptimalCopy, it means the pixmap
could possibly have been flipped instead if allocated with a
different format/modifier.
Signed-off-by: Louis-Francis Ratté-Boulianne
