summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2010-05-20Make TLS EGL dri2 driver search path behavior match TLS GLX dri2 behavior.Eric Anholt
2010-05-20Fix a substitution in glesv1_cm.pcEric Anholt
2010-05-20i965: remove disabled code for cycling through MRF registers in clipping.Eric Anholt
The idea would be that you could have multiple send messages going on if nothing depended on the previous message's results and you used a different send message. The problem is that the later send requires the VUE handle returned by the first send's allocate anyway.
2010-05-20nv50: fixed other void pointer arithmetic errorsXavier Chantry
2010-05-20nv50: fix too long shader uploads by splitting themXavier Chantry
2010-05-20nv50: fill in shader limitsChristoph Bumiller
2010-05-20scons: add comments and whitespaceBrian Paul
2010-05-20scons: fix llvm detectionBrian Paul
The test for env['platform'] caused an exception since 'env' is not defined at that point. Instead, determine the target platform by scanning sys.argv[].
2010-05-20gallivm: rename a var: s/val/array_size/Brian Paul
2010-05-20gallivm: fix spelling in commentBrian Paul
2010-05-20gallivm: handle pointer types in lp_dump_llvmtype()Brian Paul
2010-05-20llvmpipe: more tweaks to dump_fs_variant_key()Brian Paul
2010-05-20gallium: fix/update tex target dumpingBrian Paul
2010-05-20llvmpipe: use util_dump_logicop()Brian Paul
2010-05-20gallium: added util_dump_logicop()Brian Paul
2010-05-20llvmpipe: put variant print/debug code into separate functionBrian Paul
2010-05-20intel: Throttle after doing copyregion/swapbuffers round tripKristian Høgsberg
Before we would throttle in the flush callback prior to round-tripping to the server to do copyregion or swapbuffer. Now, instead just note that we need to throttle and do it in intel_prepare_render(), which will be called after receiving the response from the server but before we start rendering the next frame. Even if the server also throttles us in swapbuffer, this just makes the throttling a no-op when we hit intel_prepare_render(). With that we can drop the using_dri2_swapbuffers hack and just always throttle.
2010-05-20graw-null: Remove unnecessary header.Vinson Lee
2010-05-19util: fix obvious util_blitter_copy bugs...Roland Scheidegger
2010-05-19nv50: fix typo: s/_/./Brian Paul
2010-05-19util: util_blitter_fill no longer needs to handle overlapRoland Scheidegger
2010-05-19i915g: remove unused flip parameterRoland Scheidegger
2010-05-18docs: update differences to d3d11Roland Scheidegger
2010-05-18util: fix some leftover util_surface_fill/copy callsRoland Scheidegger
2010-05-18st/mesa: fix wrong argument orderRoland Scheidegger
2010-05-18gallium: implement set_sample_mask() in all driversRoland Scheidegger
prevents segfault when state trackers try to set default mask. Other option would be to make this required only for drivers supporting multisampling, but this seems more clean. Only dummy implementations (for normal drivers) provided (no driver supports multisampling yet neither).
2010-05-17st/egl: adapt to interface changesRoland Scheidegger
2010-05-17st/dri: adapt to interface changesRoland Scheidegger
2010-05-17st/glx: adapt to interface changesRoland Scheidegger
2010-05-17st/wgl: adapt to interface changesRoland Scheidegger
2010-05-17st/vega: adapt to interface changesRoland Scheidegger
2010-05-17st/xorg: adapt to interface changesRoland Scheidegger
2010-05-17st/python: adapt to interface changesRoland Scheidegger
compile tested only. Should probably change the python surface_copy/fill functions also into resource_copy/fill_region functions and adapt the code using them.
2010-05-17svga: adapt to interface changesRoland Scheidegger
might need further cleanup. Using surfaces internally just to be able to use the existing code might cause unnecessary copies afaict.
2010-05-17r300g: adapt to interface changesRoland Scheidegger
might need further cleanup. Using surfaces internally for the u_blitter code seems nonoptimal.
2010-05-17nouveau: adapt to interface changesRoland Scheidegger
this probably needs further cleanup (just getting a surface for the resource seems quite nonoptimal and potentially cause unnecessary copies I think)
2010-05-17fo: adapt to interface changesRoland Scheidegger
2010-05-17identity: adapt to interface changesRoland Scheidegger
2010-05-17trace: adapt to interface changesRoland Scheidegger
2010-05-17i965g: adapt to interface changesRoland Scheidegger
2010-05-17i915g: adapt to interface changesRoland Scheidegger
2010-05-17softpipe: adapt to interface changesRoland Scheidegger
2010-05-17llvmpipe: adapt to interface changesRoland Scheidegger
2010-05-17cell: adapt to interface changesRoland Scheidegger
not even compile tested but fairly trivial
2010-05-17mesa/st: adapt to interface changesRoland Scheidegger
adapt to blit changes, and also handle a bit more msaa state in theory (incomplete, doesn't handle resolves in any way for now).
2010-05-17gallium/util: adapt util code to interface changesRoland Scheidegger
The util blit functions change their interface (apart from some rename) too (in particular util_blit_pixels now also takes a pipe_resource as the src blit argument instead of a surface, as it might just call resource_copy_region). Maybe the blit util code might need a bit more cleanup, it still doesn't feel very clean. In particular it seems that util_blit_pixels_tex should probably disappear, and I think it would be great if the code called by drivers for blitting (u_blitter.c, which isn't really touched by this change) could somehow be merged with the u_blit code.
2010-05-17gallium: clean up resource_copy_region functionRoland Scheidegger
Previously, surface_copy was said to allow overlapping blits, and it was "optional". However, some state trackers actually assumed it is always present, and quite some code (like in u_blit) assumed overlapping isn't allowed. Hence, resource_copy_region (and in the same spirit, resource_fill_region) is now mandatory, but overlapping blits are no longer allowed. A driver can plug in the cpu fallback util_resource_copy_region if it does not want to provide its own implementation, though this is not optimal.
2010-05-17gallium: another interface change for multisamplingRoland Scheidegger
due to popular request, use nr_samples parameter in is_format_supported() instead of new is_msaa_supported() query. This makes it easily possible to query if a format with a given sample count is also supported not only as render target, but for sampler views (note that texture sampling from multisampled resources isn't supported yet). It is not quite how dx10 format msaa queries work, but we might need to revisit format queries completely in the future anyway.
2010-05-17llvmpipe: fix front/back tri culling mix-upBrian Paul
2010-05-14draw: fix front/back error in unfilled pipeline stageKeith Whitwell
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-19 11:32:04 +0000