summaryrefslogtreecommitdiffstats
path: root/src/mesa
Commit message (Collapse)AuthorAgeFilesLines
* radeon: Add gcc attribute to enable pritnf format warnings.Pauli Nieminen2009-08-311-0/+16
|
* r100: Use shared debug code.Pauli Nieminen2009-08-3124-222/+125
| | | | | | Converted r100 to use shared debug code with sed and fast compile check. New code has compability layer so old debugging code doesn't have to be changed all immidiatly.
* radeon: Add common debugging functions.Pauli Nieminen2009-08-318-0/+213
| | | | | | | | | | These function are aiming to make it very simple to add and keep large amount of debugging code without having runtime impact in relase builds. Basic idea is to expose simple printf style debugging functions that are inlined. Level parameter will be evalueted in compile time so compiler can optimise some of debugging functions out if compile time request for debug level is too tight.
* mesa: added const qualifiers, move local varBrian Paul2009-08-311-7/+8
|
* mesa: fix saturation logic in emit_texenv()Brian Paul2009-08-311-1/+7
| | | | | | We need to clamp/saturate after each texenv stage, not just the last one. Fixes glean texEnv failure for softpipe (and probably other fragment program- based drivers).
* mesa: fix 32bit cross compilation on a 64bit machineMarc Dietrich2009-08-311-1/+1
| | | | | | | | | | | When cross compiling on a 64bit machine, gen_matypes.c is build for the host machine (64bit) but must generates code for the target machine (32bit). This causes wrong offsets all over the place and crashes googleearth on my machine. Solution is to add -m32 when cross compiling. Attached patch is compatible with linux-x86-32 and autoconf based builds.
* r600: add missing r7xx pci idAlex Deucher2009-08-312-0/+2
|
* mesa: set additional fields in _mesa_buffer_map_range()Brian Paul2009-08-311-3/+5
|
* mesa: set Length/Offset fields in _mesa_buffer_map()Brian Paul2009-08-311-0/+2
|
* mesa: additional assertions for ctx->Driver.UnmapBuffer()Brian Paul2009-08-311-4/+7
| | | | | The Pointer, Offset and Lenght fields should be cleared by the driver function since ctx->Driver.Unmap() may be called from VBO code, etc.
* intel: clear buffer fields in intel_bufferobj_unmap()Brian Paul2009-08-311-0/+2
|
* mesa: new assertions, comments about buffer mappingBrian Paul2009-08-311-12/+29
| | | | | | | Since ctx->Driver.MapBuffer() and ctx->Driver.MapBufferRange() may be called from other places in Mesa (such as VBO) it's important that the driver callbacks set all the buffer object fields properly (Pointer, Offset, Length, etc). Add assertions to make sure that the driver does that.
* st/mesa: fix obj->Pointer offset in st_bufferobj_map_range()Brian Paul2009-08-311-5/+5
| | | | | This fixes a bunch of gallium regressions since commit 8096aa521369c3bcf5226c060efa6dd06e48ddc8
* swrast: minor code consolidationBrian Paul2009-08-301-7/+2
|
* mesa: consolidate texture-related code in meta.cBrian Paul2009-08-301-262/+372
| | | | | Also, allow using texture rectangles, NPOT textures or regular POT textures (preferred in that order).
* intel: use more efficient loop over buffersBrian Paul2009-08-301-3/+7
|
* mesa: avoid redundant viewport changes in meta codeBrian Paul2009-08-301-3/+18
|
* i965: Fix segfault with ARB_oq CheckQuery when results are already fetched.Eric Anholt2009-08-291-1/+1
|
* i965: Support PROGRAM_ENV_PARAMs in brw_vs_emit.cEric Anholt2009-08-292-1/+4
|
* r300: Disable threshold register for KMS.Pauli Nieminen2009-08-291-1/+2
| | | | Kernel side doesn't have required register in safe list so can't send it kernel.
* r300: Swtcl prediction was still missing scissors.Pauli Nieminen2009-08-291-2/+3
| | | | All that state stuff should really be in state atoms :/
* r300: Add missing pre_emit_count to swtcl state size prediction.Pauli Nieminen2009-08-291-3/+4
|
* mesa: Update sconscript for new ARB/FP assembler.José Fonseca2009-08-291-0/+6
|
* Put 'extern' first on the line to silence GCC warnings.Ian Romanick2009-08-281-2/+2
|
* i965: Use VBOs in the VBO module on 965, now that we have ARB_map_buffer_range.Eric Anholt2009-08-281-0/+2
| | | | This looks like it's a small win on blender.
* vbo: Fix array pointer calculation for MapBufferRange-mapped vertex data.Eric Anholt2009-08-281-1/+3
| | | | | We would end up with the offset from the start of the mapping rather than the offset from the start of the buffer.
* intel: Add support for GL_ARB_map_buffer_range.Eric Anholt2009-08-285-35/+189
| | | | | Passes glean's bufferObject test, and should provide good performance in the cases applications are expected to use.
* i965: Implement ARB_oq CheckQuery in the intended way.Eric Anholt2009-08-281-6/+1
| | | | | Previously we blocked because I hadn't added the libdrm function. Now it's there, so update your libdrm.
* radeon: Fix swtcl emit pediction.Pauli Nieminen2009-08-294-45/+70
| | | | | | Problem was to find the correct place to run prediction. Only place that is called for every primitive is ALLOC_VERTS so we have to do prediction there before allocation.
* radeon: Fix scissors for dri1.Pauli Nieminen2009-08-281-4/+21
| | | | DRI1 has to set scissors in framebuffer coordinates.
* r100/r200: Bring back old PolygonStripple for DRI1.Pauli Nieminen2009-08-2811-14/+37
| | | | DRI1 didn't have support for command buffer emit for stripple.
* r100/r200: Share PolygonStripple code.Pauli Nieminen2009-08-285-56/+30
|
* r200: Fix piglit paths test.Pauli Nieminen2009-08-282-11/+17
| | | | | Polygon stipple has to go to command buffer because special ioctl is disabled. Piglit doesn't like HyperZ warning so disable it for kms.
* r600: fix scissor also.Dave Airlie2009-08-281-2/+2
| | | | I forgot about r600 being here.
* radeon: fix scissors harder.Dave Airlie2009-08-283-6/+6
| | | | this makes gnome-shell work on r300 for me
* intel: Add support for ARB_copy_buffer.Eric Anholt2009-08-272-2/+93
| | | | Passes glean's bufferObject test for this extension.
* r300: Fix emit prediction to account scissor emitting correctly.Pauli Nieminen2009-08-281-1/+1
|
* Merge branch 'mesa_7_5_branch'Brian Paul2009-08-273-15/+17
|\
| * swrast: fix incorrect tri culling in selection/feedback mode.Brian Paul2009-08-272-7/+9
| | | | | | | | See bug 16866.
| * mesa: direct program debug output to stderr instead of stdoutmarvin242009-08-271-9/+9
| |
* | i915: Fix undefined symbol as of eabe12df44a41e97fb5736959e8864ddbd01be14Eric Anholt2009-08-271-0/+1
| |
* | r300: Cleanup reported native program limitsNicolai Hähnle2009-08-271-6/+3
| | | | | | | | | | | | | | | | The fragment program native limits are actually higher on R4xx as reported by Alex Deucher, but using those requires some bit-twiddling changes to program handling. Signed-off-by: Nicolai Hähnle <[email protected]>
* | r300: Debug messages are written to stderr, so fflush thatNicolai Hähnle2009-08-275-10/+10
| | | | | | | | Signed-off-by: Nicolai Hähnle <[email protected]>
* | radeon/r200/r300: Fix swtcl prediction to work after primitie change.Pauli Nieminen2009-08-274-41/+86
| | | | | | | | | | Swtcl calls flush everytime primitive changes so prediction has to made again after flushing.
* | mesa: move decls before codeVinson Lee2009-08-271-2/+4
| |
* | radeon: fix scissor calcs.Dave Airlie2009-08-271-15/+20
| | | | | | | | | | | | For non-FBOs we need to invert, for FBOs the scissors are non-inverted. no matter what we need to clamp them to the buffer sizes.
* | i965: Increase assmebly shader program parameter limitsIan Romanick2009-08-261-2/+2
| | | | | | | | | | Increase the number of native program parameters to the same values exposed by GLSL.
* | ARB prog: Change handling of program parameter limitsIan Romanick2009-08-264-28/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Several changes are made to program parameter limits. Several of the non-NATIVE limits are set higher. All of the NATIVE limits are set to zero in the core Mesa code. Each driver must set the actual value in its context creation routine. If the NATIVE value remains zero, this indicates that hardware shaders may not be supported. Each of the preceeding changes matches the bahavior of Apple's shader assembler, so it seems safe. Finally, we limit the value of MaxEnvParams to be no greater than MaxNativeAttribs. At least one case has been found where an application does the wrong thing if MaxNativeAttribs < MaxEnvParams. See also bugzilla #23490.
* | radeon: fix max indx/vertex emission due to state checkerDave Airlie2009-08-272-2/+4
| |
* | r300/compiler: Fix vertex program MAD emitNicolai Hähnle2009-08-271-6/+46
| | | | | | | | | | | | | | Only use the macro variant of MAD when absolutely necessary. Apparently it cannot deal with relative addressing. Signed-off-by: Nicolai Hähnle <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-23 00:22:34 +0000