Reviewed-by: Marek Olšák
Marek
On Wed, May 17, 2017 at 3:18 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> There is really no reason why the current DrawBuffer needs to be complete
> at this point. In particularly, the assertion gets hit on the X server side
> in libglx when running .../
From: Nicolai Hähnle
There is really no reason why the current DrawBuffer needs to be complete
at this point. In particularly, the assertion gets hit on the X server side
in libglx when running .../piglit/bin/glx-get-current-display-ext -auto
(which uses indirect GLX rendering).
Fixes: 19b61799e
