summaryrefslogtreecommitdiffstats
path: root/src/gallium
Commit message (Collapse)AuthorAgeFilesLines
* r300/compiler: implement DP2 opcodeMarek Olšák2010-08-161-1/+1
|
* r300/compiler: implement SSG opcodeMarek Olšák2010-08-161-1/+1
|
* llvmpipe: special case triangles which fall in a single 16x16 blockKeith Whitwell2010-08-153-0/+106
| | | | | Check for these and route them to a dedicated handler with one fewer levels of recursive rasterization.
* llvmpipe: consolidate several loops in lp_rast_triangleKeith Whitwell2010-08-151-18/+15
|
* llvmpipe: remove all traces of step arrays, pos_tablesKeith Whitwell2010-08-153-114/+0
| | | | | No need to calculate these values any longer, nor to store them in the bin data. Improves isosurf a bit more, 115->123 fps.
* llvmpipe: eliminate last usage of step array in rast_tmp.hKeith Whitwell2010-08-152-16/+57
| | | | | | | | | | | | For 16 and 64 pixel levels, calculate a mask which is linear in x and y (ie not in the swizzle layout). When iterating over full and partial masks, figure out position by manipulating the bit number set in the mask, rather than relying on postion arrays. Similarly, calculate the lower-level c values from dcdx, dcdy and the position rather than relying on the step array.
* llvmpipe: don't refer to plane->step when dcdx or dcdy would doKeith Whitwell2010-08-151-6/+6
|
* llvmpipe: also use build_mask at 16, 64 pixel levelsKeith Whitwell2010-08-151-28/+19
|
* llvmpipe: version of block4 which doesn't need the full step arrayKeith Whitwell2010-08-152-7/+27
| | | | No noticable slowdown with isosurf.
* llvmpipe: reorganize block4 loop, nice speedupKeith Whitwell2010-08-152-12/+19
| | | | | isosurf 95->115 fps just by exchanging the two inner loops in this function...
* gallium/docs: Cleanup debugging. Spelling, grammar, organization.Corbin Simpson2010-08-151-25/+30
|
* gallium/docs: Add formatting for envvar role; change debugging.Corbin Simpson2010-08-154-30/+44
| | | | | Per Jakob's request. Not super-pretty, but it's a good point for modding later.
* r300g: mark HiZ/ZMask_clear atoms as non-dirty after emission in clearMarek Olšák2010-08-151-1/+4
|
* r300g: do not use HiZ if HiZ RAM is not properly initializedMarek Olšák2010-08-155-18/+23
|
* r300g: rename dirty_zmask -> zmask_in_useMarek Olšák2010-08-155-13/+13
|
* r300g: do not clear with blitter if we clear just the ZMask RAMMarek Olšák2010-08-151-9/+37
| | | | | This skips the blitter clear path entirely if the color is not cleared and the depth+stencil is cleared with the ZMask.
* r300g: do not use fastfill if ZMask RAM is not properly initializedMarek Olšák2010-08-154-18/+31
| | | | z_fastfill -> dirty_zmask[level].
* r300g: separate num_cs_end_dwords out from prepare_for_renderingMarek Olšák2010-08-153-24/+25
|
* gallium/docs: Add rbug to distributionJakob Bornecrantz2010-08-151-0/+5
|
* gallium/docs: Add a debugging sectionJakob Bornecrantz2010-08-152-0/+97
|
* gallium: Make printing info on debug builds default offJakob Bornecrantz2010-08-154-4/+4
| | | | | | | This commit silences the printing off most of the debug information when running debug builds. The big culprits are: the tgsi sanity checker that gets run on all shaders on debug; all the options; and finaly the cpu caps printer.
* gallivm: Remove unnecessary header.Vinson Lee2010-08-141-1/+0
|
* scons: Fix r600g build.Vinson Lee2010-08-142-1/+26
|
* r600g: Remove unnecessary headers.Vinson Lee2010-08-142-2/+0
|
* r300g: Remove unnecessary header.Vinson Lee2010-08-141-1/+0
|
* u_cpu_detect: remove arch and little_endianLuca Barbieri2010-08-144-35/+9
| | | | | This logic duplicates the one in p_config.h, so remove it and adjust the only two places that were using it.
* gallivm: Refactor the Newton-Rapshon steps, and disable once again.José Fonseca2010-08-141-28/+83
| | | | It causes a very ugly corruption on the Earth's halo on Google Earth.
* st/dri: make dri_drawable_validate_att staticGeorge Sapountzis2010-08-132-7/+2
|
* st/dri: move TFP code to dri_drawable.cGeorge Sapountzis2010-08-133-52/+55
| | | | | | | | | | | | | | | | | | | | This is based on a patch by nobled <[email protected]> and allows the TFP extension to be enabled for DRISW also. This patch does not enable TFP for DRISW though, because testing on xephyr segfaults here (for both classic and gallium): Program received signal SIGSEGV, Segmentation fault. 0x00786a4a in _mesa_GenTextures (n=1, textures=0xbfffee4c) at main/texobj.c:788 788 ASSERT_OUTSIDE_BEGIN_END(ctx); (gdb) (gdb) where \#0 0x00786a4a in _mesa_GenTextures (n=1, textures=0xbfffee4c) at main/texobj.c:788 \#1 0x0817a004 in __glXDisp_GenTextures () \#2 0x08168498 in __glXDispatch () \#3 0x0808b6ce in Dispatch () \#4 0x08084435 in main () The TFP code is generic except for the teximage call. We need to verify that DRISW correclty implements whatever hook teximage finally calls.
* st/dri: Fix segmentation fault in sw driversnobled2010-08-131-2/+2
|
* st/dri: dri_drawable_get_format is shared between DRI2 and DRISWGeorge Sapountzis2010-08-131-31/+2
|
* r300g: do not support separate depth/stencil clear in the driverMarek Olšák2010-08-131-3/+1
| | | | It doesn't work well with Hyper-Z, so put the burden on the state tracker.
* r300g: fix fastfill when color and Z clear are invoked separatelyMarek Olšák2010-08-132-2/+2
| | | | This always restores the previous depth clear value after CBZB clear.
* r600g: update shader capsMarek Olšák2010-08-131-5/+13
| | | | | | Sent on ML by Владимир. These values are what fglrx returns.
* r300g: disable depth clamp for nowMarek Olšák2010-08-131-1/+1
| | | | | | | It breaks Regnum Online in that it renders random triangles all over the screen. https://bugs.freedesktop.org/show_bug.cgi?id=29518
* r600g: fix warning in the winsysDave Airlie2010-08-131-1/+1
|
* r600g: fix memory leaks running gears.Dave Airlie2010-08-132-0/+6
| | | | | I noticed gears memory usage was heading skywards, some r600 "states" aren't properly refcounted, and the ctx->state is never freed.
* translate_test: Fix compilation with MSVC.Vinson Lee2010-08-121-1/+2
|
* translate_test: fix compilation on non-POSIX platformsLuca Barbieri2010-08-121-5/+19
| | | | Use a kludgy function based on rand() instead of drand48()
* translate_test: improveLuca Barbieri2010-08-121-6/+60
| | | | | | | 1. Generate random data specifically for float and doubles, so that they end up in [0, 1] range 2. Don't test useless conversions like SCALED <-> NORM 3. Poison the buffers before testing
* Revert "u_blitter: unify clear_depth_stencil and flush_depth_stencil"Marek Olšák2010-08-123-3/+49
| | | | This reverts commit de4784e36505316c2a5ab34cc5b371d17f38d3c5.
* r600g: fix typo in stencil translate.Dave Airlie2010-08-121-1/+1
| | | | fixes piglit stencil-twoside and stencil-wrap
* r600g: fix provoking-vertex piglit test.Dave Airlie2010-08-121-8/+12
|
* r600g: improve texture format checker.Dave Airlie2010-08-124-12/+263
| | | | | | | | | This takes the r300g texture format checker and fixes it up for r600g, it passes glean texSwizzle, pixelformats, and texture_srgb tests, however I think it L8S8_SRGB is broken as is L8_SRGB, need to investigate. Signed-off-by: Dave Airlie <[email protected]>
* u_blitter: unify clear_depth_stencil and flush_depth_stencilMarek Olšák2010-08-123-49/+3
| | | | No need to enable depth test for clear.
* scons: Fix freebsd8 build.Vinson Lee2010-08-112-2/+8
|
* translate_test: fix segfault on x86-64Luca Barbieri2010-08-111-2/+6
|
* u_staging: remove useless inline keywordLuca Barbieri2010-08-111-1/+1
|
* translate_test: fix, reindent, and improveLuca Barbieri2010-08-111-137/+204
| | | | | | | 1. Fix the segfault due to the reverted commit using the new interface 2. Reindent to Mesa 3 spaces style 3. Improve output and return success/failure with error code 4. Add much better support for testing translate_sse
* translate: allow clients to ask for supported output formatsLuca Barbieri2010-08-113-0/+88
| | | | | | | | | | | | | Currently translate asserts on unsupported output formats, making it impossible to use for some purposes, such as testing whether it actually works on all formats it supports. Removing the assert was met with opposition, so this change allows clients to ask whether an output format is supported, and they are thus able to avoid attempting to use it. Since this is just an addition to the API, no adverse effect is possible, and it makes the testsuite work again.