Am Freitag, 22. Oktober 2004 13:28 schrieb Keith Whitwell:
Ian Romanick wrote:
Dieter Nützel wrote:
Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
There is disagreement about the meaning of the CLIPSPAN _n parameter in
CVS.
The drivers I have looked at and
Ian Romanick wrote:
Dieter Nützel wrote:
Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
There is disagreement about the meaning of the CLIPSPAN _n parameter in
CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat
_n as
the number of pixels in the span after
On Thu, Oct 21, 2004 at 11:49:20PM +0200, Dieter Nützel wrote:
Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
Hi,
There is disagreement about the meaning of the CLIPSPAN _n parameter in
CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat _n as
the
Dieter Nützel wrote:
Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
There is disagreement about the meaning of the CLIPSPAN _n parameter in
CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat _n as
the number of pixels in the span after clipping.
depthtmp.h and
On Thu, Oct 21, 2004 at 03:35:21PM -0700, Ian Romanick wrote:
Dieter Nützel wrote:
Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
There is disagreement about the meaning of the CLIPSPAN _n parameter in
CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat
Hi,
There is disagreement about the meaning of the CLIPSPAN _n parameter in CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat _n as
the number of pixels in the span after clipping.
depthtmp.h and stenciltmp.h treat _n as the end+1 x coordinate of the span.
This
