[Mesa-dev] [PATCH 1/3] main: call invalidate_framebuffer_storage() with driver's viewport limits
Samuel Iglesias Gonsálvez
siglesias at igalia.com
Tue Mar 1 14:22:03 UTC 2016
Don't use hardcoded ones because the driver can set different ones.
Signed-off-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
---
src/mesa/main/fbobject.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/mesa/main/fbobject.c b/src/mesa/main/fbobject.c
index 621f84f..351023e 100644
--- a/src/mesa/main/fbobject.c
+++ b/src/mesa/main/fbobject.c
@@ -4161,7 +4161,8 @@ _mesa_InvalidateFramebuffer(GLenum target, GLsizei numAttachments,
*/
invalidate_framebuffer_storage(ctx, fb, numAttachments, attachments,
0, 0,
- MAX_VIEWPORT_WIDTH, MAX_VIEWPORT_HEIGHT,
+ ctx->Const.MaxViewportWidth,
+ ctx->Const.MaxViewportHeight,
"glInvalidateFramebuffer");
}
@@ -4201,7 +4202,8 @@ _mesa_InvalidateNamedFramebufferData(GLuint framebuffer,
*/
invalidate_framebuffer_storage(ctx, fb, numAttachments, attachments,
0, 0,
- MAX_VIEWPORT_WIDTH, MAX_VIEWPORT_HEIGHT,
+ ctx->Const.MaxViewportWidth,
+ ctx->Const.MaxViewportHeight,
"glInvalidateNamedFramebufferData");
}
--
2.7.0
More information about the mesa-dev
mailing list