Re: [Mesa-dev] [PATCH] brw_clear: fix noop_scissor range issue on width/height

2016-08-31 Thread Matt Turner
On Wed, Aug 31, 2016 at 1:05 PM, Matt Turner wrote: > From: Jordan Justen > > If scissor X or Y was set to a negative value then the previous > code might have indicated noop scissors when the scissor range > actually was masking a portion of the framebuffer. > > Since fb->_Xmin, _Xmax, _Ymin and

[Mesa-dev] [PATCH] brw_clear: fix noop_scissor range issue on width/height

2016-08-31 Thread Matt Turner
From: Jordan Justen If scissor X or Y was set to a negative value then the previous code might have indicated noop scissors when the scissor range actually was masking a portion of the framebuffer. Since fb->_Xmin, _Xmax, _Ymin and _Ymax take scissors into account, we can use these to test for a