summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* r300: always emit output insts after all KIL instsMaciej Cencora2009-04-272-3/+46
|
* r300-gallium: Correctly flush Draw.Corbin Simpson2009-04-261-1/+5
| | | | Should help with a few non-TCL bugs.
* r300-gallium: Add a draw_flush() to r300_flush().Mathias Gottschlag2009-04-261-0/+2
| | | | This fixes some missing primitives which had been drawn right before the next glClear().
* r300-gallium: Fix vertex shader OVM counting.Corbin Simpson2009-04-252-6/+44
| | | | | | Attribs must be packed: position, point size, colors, texcoords. Thanks to osiris for pointing it out.
* r300-gallium: Clean up FB state emit.Corbin Simpson2009-04-251-13/+13
|
* r300-gallium: Set framebuffer pitch on every framebuffer change.Mathias Gottschlag2009-04-251-1/+6
| | | | Signed-off-by: Corbin Simpson <[email protected]>
* gallium-intel: Fix warningJakob Bornecrantz2009-04-251-2/+0
|
* gallium-intel: Cache software switchJakob Bornecrantz2009-04-253-2/+7
|
* gallium-intel: Link dri2 driver with softpipeJakob Bornecrantz2009-04-251-0/+1
|
* intel: Fix more issues with the combined depth-stencil attachmentIan Romanick2009-04-241-6/+13
|
* intel: Initialize region ptr to prevent assertion in intel_region_referenceIan Romanick2009-04-241-1/+1
|
* tgis: SSE code generator doesn't yet support indirect addressing of temp regsBrian Paul2009-04-241-0/+29
| | | | Fall back to interpreter in this case.
* intel / DRI2: When available, use DRI2GetBuffersWithFormatIan Romanick2009-04-242-16/+99
| | | | | | | | | | | This interface gives the driver two important features. First, it can allocate the (fake) front-buffer only when needed. Second, it can tell the buffer allocator the format of buffers being allocated. This enables support for back-buffer and depth-buffer with different bits per pixel. Signed-off-by: Ian Romanick <[email protected]> Reviewed-by: Kristian Høgsberg <[email protected]>
* DRI2: Implement interface for drivers to access DRI2GetBuffersWithFormatIan Romanick2009-04-241-19/+85
| | | | | Signed-off-by: Ian Romanick <[email protected]> Reviewed-by: Kristian Høgsberg <[email protected]>
* DRI2: Implement protocol for DRI2GetBuffersWithFormatIan Romanick2009-04-242-0/+80
| | | | | Signed-off-by: Ian Romanick <[email protected]> Reviewed-by: Kristian Høgsberg <[email protected]>
* mesa: fix up error/warning/debug output newlinesBrian Paul2009-04-242-10/+27
| | | | | | | | | | As of commit 23ad86cfb91c294ce85a3116d4b825aaa3988a6e all messages go through output_if_debug(). Add new parameter to output_if_debug() to indicate whether to emit a newline. _mesa_warning() and _mesa_error() calls should not end their strings with \n. _mesa_debug() calls should end their text with \n.
* i965: use drm_intel_gem_bo_map/unmap_gtt() when possible, otherwise ↵Brian Paul2009-04-241-5/+9
| | | | | | dri_bo_subdata() This wraps up the unfinished business from commit a9a363f8298e9d534e60e3d2869f8677138a1e7e
* pipebuffer: don't fail when validating mapped buffersKeith Whitwell2009-04-241-4/+5
| | | | | | This can be almost impossible to avoid - hopefully we won't encounter a situation where this is a true requirement. Would probably require drivers to flush between hardware and software vertex processing.
* util: Add more entry points for dumping to bmpJakob Bornecrantz2009-04-242-18/+43
|
* i965: fix point size issueRoland Scheidegger2009-04-241-1/+1
| | | | | need to clamp point size to user set min/max values, even for constant point size. Fixes glean pointAtten test.
* mesa: more informative error messagesBrian Paul2009-04-231-6/+10
|
* i965: revert part of commit 4f4907d69f9020ce17aef21b6431d2dd65e01982Brian Paul2009-04-231-2/+2
| | | | | | | | | | | The drm_intel_gem_bo_map_gtt() call that replaced dri_bo_map() is producing errors like: intel_bufmgr_gem.c:689: Error preparing buffer map 39 (vp_const_buffer): Invalid argument . and returning NULL, causing a segfault in the memcpy(). Just reverting until we can get to the root issue...
* i915: fix fix for anisotropic filteringRoland Scheidegger2009-04-231-2/+7
| | | | forgot to commit the changes to actually support 4x aniso filtering...
* i965: Support drawing to FBO cube faces other than positive X.Eric Anholt2009-04-231-7/+11
| | | | Also fixes drawing to 3D texture depth levels.
* intel: Take advantage of GL_READ_ONLY_ARB to map to GEM bo_map write flag.Eric Anholt2009-04-232-5/+4
| | | | | This is a CPU win in general, but in particular reduces the pain of Mesa's calculation of min/max indices in DrawElements (wtf?).
* gallium: Handle non-NULL data pointer in EXA ModifyPixmapHeader hook.Michel Dänzer2009-04-231-0/+14
| | | | | | Need to use the data pointed to for pixmap contents in that case. Fixes RENDER based text rendering.
* gallium: Make the intel xorg winsys start up with any Intel chipset.Michel Dänzer2009-04-231-6/+3
| | | | | For unsupported devices the screen/context creation should fail cleanly later on.
* gallium/intel/gem: Use softpipe rather than i915simple if INTEL_SOFTPIPE is set.Michel Dänzer2009-04-235-8/+41
|
* gallium: Always include xorg-server.h before other X server headers.Michel Dänzer2009-04-232-0/+2
| | | | | Various breakage otherwise, e.g. _XSERVER64 not being defined on 64 bit leading to inconsistent definitions of X server internal structs.
* gallium: Fix up xorg state tracker build.Michel Dänzer2009-04-232-3/+0
|
* mesa: minor state-update changes in histogram codeBrian Paul2009-04-221-5/+2
| | | | | Call FLUSH_VERTICES() in _mesa_Histogram(). No need to signal _NEW_PIXEL in ResetHistogram(), ResetMinmax().
* mesa: fix comment typoBrian Paul2009-04-221-1/+1
|
* gallium: license, copyrightBrian Paul2009-04-222-0/+62
|
* st: comments, license, copyrightBrian Paul2009-04-221-0/+32
|
* mesa: fix _mesa_dump_textures(), add null ptr checkBrian Paul2009-04-221-2/+3
| | | | Calling _mesa_dump_textures() deleted the textures... oops!!!
* mesa: Fix buffer overflow when parsing generic vertex attributes.Brian Paul2009-04-221-3/+9
|
* intel: fix max anisotropy supportedRoland Scheidegger2009-04-225-3/+7
| | | | | | i915 actually supports up to 4 (according to header file - not tested), i965 up to 16 (code already handled this but slightly broken), so don't use 2 for all chips, even though angular dependency is very high.
* st: also check _NEW_PROGRAM flag for vertex shader constant buffersBrian Paul2009-04-221-1/+1
| | | | | | This is a follow-on to commit c1a3b852807fb160f0cd246c1364b7336b4b947e. Note that (at this time) wherever _NEW_PROGRAM_CONSTANTS is set we're still setting _NEW_PROGRAM so this won't really make any difference (for now).
* gallium: Reinstate unconditional flushes.Thomas Hellstrom2009-04-222-0/+4
| | | | | | Lost in commit e50dd26ca6d0eb0d0f97c2780020ea16e3d4a687. Signed-off-by: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
* mesa: protect driver.flush() with FLUSH_CURRENTKeith Whitwell2009-04-222-8/+8
| | | | | | Need to do this to ensure vbo code unmaps its buffers before calling the driver, which may be sitting on top of a memory manager which objects to firing commands from a mapped buffer.
* st: play it safe for now and check _NEW_PROGRAM for shader const buffer atomBrian Paul2009-04-211-1/+1
| | | | | When a new program is bound but no constants are updated we still need to update the Gallium const buffer.
* swrast: simplify state update logic for fragment shader const buffersBrian Paul2009-04-211-25/+2
|
* st: use the static atoms[] array directlyBrian Paul2009-04-212-20/+8
| | | | We can simplify this now that we no longer have any dynamic atoms.
* st: do away with dynamic state atom for const buffersBrian Paul2009-04-212-29/+4
| | | | Just use the new _NEW_PROGRAM_CONSTANTS flag instead.
* mesa: new _NEW_PROGRAM_CONSTANTS flagBrian Paul2009-04-215-10/+43
| | | | | | | | | | | | | | | This state flag will be used to indicate that vertex/fragment program constants have changed. _NEW_PROGRAM will be used to indicate changes to the vertex/fragment shader itself, or misc related state. _NEW_PROGRAM_CONSTANTS is also set whenever a program parameter that's tracking GL state has changed. For example, if the projection matrix is in the parameter list, calling glFrustum() will cause _NEW_PROGRAM_CONSTANTS to be set. This will let to remove the need for dynamic state atoms in some drivers. For now, we still set _NEW_PROGRAM in all the places we used to. We'll no longer set _NEW_PROGRAM in glUniform() after drivers/etc have been updated.
* mesa: print internal.current[i] attribBrian Paul2009-04-211-2/+7
|
* mesa: print parameter list dirty state flag maskBrian Paul2009-04-211-0/+1
|
* i965: const correctnessBrian Paul2009-04-211-49/+49
|
* r300: r300 hw doesn't support any input modifiers in tex instsMaciej Cencora2009-04-211-2/+1
|
* r300-gallium: Fix CS size mismatchMathias Gottschlag2009-04-211-1/+5
| | | | | This fixes some warnings which appear because the driver assumes a wrong cs size (13 vs 16 register writes in some cases).
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-05 03:26:15 +0000