summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2009-04-23gallium: Make the intel xorg winsys start up with any Intel chipset.Michel Dänzer
For unsupported devices the screen/context creation should fail cleanly later on.
2009-04-23gallium/intel/gem: Use softpipe rather than i915simple if INTEL_SOFTPIPE is set.Michel Dänzer
2009-04-23gallium: Always include xorg-server.h before other X server headers.Michel Dänzer
Various breakage otherwise, e.g. _XSERVER64 not being defined on 64 bit leading to inconsistent definitions of X server internal structs.
2009-04-23gallium: Fix up xorg state tracker build.Michel Dänzer
2009-04-22mesa: minor state-update changes in histogram codeBrian Paul
Call FLUSH_VERTICES() in _mesa_Histogram(). No need to signal _NEW_PIXEL in ResetHistogram(), ResetMinmax().
2009-04-22mesa: fix comment typoBrian Paul
2009-04-22gallium: license, copyrightBrian Paul
2009-04-22st: comments, license, copyrightBrian Paul
2009-04-22mesa: fix _mesa_dump_textures(), add null ptr checkBrian Paul
Calling _mesa_dump_textures() deleted the textures... oops!!!
2009-04-22i965: disable debug printfBrian Paul
2009-04-22i965: enable VS constant buffersBrian Paul
In the VS constants can now be handled in two different ways: 1. If there's room in the GRF, put constants there. They're preloaded from the CURBE prior to VS execution. This is the historical approach. The problem is the GRF may not have room for all the shader's constants and temps and misc registers. Hence... 2. Use a separate constant buffer which is read from using a READ message. This allows a very large number of constants and frees up GRF regs for shader temporaries. This is the new approach. May be a little slower than 1. 1 vs. 2 is chosen according to how many constants and temps the shader needs.
2009-04-22i965: define BRW_MAX_GRFBrian Paul
2009-04-22i965: remove old code to init surface-related cache IDsBrian Paul
These types are only found in the new surface state cache now.
2009-04-22i965: comments, reformattingBrian Paul
2009-04-22mesa: Fix buffer overflow when parsing generic vertex attributes.Brian Paul
2009-04-22i965: actually use the new, second surface state cacheBrian Paul
2009-04-22i965: checkpoint commit: use two state caches instead of oneBrian Paul
The new, second cache will only be used for surface-related items. Since we can create many surfaces the original, single cache could get filled quickly. When we cleared it, we had to regenerate shaders, etc. With two caches, we can avoid doing that.
2009-04-22i965: remove unused state atom entriesBrian Paul
2009-04-22intel: fix max anisotropy supportedRoland Scheidegger
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.
2009-04-22i965: the brw_constant_buffer state atom is no longer dynamicBrian Paul
No more dynamic atoms so we can simplify the state validation code a little.
2009-04-22i965: add _NEW_PROGRAM_CONSTANTS to mesa_bits[] listBrian Paul
2009-04-22i915: check the new _NEW_PROGRAM_CONSTANT flagBrian Paul
2009-04-22i965: use _NEW_PROGRAM_CONSTANTS and always create new const buffersBrian Paul
When program constants change we create a new VS constant buffer instead of re-using the old one. This allows us to have several const buffers in flight with vertex rendering.
2009-04-22i965: updates to some debug codeBrian Paul
2009-04-22i965: use new _NEW_PROGRAM_CONSTANTS flag instead of dynamic flagsBrian Paul
2009-04-22r200/r300/r500: add _NEW_PROGRAM_CONSTANTS flagBrian Paul
Make sure we detect constant buffer changes indicated by the new flag. Should be able to remove _NEW_PROGRAM (and _NEW_MODELVIEW, _NEW_LIGHT, etc) from several places (someday.
2009-04-22st: also check _NEW_PROGRAM flag for vertex shader constant buffersBrian Paul
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).
2009-04-22Merge remote branch 'origin/master' into radeon-rewriteDave Airlie
2009-04-22gallium: Reinstate unconditional flushes.Thomas Hellstrom
Lost in commit e50dd26ca6d0eb0d0f97c2780020ea16e3d4a687. Signed-off-by: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
2009-04-22mesa: protect driver.flush() with FLUSH_CURRENTKeith Whitwell
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.
2009-04-21st: play it safe for now and check _NEW_PROGRAM for shader const buffer atomBrian Paul
When a new program is bound but no constants are updated we still need to update the Gallium const buffer.
2009-04-21swrast: simplify state update logic for fragment shader const buffersBrian Paul
2009-04-21st: use the static atoms[] array directlyBrian Paul
We can simplify this now that we no longer have any dynamic atoms.
2009-04-21st: do away with dynamic state atom for const buffersBrian Paul
Just use the new _NEW_PROGRAM_CONSTANTS flag instead.
2009-04-21mesa: new _NEW_PROGRAM_CONSTANTS flagBrian Paul
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.
2009-04-21mesa: print internal.current[i] attribBrian Paul
2009-04-21mesa: print parameter list dirty state flag maskBrian Paul
2009-04-21i965: const correctnessBrian Paul
2009-04-21R6xx/R7xx: remove unused filesRichard Li
2009-04-21R6xx/R7xx: add updated reg fileRichard Li
2009-04-21Update GALLIUM_AUXILIARY_DIRS in configure.ac to match configs/default.Michel Dänzer
2009-04-21Initial pull of code from r6xx-r7xx-support branchRichard Li
Not functional yet.
2009-04-21r300: r300 hw doesn't support any input modifiers in tex instsMaciej Cencora
2009-04-21r300-gallium: Fix CS size mismatchMathias Gottschlag
This fixes some warnings which appear because the driver assumes a wrong cs size (13 vs 16 register writes in some cases).
2009-04-21demos: check that GL version is 2.0 or higherBrian Paul
2009-04-21st: report GL_OUT_OF_MEMORY instead of assertingBrian Paul
2009-04-21trivial/tri-viewport: add keys for frustrum/ortho and z coordinateKeith Whitwell
2009-04-21trivial/tri-viewport: add more out-of-bounds background quadsKeith Whitwell
2009-04-21trivial/tri_viewport: add space==reset keyKeith Whitwell
2009-04-21trivial/tri_viewport: add width/height keysKeith Whitwell
generated by cgit v1.2.3 (git 2.39.1) at 2025-07-25 11:41:08 +0000