summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* nouveau/nvfx: Add new PIPE_CAP valuesPatrice Mandin2010-07-211-0/+4
| | | | Signed-off-by: Patrice Mandin <[email protected]>
* gallivm: replace has_indirect_addressing field with indirect_files fieldBrian Paul2010-07-211-8/+17
| | | | | | | | | | Instead of one big boolean indicating indirect addressing, use a bitfield indicating which register files are accessed with indirect addressing. Most shaders that use indirect addressing only use it to access the constant buffer. So no need to use an array for temporary registers in this case.
* tgsi: added tgsi_shader_info::indirect_files fieldBrian Paul2010-07-212-0/+19
| | | | Indicates which register files are accessed with indirect addressing.
* gallivm: refactor code into get_indirect_offsets() functionBrian Paul2010-07-211-23/+34
|
* gallivm: added commentBrian Paul2010-07-211-0/+6
|
* gallivm: remove extraneous bracesBrian Paul2010-07-211-20/+18
|
* gallivm: no longer do indirect addressing in get_temp_ptr()Brian Paul2010-07-211-20/+15
|
* gallivm: implement correct indirect addressing of temp registersBrian Paul2010-07-211-11/+29
| | | | | As with indexing the const buffer, the ADDR reg may have totally different values for each element. Need to use a gather operation.
* gallivm: re-org, comments for get_temp_ptr()Brian Paul2010-07-211-3/+13
|
* draw: whitespace clean-upBrian Paul2010-07-211-33/+33
|
* gallium: remove pointless bitfield restrction in pipe_vertex_elementKeith Whitwell2010-07-211-1/+1
| | | | | This used to be a somewhat packed struct, but no longer. Remove the last remaining bitfield tag.
* gallivm: rename a var to avoid compiler warningsBrian Paul2010-07-211-2/+2
|
* gallivm: fix indirect addressing of constant bufferBrian Paul2010-07-201-25/+83
| | | | | | | | | The previous code assumed that all elements of the address register were the same. But it can vary from pixel to pixel or vertex to vertex so we must use a gather operation when dynamically indexing the constant buffer. Still need to fix this for the temporary register file...
* gallivm: added lp_build_const_int32() helperBrian Paul2010-07-201-0/+8
|
* radeon: Remove unnecessary header.Vinson Lee2010-07-201-1/+0
|
* r600g: split trans unit computationJerome Glisse2010-07-202-7/+23
| | | | Signed-off-by: Jerome Glisse <[email protected]>
* st/mesa: implement and advertise GL_ARB_draw_elements_base_vertexMarek Olšák2010-07-202-3/+5
| | | | Signed-off-by: Brian Paul <[email protected]>
* draw: correctly handle max_index=0xffffffff case in vcache codeBrian Paul2010-07-201-6/+14
| | | | | | | | | | If max_index=0xffffffff and elt_bias > 0 the test for elt_bias + max_index >= DRAW_PIPE_MAX_VERTICES was wrong. Check earlier if max_index=0xffffffff and do the "fail" case. This fixes the piglit draw-elements-base-vertex test (and probably some other things).
* st/mesa: implement depth texture modesMarek Olšák2010-07-201-11/+85
|
* mesa: call ctx->Driver.ChooseTextureFormat() only when necessary.Brian Paul2010-07-203-51/+84
| | | | | | | | | | | | | | | | | | | When defining mipmap level 'L' and level L-1 exists and the new level's internalFormat matches level L-1's internalFormat, then use the same hw format. Otherwise, do the regular ctx->Driver.ChooseTextureFormat() call. This avoids a problem where we end up choosing different hw formats for different mipmap levels depending on how the levels are defined (glTexImage vs. glCopyTexImage vs. glGenerateMipmap, etc). The root problem is the ChooseTextureFormat() implementation in some drivers uses the user's glTexImage format/type parameters in the choosing heuristic. Later mipmap levels might be generated with different calls (ex: glCopyTexImage()) so we don't always have format/type info and the driver may choose a different format. For more background info see the July 2010 mesa-dev thread "Bug in _mesa_meta_GenerateMipmap"
* graw/tests: pass -e option to test draw_elements_instanced()Brian Paul2010-07-201-1/+45
|
* softpipe: Support non-depth-stencil formats in sp_tile_cache_flush_clear().Michal Krol2010-07-201-2/+7
|
* glx: #ifdef DRI specific prototypeKristian Høgsberg2010-07-201-0/+2
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=29162
* glx/dri2: Fix dri2CopySubBuffer() again.Michel Dänzer2010-07-201-3/+4
| | | | | | | Only refresh the fake front buffer if there is one, and only destroy the region once. Fixes X11 protocol errors reported by 'mcgreg' on IRC.
* util: mempool: initialize last block's magic number in a pageMarek Olšák2010-07-201-0/+1
|
* st/egl: Fixes for recent GLX cleanup.Chia-I Wu2010-07-202-19/+45
| | | | | Mainly, the type of __GLXdisplayPrivateRec::screenConfigs has changed from "__GLXscreenConfigs *" to "__GLXscreenConfigs **".
* st/dri: Remove driFrameTrackingExtension.Chia-I Wu2010-07-201-1/+0
| | | | | The extension has been removed in 22266c391fbe17603b15a83d4ccf5fa9455ccf8d.
* glx: Move DRI CopySubBuffer extension to DRI1 codeKristian Høgsberg2010-07-196-39/+14
| | | | We do this in the X server for DRI2.
* glx: Move driver_configs to DRI screen privatesKristian Høgsberg2010-07-197-12/+22
|
* glx: Move drawHash to display privateKristian Høgsberg2010-07-195-41/+27
| | | | | The XIDs are display wide so the natural location of the hash is here. This way we don't have to lookup in each of the screen hashes.
* glx: Don't use __glXInitialize() when we might be holding __glXLock()Kristian Høgsberg2010-07-193-5/+5
|
* glx: Workaround mismatch in signedness between extensions and protocolKristian Høgsberg2010-07-191-7/+32
| | | | | The DRI2 protocol for ust, msc and sbc are unsigned but the extensions talk about int64_t. Do a little dance to make the compiler shut up.
* glx: Move __DRIdrawable pointers to DRI drawable privatesKristian Høgsberg2010-07-195-64/+88
|
* glx: Remove support for MESA_swap_frame_usageKristian Høgsberg2010-07-1912-210/+0
| | | | | The extension never worked, the implementation returns GLX_BAD_CONTEXT when enabling the frame tracking.
* glx: Move __driScreen into the dri screen privatesKristian Høgsberg2010-07-194-31/+32
|
* glx: Move DRI1 specific extensions and code to DRI1 screen privateKristian Høgsberg2010-07-197-160/+132
|
* glx: Move DRI2 extensions to DRI2 screen privateKristian Høgsberg2010-07-194-84/+73
|
* glx: Drop support for GLX_MESA_allocate_memoryKristian Høgsberg2010-07-1911-287/+1
| | | | Only r200 implemented it.
* glx: Add screen privates for dri drivers and moved some fields thereKristian Høgsberg2010-07-1910-227/+315
| | | | | | GLXscreenConfigs is badly named and a dumping ground for a lot of stuff. This patch creates private screen structs for the dri drivers and moves some of their fields over there.
* glx: Rename various DRI structs away from obnoxious __GLXfooRec conventionKristian Høgsberg2010-07-193-70/+59
| | | | Enough is enough.
* glx: Factor out common code from dri2WaitGL() and dri2WaitX()Kristian Høgsberg2010-07-191-28/+19
|
* glx: Dont use dri2WaitX() to update fake frontKristian Høgsberg2010-07-191-3/+3
| | | | This saves a superfluous flush and a create/destryo region.
* i965: Mostly fix glsl-max-varyings.Eric Anholt2010-07-191-10/+20
| | | | | | | | There was confusion on both the size of message we can send, and on what the URB destination offset means. The remaining problems appear to be due to spilling of regs in the fragment shader being broken.
* i965: Clean up message register setup in emit_vertex_write().Eric Anholt2010-07-191-7/+7
|
* i965: Reduce repeated calculation of the attribute-offset-in-VUE.Eric Anholt2010-07-194-24/+19
| | | | | | This cleans up some chipset dependency sprinkled around, and fixes a potential overflow of the attribute offset array for many vertex results.
* i965: Clarify the nr_regs calculation in brw_clip.cEric Anholt2010-07-191-3/+8
|
* i965: Don't set up VUE space for the disabled user clip distances on gen6.Eric Anholt2010-07-192-8/+14
|
* draw: fix incorrect instancing divisor in LLVM codeBrian Paul2010-07-191-3/+6
|
* mesa: remove restart.c from buildBrian Paul2010-07-192-2/+0
|
* r300g: fix possible crash in destroy_contextMarek Olšák2010-07-191-2/+2
| | | | | | | | | The problem is destroy_context is almost NEVER called. The only test for destroy_context I know is compiz. Reported by Vinson Lee. FDO bug #29150.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-22 03:39:49 +0000