Hi,
On 05/09/2017 08:37, Thomas Hellstrom wrote:
Hi!
On 09/05/2017 07:36 AM, Axel Davy wrote:
On 04/09/2017 14:27, Thomas Hellstrom wrote:
The copySubBuffer functionality always attempted a server side blit
from
back to fake front if a fake front was present, and we weren't
displaying
on a
On 09/05/2017 08:49 AM, Axel Davy wrote:
Hi,
[...]
Reviewed-by: Axel Davy
Thanks for reviewing, Axel.
/Thomas
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Hi!
On 09/05/2017 07:36 AM, Axel Davy wrote:
On 04/09/2017 14:27, Thomas Hellstrom wrote:
The copySubBuffer functionality always attempted a server side blit from
back to fake front if a fake front was present, and we weren't
displaying
on a remote GPU.
Now that we always have local blit cap
On 04/09/2017 14:27, Thomas Hellstrom wrote:
The copySubBuffer functionality always attempted a server side blit from
back to fake front if a fake front was present, and we weren't displaying
on a remote GPU.
Now that we always have local blit capability on modern drivers, first
attempt a local
On 04/09/17 09:27 PM, Thomas Hellstrom wrote:
> The copySubBuffer functionality always attempted a server side blit from
> back to fake front if a fake front was present, and we weren't displaying
> on a remote GPU.
>
> Now that we always have local blit capability on modern drivers, first
> attem
The copySubBuffer functionality always attempted a server side blit from
back to fake front if a fake front was present, and we weren't displaying
on a remote GPU.
Now that we always have local blit capability on modern drivers, first
attempt a local blit, and only if that fails, try the server bl