summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* gallium: Move dri drivers to targetsJakob Bornecrantz2010-03-2414-42/+12
| | | | | | | | | | | | | | Attached output from git commit: rename src/gallium/{winsys/drm/Makefile.template => targets/Makefile.dri} (100%) rename src/gallium/{winsys/drm/intel/dri => targets/dri-i915}/Makefile (75%) rename src/gallium/{winsys/drm/intel/dri => targets/dri-i915}/SConscript (100%) rename src/gallium/{winsys/drm/i965/dri => targets/dri-i965}/Makefile (76%) rename src/gallium/{winsys/drm/i965/dri => targets/dri-i965}/SConscript (100%) rename src/gallium/{winsys/drm/nouveau/dri => targets/dri-nouveau}/Makefile (86%) rename src/gallium/{winsys/drm/radeon/dri => targets/dri-radeong}/Makefile (85%) rename src/gallium/{winsys/drm/radeon/dri => targets/dri-radeong}/SConscript (100%) rename src/gallium/{winsys/drm/vmware/dri => targets/dri-vmwgfx}/Makefile (85%) rename src/gallium/{winsys/drm/vmware/dri => targets/dri-vmwgfx}/SConscript (100%)
* gallium: Remove GALLIUM_WINSYS_DRM_DIRSJakob Bornecrantz2010-03-241-12/+0
|
* st/mesa: fix typo in prev commitBrian Paul2010-03-241-1/+1
|
* st/mesa: fix sampler_view destruction bug when texture is sharedBrian Paul2010-03-241-2/+10
| | | | | | | | | | | Since texture's can be shared by many contexts, the texture's sampler view's context pointer might be invalid by time we delete the texture. Prevent crashes/etc by setting the sampler view's context to be the calling context before deleting it. This should be safe as long as all contexts which share the texture are using the same gallium driver. That's a reasonable assumption since pipe_texture objects aren't compatible between different drivers anyway.
* st/mesa: code clean-ups, formatting fixes, comments, etcBrian Paul2010-03-241-16/+31
|
* st/mesa: rename st_clear() to st_Clear()Brian Paul2010-03-241-2/+2
| | | | To be consistent with other Mesa driver functions.
* st/mesa: return GL_TRUE/GL_FALSE if return type is GLbooleanBrian Paul2010-03-241-15/+13
| | | | Just to be consistent.
* swrast: improve depth texture mipmap selectionBrian Paul2010-03-231-11/+30
| | | | | | | We still don't do proper min/mag filtering but this is better than just sampling the base mipmap level all the time. Fixes piglit depth-level-clamp test. Fixes fd.o bug 27256.
* st/glx: add support for multiple displaysBrian Paul2010-03-231-4/+26
| | | | | | | | This is a quick & dirty solution, but it works. See comments in the code for other ideas. Fixes regressions/breakage seen in progs/xdemos/glxheads, etc. from commit 6632915e957149c153a3f793c400a532b4995b18.
* glslcompiler: added option to do linking of vert/frag shadersBrian Paul2010-03-231-12/+37
|
* dri: fix dri_test.c for non-TLS buildLuca Barbieri2010-03-231-2/+7
| | | | | _glapi_Context and _glapi_Dispatch have different constness between TLS and non-TLS builds.
* dri: add _glthread_GetID to dri_test.c dummy glapiLuca Barbieri2010-03-231-0/+6
|
* dri: make unresolved symbol test link work even without a libGL.soLuca Barbieri2010-03-233-2/+70
| | | | | | | | | | | | | | | | Currently the test link uses -lGL to define the glapi symbols. This makes it impossible to build DRI drivers on systems without Mesa installed and without building the libGL from the Mesa tree first. Some automated build systems trigger this problem. This commit removes -lGL and instead adds a dummy implementation of glapi to dri_test.c This, along with Kristian's commit, should fix all known regressions due to the addition of unresolved symbol checking.
* Change libX11 variables to not conflict with AC_PATH_XTRADan Nicholson2010-03-232-2/+2
| | | | | | | | The variable X_LIBS from AC_PATH_XTRA contains only the -L searchdir parameter and not the -lX11 to link to Xlib. Use X11 prefixed build vars for linking with Xlib to avoid the conflict. Signed-off-by: Dan Nicholson <[email protected]>
* dri: Add $(DRI_LIB_DEPS) when linking the test binaryKristian Høgsberg2010-03-232-2/+2
| | | | This will make sure we pick up libdrm_$(chipset).so from the right place.
* i965: Stop abusing ctx->NewState flags for storing driver internal changes.Eric Anholt2010-03-231-3/+3
| | | | | | | | | | | We're still abusing the flags by putting them where our driver stores ctx->NewState changes. Making them into more restricted state change flags would be a project for later. Fixes a failure where calling intel_draw_buffer() too often would trip up Mesa assertions about when Mesa state could get changed, when it hadn't. Bug #27034.
* mesa: Also print _NEW_STENCIL in _mesa_print_state()Kristian Høgsberg2010-03-231-1/+2
|
* nvfx: add NOUVEAU_VTXIDX_IN_VRAM variable to put vertex/index buffers in VRAMLuca Barbieri2010-03-233-1/+33
| | | | | | | | | | | | On some systems, putting vertex and index buffers in VRAM instead of GART memory eliminates massive graphics corruption which is otherwise present, due to unclear causes. This patch adds an environment variable that does that, along with helpful messages. It turns it on by default on G7x, as it is what I am seeing corruption on and some other reports also seemed to pinpoint these cards.
* nvfx: delay allocation of buffers in GART/VRAM to validation timeLuca Barbieri2010-03-232-5/+3
| | | | | | | | | | | | | | | | | | | | | | | Currently we allocate buffers in GART or VRAM at creation time. However, when using swtnl, this results in reads from uncached memory, which drastically impair performance. So, for now, cause nouveau_screen.c to not pass any placement flags to buffer creation, so that the buffers are moved later. Previously libdrm itself did this, but was changed to not to do it. This may introduce an extra copy in normal usage, but this currently does not seem to introduce significant performance degradation. This will be revisited when pipebuffer is integrated. Note that for AGP systems, properly solving this may be complex since currently there is no fast way of reading from GART/VRAM. We will probably need to try mapping AGP as writethrough and, in addition, make buffer creation more aware of future buffer usage.
* st/mesa: make st_manager.c set have[Stencil|Depth]Buffer only if bits > 0Luca Barbieri2010-03-231-3/+3
| | | | Fixes a segfault when clearing a non-existent stencil buffer.
* dri: use mv -f instead of mv to ensure no prompting occursLuca Barbieri2010-03-232-2/+2
| | | | Using just mv may cause prompts on some systems/configurations.
* Merge branch '7.8'Brian Paul2010-03-232-187/+219
|\ | | | | | | | | | | | | | | | | | | Conflicts: Makefile src/gallium/state_trackers/glx/xlib/xm_api.c src/mesa/drivers/dri/intel/intel_blit.c src/mesa/drivers/dri/intel/intel_pixel_copy.c src/mesa/main/version.h
| * softpipe: comments, re-formatting, etcBrian Paul2010-03-231-14/+24
| |
| * softpipe: add special cases for all Z compare modes for 16-bit Z bufferBrian Paul2010-03-232-173/+195
| | | | | | | | | | | | | | | | We had fast paths for PIPE_FUNC_LESS and LEQUAL before. To satisfy OpenGL invariance rules, all depth compare modes should produce the same fragment Z values. Fixes progs/demos/singlebuffer.c
| * st/glx: better format selection in xmesa_choose_z_stencil_format()Brian Paul2010-03-231-17/+24
| | | | | | | | | | This is a back-port of commit ef2664da6c4db1b52ef351641e3ee949b87f9c7b from master.
| * glx: Suppress BadDrawable from DRI2CopyRegionKristian Høgsberg2010-03-221-1/+14
| | | | | | | | | | | | | | | | | | | | This can happen when an X window is destroyed behind our back. We use DRI2CopyRegion behind the scenes in many places (like flushing the fake front to the real front) so we have to ignore X errors triggered in that case. The glean test cases trigger this consistently as they don't destroy the GLX drawable nicely, they just destroy the X window.
| * mesa: set version string to 7.8-rc27.8-rc2Ian Romanick2010-03-221-1/+1
| |
| * intel: Call intel_prepare_render() before looking up regions.Kristian Høgsberg2010-03-223-6/+9
| | | | | | | | Fixes #27213.
* | nvfx: don't crash on empty fragment programLuca Barbieri2010-03-231-1/+2
| |
* | nvfx: fix coding style in nvfx_transfer.cLuca Barbieri2010-03-231-8/+8
| |
* | nvfx: stop incessantly spewing debug messages on the terminalLuca Barbieri2010-03-232-3/+8
| | | | | | | | | | | | | | | | | | | | | | Currently we are continuously spewing messages about these variables since we call debug_get_bool_option everytime we want to check their value. This is annoying, slows things down due to terminal rerendering and obscures useful messages. This patch only calls debug_get_bool_option once and caches the result in a static variable.
* | nvfx: fix/workaround nv3x hwtnl issuesLuca Barbieri2010-03-231-5/+6
| | | | | | | | | | | | | | | | | | | | | | This patch re-emits the viewport state on framebuffer or rasterizer change. This seems to be necessary on nv3x, but the reason is not fully understood. It is quite likely that this isn't really the correct fix, but seems to work, and makes nv3x much better.
* | dri: test whether the built drivers have unresolved symbolsLuca Barbieri2010-03-233-4/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a different approach to solving this problem that the patch I previously posted, and unlike that, should not cause any problems. Right now undefined symbols in DRI drivers will still allow the build to succeed. As a result, people modifying drivers they cannot test risk creating unloadable drivers with no easy way of automatically avoiding it. For instance, the modifications to nv50 for context transfers caused such an issue recently. Unfortunately, just adding -Wl,--no-undefined doesn't work, because the DRI drivers depend on glapi symbols, but do not depend on libGL.so.1 Adding -lGL is not the correct solution since DRI drivers are not loaded just by libGL, but also by X and possibly by other clients. So, this patch simply tries to build an executable linked to the DRI driver and to libGL. If the DRI driver contains any undefined symbols not satisfied by its dependencies or by libGL, this will fail. This solution does not alter the built drivers, and does not significantly slow down the build process. All classic DRI drivers as well as all the Gallium drivers with configure options compiled successfully with this change. Thanks to Xavier Chantry <[email protected]> and Michel Daenzer <[email protected]> for helping with this. Signed-off-by: Luca Barbieri <[email protected]> Acked-by: Brian Paul <[email protected]>
* | radeong: fix build issue with libdrm < 2.4.19Marek Olšák2010-03-232-0/+6
| |
* | r300g: fix glean occlusion query testDave Airlie2010-03-231-0/+2
| |
* | glx: Suppress BadDrawable from DRI2CopyRegionKristian Høgsberg2010-03-221-1/+14
| | | | | | | | | | | | | | | | | | | | This can happen when an X window is destroyed behind our back. We use DRI2CopyRegion behind the scenes in many places (like flushing the fake front to the real front) so we have to ignore X errors triggered in that case. The glean test cases trigger this consistently as they don't destroy the GLX drawable nicely, they just destroy the X window.
* | gallium/docs: Cleanup and clarify point ras info.Corbin Simpson2010-03-221-32/+44
| | | | | | | | ...This state's interdependent? Really? Needs moar cleanup.
* | radeong: Always initialize this variable.Corbin Simpson2010-03-221-2/+2
| | | | | | | | May or may not be responsible for slight increases in ipers FPS.
* | r300g: Cleanup a few old warnings.Corbin Simpson2010-03-221-24/+9
| | | | | | | | | | Those paths aren't important anymore, and a debugging warning won't stop a hardlock anyway.
* | GLX/OML: honor OML semantics even if target, divisor and remainder are 0Jesse Barnes2010-03-221-0/+3
| | | | | | | | | | | | | | | | | | | | | | This change passes a remainder of 1 to the server with the DRI2SwapBuffers request, causing it to honor the OML semantics for the swap rather than falling through to glXSwapBuffers behavior. The remainder actually ends up ignored since the divisor is 0, but we need to differentiate the OML and standard behavior somehow. Reported-by: Mario Kleiner <[email protected]> Signed-off-by: Jesse Barnes <[email protected]>
* | i965: Add disasm for SNB MATH opcode.Eric Anholt2010-03-221-1/+6
| |
* | i965: Enable normal clipping on SNB.Eric Anholt2010-03-221-1/+1
| | | | | | | | Rejecting all doesn't seem to be helping get the pipeline lit up.
* | i965: Force single program flow in SNB GS, to match gen4 GS.Eric Anholt2010-03-221-1/+2
| |
* | i965: Correct copy and wasted field shifts for SNB GS URB.Eric Anholt2010-03-221-2/+2
| |
* | i965: Enable VS on SNB.Eric Anholt2010-03-221-1/+2
| | | | | | | | | | | | | | It appears that the thing that was killing VS threads was the gratuitous NOP that replaced the gratuitous jump from OPCODE_END to the nearby OPCODE_END implementation. With that gone, we can move on to the rest of the pipeline.
* | i965: Remove gratuitous jump or nop from OPCODE_END to vertex emit.Eric Anholt2010-03-221-40/+3
| | | | | | | | | | | | Just emit the URB write at END time. Subroutine code that sits after OPCODE_END won't be executed since we've ended the thread at the point that the URB write is done.
* | i965: Ignore execution mask for the mov(m0, g0) of VS URB write header on SNB.Eric Anholt2010-03-221-0/+3
| | | | | | | | | | Otherwise, we may not get the FFTID set up which would break freeing of resources.
* | i965: Allow FS constants to be used as immediates instead of push/pull.Eric Anholt2010-03-223-7/+58
| | | | | | | | | | | | | | The hope is to later take advantage of the reduced constant usage to free up regs. This only covers the GLSL path at the moment, because the brw_wm_emit path doesn't get the information as to whether a float value is a constant or a uniform.
* | i965: Add INTEL_DEBUG=glsl_force to force brw_wm_glsl.c.Eric Anholt2010-03-223-0/+5
| | | | | | | | | | I keep finding the desire to force this path to debug it instead of cooking up goofy-looking testcases to do so.
* | i965: Optimize OPCODE_CMP by using BRW_SEL to choose results.Eric Anholt2010-03-221-5/+1
| | | | | | | | Tested with piglit glsl-fs-sqrt-branch, fp-cmp.vpfp.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-03 23:19:49 +0000