# [cairo-commit] papers/opengl_freenix04 opengl_freenix04.tex, 1.40, 1.41

David Reveman commit at pdx.freedesktop.org
Mon Apr 5 06:18:46 PDT 2004

Committed by: davidr

Update of /cvs/cairo/papers/opengl_freenix04
In directory pdx:/tmp/cvs-serv4361

Modified Files:
opengl_freenix04.tex
Log Message:
text

Index: opengl_freenix04.tex
===================================================================
RCS file: /cvs/cairo/papers/opengl_freenix04/opengl_freenix04.tex,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** a/opengl_freenix04.tex	4 Apr 2004 19:26:23 -0000	1.40
--- b/opengl_freenix04.tex	5 Apr 2004 13:18:44 -0000	1.41
***************
*** 123,136 ****
XAA breaks down complex Render operations into simpler ones and
accelerates them if support is provided by the driver, otherwise it falls
!   back on software. This requires graphics driver developers to add their
!   own XAA Render hooks in each driver to support it, which results in a
!   duplicated effort. Unfortunately not many drivers have much support for
!   XAA Render hooks at this point. This results in inconsistent acceleration
!   between different drivers and hardware.

!   From the benchmarks made in the context of this project the conclusion can
!   be made that the amount of accelerated rendering achieved by Render doesn't
!   seem to be enough for the complex visual effects addressed by this project.
!   See section~\ref{section: Results} Results for documented benchmark tests.

\subsection{\Libname{} Fundamentals}
--- 123,139 ----
XAA breaks down complex Render operations into simpler ones and
accelerates them if support is provided by the driver, otherwise it falls
!   back on software. To fall back on software means that all calculations
!   are processed by the local CPU. For most XFree86 drivers, image
!   data lives in video memory, so for the CPU to be able to access this data
!   it must first be fetched from video memory. The CPU can then perform
!   its calculations and the image data must then be transfered back to video
!   memory.

!   The ideal situation would be to have XAA Render hooks for all Render
!   operations in every driver. This requires graphics driver developers to add
!   XAA Render hooks in each driver, which results in a duplicated effort.
!   Unfortunately, not many drivers have much support for XAA Render hooks at
!   this point. This results in inconsistent acceleration between different
!   drivers and hardware.

\subsection{\Libname{} Fundamentals}