From 2c0ce92e8af4aab75f9a69a7913a1bec705220f3 Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Thu, 8 Jan 2009 16:15:31 -0700 Subject: docs: updated Cell docs, from gallium-0.2 branch --- docs/cell.html | 72 ++++++++++++++++++++++++++++++++++++++++++++++------------ 1 file changed, 57 insertions(+), 15 deletions(-) (limited to 'docs/cell.html') diff --git a/docs/cell.html b/docs/cell.html index f9915d67e5..7fbbba7c7e 100644 --- a/docs/cell.html +++ b/docs/cell.html @@ -6,7 +6,7 @@ -

Mesa Cell Driver

Mesa/Gallium Cell Driver

The Mesa @@ -23,18 +23,19 @@ Two phases are planned. First, to implement the framework for parallel rasterization using the Cell SPEs, including texture mapping. Second, to implement a full-featured OpenGL driver with support for GLSL, etc. +The second phase is now underway.

Source Code

-The Cell driver source code is on the gallium-0.1 branch of the -git repository. +The latest Cell driver source code is on the gallium-0.2 branch +of the Mesa git repository. After you've cloned the repository, check out the branch with:

-   git-checkout -b gallium-0.1 origin/gallium-0.1
+   git-checkout -b gallium-0.2 origin/gallium-0.2

To build the driver you'll need the IBM Cell SDK (version 2.1 or 3.0). @@ -43,12 +44,13 @@ or the Cell Simulator (untested, though).

-If using Cell SDK 3.0, first edit configs/linux-cell and add --DSPU_MAIN_PARAM_LONG_LONG to the SPU_CFLAGS. +If using Cell SDK 2.1, see the configs/linux-cell file for some +special changes.

To compile the code, run make linux-cell. +To build in debug mode, run make linux-cell-debug.

@@ -60,7 +62,7 @@ directory that contains libGL.so. Verify that the Cell driver is being used by running glxinfo and looking for:

-  OpenGL renderer string: Gallium 0.1, Cell on Xlib
+  OpenGL renderer string: Gallium 0.2, Cell on Xlib

@@ -77,21 +79,61 @@ SPU local store as needed. Similarly, textures are tiled and brought into local store as needed.

+ +

Status

+ +

+As of October 2008, the driver runs quite a few OpenGL demos. +Features that work include: +

Point/line/triangle rendering, glDrawPixels +
2D, NPOT and cube texture maps with nearest/linear/mipmap filtering +
Dynamic SPU code generation for fragment shaders, but not complete +
Dynamic SPU code generation for fragment ops (blend, Z-test, etc), but not complete +
Dynamic PPU/PPC code generation for vertex shaders, but not complete +

-More recently, vertex transformation has been parallelized across the SPUs -as well. +Performance has recently improved with the addition of PPC code generation +for vertex shaders, but the code quality isn't too great yet. +

+Another bottleneck is SwapBuffers. It may be the limiting factor for +many simple GL tests.

Status

+ +

Debug Options

-As of February 2008 the driver supports smooth/flat shaded triangle rendering -with Z testing and simple texture mapping. -Simple demos like gears run successfully. -To test texture mapping, try progs/demos/texcyl (press right mouse button for -rendering options). +The CELL_DEBUG env var can be set to a comma-separated list of one or +more of the following debug options:

checker - use a different background clear color for each SPU. + This lets you see which SPU is rendering which screen tiles. +
sync - wait/synchronize after each DMA transfer +
asm - print generated SPU assembly code to stdout +
fragops - emit fragment ops debug messages +
fragopfallback - don't use codegen for fragment ops +
cmd - print SPU commands as their received +
cache - print texture cache statistics when program exits +

+Note that some of these options may only work for linux-cell-debug builds. +

+ +

+If the GALLIUM_NOPPC env var is set, PPC code generation will not be used +and vertex shaders will be run with the TGSI interpreter. +

+If the GALLIUM_NOCELL env var is set, the softpipe driver will be used +intead of the Cell driver. +This is useful for comparison/validation. +

Contributing

-- cgit v1.2.3