summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* gallium: drivers should reference vertex buffersMarek Olšák2011-01-0617-52/+89
| | | | So that a state tracker can unreference them after set_vertex_buffers.
* st/mesa: optimize constant buffer uploadsMarek Olšák2011-01-064-34/+20
| | | | | | | | | | | | | The overhead of resource_create, transfer_inline_write, and resource_destroy to upload constant data is very visible with some apps in sysprof, and as such should be eliminated. My approach uses a user buffer to pass a pointer to a driver. This gives the driver the freedom it needs to take the fast path, which may differ for each driver. This commit addresses the same issue as Jakob's one that suballocates out of a big constant buffer, but it also eliminates the copy to the buffer.
* st/mesa: do sanity checks on states only in debug buildsMarek Olšák2011-01-061-0/+4
|
* u_upload_mgr: new featuresMarek Olšák2011-01-066-36/+115
| | | | | | | | | | | | | | - Added a parameter to specify a minimum offset that should be returned. r300g needs this to better implement user buffer uploads. This weird requirement comes from the fact that the Radeon DRM doesn't support negative offsets. - Added a parameter to notify a driver that the upload flush occured. A driver may skip buffer validation if there was no flush, resulting in a better performance. - Added a new upload function that returns a pointer to the upload buffer directly, so that the buffer can be filled e.g. by the translate module.
* u_upload_mgr: keep the upload buffer mapped until it is flushedMarek Olšák2011-01-061-52/+14
| | | | | | | The map/unmap overhead can be significant even though there is no waiting on busy buffers. There is simply a huge number of uploads. This is a performance optimization for Torcs, a car racing game.
* mesa: fix build for NetBSDPierre Allegraud2011-01-063-25/+8
| | | | | | | | See http://bugs.freedesktop.org/show_bug.cgi?id=32859 NOTE: This is a candidate for the 7.9 and 7.10 branches. Signed-off-by: Brian Paul <brianp@vmware.com>
* glext: upgrade to version 67Brian Paul2011-01-061-2/+12
|
* mesa: Clean up header file inclusion in version.c.Vinson Lee2011-01-061-1/+1
| | | | | Include imports.h directly instead of indirectly through context.h. version.c does use any symbols that are added by context.h.
* nvc0: Fix typo of nvc0_mm.c in SConscript.Vinson Lee2011-01-061-1/+1
|
* mesa: bump version to 7.11Vinson Lee2011-01-053-5/+5
|
* mesa: Include mtypes.h in files that use gl_context struct.Vinson Lee2011-01-0536-0/+36
| | | | | | Directly include mtypes.h if a file uses a gl_context struct. This allows future removal of headers that are not strictly necessary but indirectly include mtypes.h for a file.
* i965: skip too small size mipmapZou Nan hai2011-01-061-2/+4
| | | | this fixes doom3 crash.
* i915: Fix build for previous commit.Eric Anholt2011-01-051-11/+11
|
* intel: Always allocate miptrees from level 0, not tObj->BaseLevel.Eric Anholt2011-01-059-141/+71
| | | | | | | | | | | BaseLevel/MaxLevel are mostly used for two things: clamping texture access for FBO rendering, and limiting the used mipmap levels when incrementally loading textures. By restricting our mipmap trees to just the current BaseLevel/MaxLevel, we caused reallocation thrashing in the common case, for a theoretical win if someone really did want just levels 2..4 or whatever of their texture object. Bug #30366
* intel: Drop unused first/lastlevel args to miptree_create_for_region.Eric Anholt2011-01-053-8/+3
| | | | We're always making a single-level, 0-baselevel miptree.
* swrast: Include mtypes.h in s_triangle.c.Vinson Lee2011-01-051-0/+1
| | | | Include mtypes.h for gl_context symbol.
* st/mesa: Include mtypes.h in st_cb_drawpixels.c.Vinson Lee2011-01-051-0/+1
| | | | Include mtypes.h for gl_context symbol.
* intel: Clarify first_level/last_level vs baselevel/maxlevel by deletion.Eric Anholt2011-01-057-56/+30
| | | | | | | | | This has always been ugly about our texture code -- object base/max level vs intel object first/last level vs image level vs miptree first/last level. We now get rid of intelObj->first_level which is just tObj->BaseLevel, and make intelObj->_MaxLevel clearly based off of tObj->_MaxLevel instead of duplicating its code (incorrectly, as image->MaxLog2 only considers width/height and not depth!)
* mesa: Consider textures incomplete when maxlevel < baselevel.Eric Anholt2011-01-051-0/+6
| | | | | See section 3.8.10 of the GL 2.1 specification. There's no way to do anything sane with that, and drivers would get all sorts of angry.
* i915: Enable LOD preclamping on 8xx like on 915/965.Eric Anholt2011-01-052-0/+3
| | | | Fixes lodclamp-between and lodclamp-between-max.
* i915: Implement min/max lod clamping in hardware on 8xx.Eric Anholt2011-01-053-25/+32
| | | | | This avoids 8xx-specific texture relayout for min/max lod changes. One step closer to avoiding relayout for base/maxlevel changes!
* intel: Drop TEXTURE_RECTANGLE check in miptree layout setup.Eric Anholt2011-01-051-37/+24
| | | | | It's already handled by our non-mipmapped MinFilter, since TEXTURE_RECTANGLE is always NEAREST or LINEAR.
* intel: Clean up redundant setup of firstLevel.Eric Anholt2011-01-051-5/+4
| | | | | It's always BaseLevel (since TEXTURE_RECTANGLE's baselevel can't be changed from 0), except for 8xx minlod hilarity.
* intel: Drop a check for GL_TEXTURE_4D_SGIS.Eric Anholt2011-01-051-1/+0
| | | | | The SGIS_texture4D extension was thankfully never completed, so we couldn't implement it if we wanted to.
* swrast: Remove unnecessary headers.Vinson Lee2011-01-052-2/+0
|
* i965: Simplify the renderbuffer setup code.Eric Anholt2011-01-051-102/+93
| | | | | | It was quite a mess by trying to do NULL renderbuffers and real renderbuffers in the same function. This clarifies the common case of real renderbuffers.
* st/xorg: Flesh out colour map support and support depth 8.Michel Dänzer2011-01-053-1/+80
|
* i965: use BLT to clear buffer if possible on SandybridgeXiang, Haihao2011-01-051-6/+0
| | | | This fixes https://bugs.freedesktop.org/show_bug.cgi?id=32713
* i965: Add support for SRGB DXT1 formats.Eric Anholt2011-01-043-2/+10
| | | | | | | | | | This makes fbo-generatemipmap-formats GL_EXT_texture_sRGB-s3tc match fbo-generatemipmap-formats GL_EXT_texture_compression_s3tc and swrast in bad DXT1_RGBA alpha=0 handling, but it means we won't unpack and repack someone's textures into uncompressed SARGB8 format.
* glcpp: Add test for recursive #define.Vinson Lee2011-01-041-0/+3
|
* mesa: Fix the baseFormat for GL_COMPRESSED_SLUMINANCE_EXT.Eric Anholt2011-01-041-1/+1
| | | | | | | It's just LUMINANCE, not LUMINANCE_ALPHA. Fixes fbo-generatemipmap-formats GL_EXT_texture_sRGB-s3tc assertion failure when it tries to pack the L8 channels into LUMINANCE_ALPHA and wonders why it's trying to do that.
* intel: Merge our choosetexformat fallbacks into core.Eric Anholt2011-01-046-230/+107
| | | | | | We now share the type/format -> MESA_FORMAT_* mappings with software mesa, and the core supports most of the fallbacks hardware drivers will want.
* mesa: Make _mesa_choose_tex_format() choose formats out of a supported table.Eric Anholt2011-01-043-91/+183
| | | | | Right now this is just tweaking the current code to look at the table. Choosing actually supported formats will come later.
* glcpp: Add division by zero test cases.Vinson Lee2011-01-042-0/+4
|
* mesa: preserve 10 bits of precision in the texstore general path for ARGB2101010Marek Olšák2011-01-043-15/+25
| | | | | Use make_temp_float_image instead of _make_temp_chan_image. The latter converts the texture to 8 bits/component, losing 2 bits.
* st/mesa: advertise GL_ARB_half_float_pixelMarek Olšák2011-01-041-0/+1
| | | | This extension doesn't appear to need any driver-specific parts.
* r300/compiler: disable the rename_regs pass for loopsMarek Olšák2011-01-041-0/+8
| | | | | | This workaround fixes rendering of kwin thumbnails. NOTE: This is a candidate for the 7.9 and 7.10 branches.
* r600g: support up to 64 shader constantsAlex Deucher2011-01-042-1/+20
| | | | | | | | | | | | | | | | | | | From the r600 ISA: Each ALU clause can lock up to four sets of constants into the constant cache. Each set (one cache line) is 16 128-bit constants. These are split into two groups. Each group can be from a different constant buffer (out of 16 buffers). Each group of two constants consists of either [Line] and [Line+1] or [line + loop_ctr] and [line + loop_ctr +1]. For supporting more than 64 constants, we need to break the code into multiple ALU clauses based on what sets of constants are needed in that clause. Note: This is a candidate for the 7.10 branch. Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
* r300/compiler: Fix black terrain in Civ4Tom Stellard2011-01-041-8/+1
| | | | | | | rc_inst_can_use_presub() wasn't checking for too many RGB sources in Alpha instructions or too many Alpha sources in RGB instructions. Note: This is a candidate for the 7.10 branch.
* glsl: Check that integer vertex outputs are qualified with flatChad Versace2011-01-041-0/+19
| | | | | | | | | | Perform this check in ast_declarator_list::hir(). From section 4.3.6 of the GLSL 1.30 spec: "If a vertex output is a signed or unsigned integer or integer vector, then it must be qualified with the interpolation qualifier flat."
* glsl: Allow redeclaration of gl_Color and its variants in GLSL 1.30Chad Versace2011-01-041-0/+21
| | | | | | | | | | | | | Allow redeclaration of the following built-in variables with an interpolation qualifier in language versions >= 1.30: * gl_FrontColor * gl_BackColor * gl_FrontSecondaryColor * gl_BackSecondaryColor * gl_Color * gl_SecondaryColor See section 4.3.7 of the GLSL 1.30 spec.
* glsl: Comment ast_type_qualifier.flagsChad Versace2011-01-041-1/+5
|
* intel: When validating an FBO's combined depth/stencil, use the given FBO.Eric Anholt2011-01-041-4/+4
| | | | | | | We were looking at the current draw buffer instead to see whether the depth/stencil combination matched. So you'd get told your framebuffer was complete, until you bound it and went to draw and we decided that it was incomplete.
* intel: Fix segfaults from trying to use _ColorDrawBuffers in FBO validation.Eric Anholt2011-01-041-4/+16
| | | | | | | | | | | | | | The _ColorDrawBuffers is a piece of computed state that gets for the current draw/read buffers at _mesa_update_state time. However, this function actually gets used for non-current draw/read buffers when checking if an FBO is complete from the driver's perspective. So, instead of trying to just look at the attachment points that are currently referenced by glDrawBuffers, look at all attachment points to see if they're driver-supported formats. This appears to actually be more in line with the intent of the spec, too. Fixes a segfault in my upcoming fbo-clear-formats piglit test, and hopefully bug #30278
* Merge remote branch 'origin/nvc0'Christoph Bumiller2011-01-0449-12/+17359
|\
| * nvc0: fix index size method value for u8 indicesChristoph Bumiller2011-01-041-8/+2
| |
| * nvc0: set the correct FP header bit for multiple colour outputsChristoph Bumiller2011-01-041-1/+1
| |
| * nvc0: delete memory caches and fence on screen destructionChristoph Bumiller2011-01-044-0/+50
| |
| * nvc0: use mov instead of ld for scalar const loadsChristoph Bumiller2011-01-041-1/+6
| |
| * nvc0: fix resource unmap after vertex pushChristoph Bumiller2011-01-043-10/+8
| |