[Xorg] Re: Xorg tinderbox status

Thomas Winischhofer thomas at winischhofer.net
Tue Aug 17 05:19:25 PDT 2004


Bryce Harrington wrote:
> Yeah, I've been playing with various bits, and in fact was just playing
> with rendercheck about an hour ago.  'rendertest' is part of Cairo, but
> I think I must have typoed it in the list above - 'rendercheck' is the
> thing we want.  It pops up a little window that flashes colors for a
> while, and prints out stuff like this:
> 
> src: 1x1R r8g8b8, mask: 10x10 r8g8b8, dst: r8g8b8 window
> ConjointXor CA composite test error of 64.0000 at (0, 0) --
> got:       0.00 1.00 0.00 1.00
> expected:  0.00 0.00 0.00 1.00
> src color: 0.00 1.00 0.00 1.00
> msk color: 0.00 1.00 0.00 1.00
> dst color: 0.00 1.00 0.00 1.00
> src: 10x10 r8g8b8, mask: 1x1R r8g8b8, dst: r8g8b8 window
> ConjointXor CA composite test error of 64.0000 at (0, 0) --
> got:       0.00 1.00 0.00 1.00
> expected:  0.00 0.00 0.00 1.00
> src color: 0.00 1.00 0.00 1.00
> msk color: 0.00 1.00 0.00 1.00
> dst color: 0.00 1.00 0.00 1.00
> 
> I don't know how to interpret those results, though, and suspect that
> like usual the value is in the analysis here...

rendercheck checks RENDER using various PictOps and various texture formats.

The results you get mean that several pixels of the RENDERed result 
don't match the expected result. For each wrongly rendered pixel a table 
like this is generated:

              R    G    B    A

 > got:       0.00 1.00 0.00 1.00
 > expected:  0.00 0.00 0.00 1.00
 > src color: 0.00 1.00 0.00 1.00
 > msk color: 0.00 1.00 0.00 1.00
 > dst color: 0.00 1.00 0.00 1.00

1.0 means "white" (ie 255 in 8bit-per-colorchannel-mode), 0.0 means "black".

"Got" is the result from a GetImage call and evaluating the pixel 
colors, ie the actual result of the RENDER operation (whose operation is 
described in the line above the table)

"expected" is what the pixel's color channels should be

"src", "msk", "dst" are the source, mask and destination colors.

Seeing such a table means that RENDER did not render correctly. Such 
errors should not occure if the driver in use has no RENDER 
acceleration. If it does, it means that the driver's RENDER acceleration 
is broken.

Thomas


-- 
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net	       *** http://www.winischhofer.net
twini AT xfree86 DOT org



More information about the xorg mailing list