summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri
AgeCommit message (Collapse)Author
2008-05-05Dump buffer tiled status from intelPrintSAREAKeith Packard
2008-05-05GEM: Allocate the right number of relocs, avoiding heap smashing.Eric Anholt
2008-05-05GEM: Include target buffer handle in relocation debug.Eric Anholt
2008-05-05GEM: Set validate index to keep the same buffer from being duped on the list.Eric Anholt
2008-05-05Print GEM handles instead of BO pointers in debugging.Eric Anholt
small integers are much prettier, and let me correlate to DRM debug output.
2008-05-05Initialize bufmgr_gem->validate_array[i].offset.Eric Anholt
This is just cosmetic, to produce less scary values when the ioctl fails and doesn't return values there.
2008-05-05Make intel_{batch,exec}_ioctl return an error code so we can recover better.Eric Anholt
2008-05-05Add intel_bufmgr_gem.c to i915Keith Packard
2008-05-05Temporarily disable intel pixel ops on i915 for GEMKeith Packard
Instead of attempting to fix these for GEM, just disable until GEM is working.
2008-05-02Don't forget to set handle of shared buffers.Eric Anholt
(And fix a nearby whitespace nit)
2008-05-02Fix GEM execbuf ioctl argument.Eric Anholt
2008-05-02Fix to use GEM execbuf instead of TTM.Eric Anholt
2008-05-02Minor fixups to get GEM to the point of execbuf ioctl.Eric Anholt
2008-05-02[intel] Fix build for GEM. TTM is now disabled, and fencing is gone.Eric Anholt
Fencing was used in two places: ensuring that we didn't get too many frames ahead of ourselves, and glFinish. glFinish will be satisfied by waiting on buffers like we would do for CPU access on them. The "don't get too far ahead" is now the responsibility of the execution manager (kernel).
2008-05-02Add intel_bufmgr_gem for new graphics execution manager.Eric Anholt
2008-05-02[intel] Warnings fixes.Eric Anholt
2008-05-02[intel] Merge intel_ioctl.h. Not sure how this slipped by in the .c merge.Eric Anholt
2008-04-30intel: test cpp to ensure mipmap tree matches texture image.Xiang, Haihao
2008-04-29r200: fix state submission issue causing bogus textures (bug 15730)Ove Kaaven
2008-04-29Change default of driconf "allow_large_textures" to announce hardware limits.Michel Dänzer
The previous default these days served mostly to cause artifical problems with GLX compositing managers like compiz (see e.g. http://bugs.freedesktop.org/show_bug.cgi?id=10501).
2008-04-28build fix for xorg driverAlan Hourihane
2008-04-25[i965] short immediate values must be replicated to both halves of the dwordKeith Packard
The 32-bit immediate value in the i965 instruction word must contain two copies of any 16-bit constants. brw_imm_uw and brw_imm_w just needed to copy the value into both halves of the immediate value instruction field.
2008-04-25silence warningAlan Hourihane
2008-04-24enable GL_EXT_multi_draw_arrays (see bug 15670)Pierre Beyssac
2008-04-22i965: fix DEPTH_TEXTURE_MODE (bug #14220)Xiang, Haihao
2008-04-22 [i965] This is to fix random crash in some maps of Ut2004 demo.Zou Nan hai
e.g. bridge of fate. If vs output is big, driver may fall back to use 8 urb entries for vs, unfortunally, for some unknown reason, if vs is working at 4x2 mode, 8 entries is not enough, may lead to gpu hang.
2008-04-22i965: save the offset of target buffer after last execution, not relocatee ↵Xiang, Haihao
buffer.
2008-04-21intel: fix an assertion failure. fix bug #15575Xiang, Haihao
2008-04-21i965: clear the PRESUMED_OFFSET flag from bo_req.hint, not bo_req.flags. fix ↵Xiang, Haihao
#15574
2008-04-18i965: fixup depth buffer checkDave Airlie
2008-04-18i965: fix vb aperture space checkDave Airlie
2008-04-18965: fix vb upload size checkDave Airlie
2008-04-18i965: fix gs_prog aperture checkDave Airlie
2008-04-18i915: check for depth region before accounting its buffer sizeDave Airlie
fd.o bz #15573
2008-04-18i965: initial attempt at fixing the aperture overflowDave Airlie
Makes state emission into a 2 phase, prepare sets things up and accounts the size of all referenced buffer objects. The emit stage then actually does the batchbuffer touching for emitting the objects. There is an assert in dri_emit_reloc if a reloc occurs for a buffer that hasn't been accounted yet.
2008-04-17Revert "[i965] renable regative rhw test"Xiang, Haihao
This reverts commit 3158e981f5f37768e9b04765704b9eaece8b899b. rhw issue has gone away on IGD.
2008-04-17r200: accept PROGRAM_CONSTANT inputs due to mesa changesAndrew Randrianasulu
2008-04-16bufmgr_fake: disable debugging againDave Airlie
2008-04-16intel: fix _mesa_error ctx I introduced at lsat minuteDave Airlie
2008-04-16intel/fake_bufmgr: Attempt to restrict references to objects in a ↵Dave Airlie
batchbuffer > aperture size. So with compiz on Intel hw with fake bufmgr, opening 4 firefox windows at 1680x1050 and hitting alt-tab, could cause the batchbuffer to try and reference more than the 32MB of RAM allocated. Fix 1: Fix 1 is to pre-verify the list of buffers against the current batchbuffer and if it can't possibly fit in the aperture to flush the batchbuffer to the hardware and try again. If the buffers still can't fit well then you are hosed as I'm not sure there is a nice way to tell anyone. Fix 2: Next problem was that even with a simple check for total < aperture, we ran into fragmentation issues, this meant that half way down a set of buffers, we would fail as no blocks were available. Fix this by nuking the memory manager from orbit and letting it start again and relayout the blocks in a manner that fits. Fix 3: Finally the initial problem we were seeing was a memcpy to a NULL backing store. We seem to end up with a texture at some point that never gets mapped but ends up with data in it. compiz al-tab icons have this property. So I created a card dirty bit that memcpy's any buffer that is !static and is written to back to memory. This probably is wrong but it makes compiz work for now. Caveats: 965 support is still fail.
2008-04-14only use __x86_64__, not __amd64__ (bug 15503)Brian Paul
2008-04-12r200: fix XPD vertex program instruction when using temps as inputsRoland Scheidegger
due to the two read ports limit into temp memory may need the MAD_2 instruction for the second instruction of the decomposed XPD. While here, also try to avoid MAD_2 for MAD if all 3 inputs are temps but the temps aren't actually distinct.
2008-04-07r300: Fix r300VAPInputRoute{0,1} for big endian platforms.Michel Dänzer
2008-04-02Initialize GLX_EXT_texture_from_pixmap attributes correctly.Kristian Høgsberg
2008-03-31DRI interface changes and DRI2 direct rendering support.Kristian Høgsberg
Add DRI2 direct rendering support to libGL and add DRI2 client side protocol code. Extend the GLX 1.3 create drawable functions in glx_pbuffer.c to call into the DRI driver when possible. Introduce __DRIconfig, opaque struct that represents a DRI driver configuration. Get's rid of the open coded __GLcontextModes in the DRI driver interface and the context modes create and destroy functions that the loader was requires to provide. glcore.h is no longer part of the DRI driver interface. The DRI config is GL binding agnostic, that is, not specific to GLX, EGL or other bindings. The core API is now also an extension, and the driver exports a list of extensions as the symbol __driDriverExtensions, which the loader must dlsym() for. The list of extension will always include the DRI core extension, which allows creating and manipulating DRI screens, drawables and contexts. The DRI legacy extension, when available, provides alternative entry points for creating the DRI objects that work with the XF86DRI infrastructure. Change DRI2 client code to not use drm drawables or contexts. We never used drm_drawable_t's and the only use for drm_context_t was as a unique identifier when taking the lock. We now just allocate a unique lock ID out of the DRILock sarea block. Once we get rid of the lock entirely, we can drop this hack. Change the interface between dri_util.c and the drivers, so that the drivers now export the DriverAPI struct as driDriverAPI instead of the InitScreen entry point. This lets us avoid dlsym()'ing for the DRI2 init screen function to see if DRI2 is supported by the driver.
2008-03-31i915: texture object's lod bias. fix bug #15192Xiang, Haihao
2008-03-30r300: Copy-and-paste error from the vertex program branch.Markus Amsler
2008-03-30r300: Take PROGRAM_CONSTANT into account.Markus Amsler
This bug was introduced by commit 978145a075255ae153ee05c2a037400e61558079.
2008-03-29Merge branch 'r300-vertprog-branch' of ssh://people.freedesktop.org/~z3ro/mesaOliver McFadden
2008-03-28i965: depth offset on glPolygonMode(GL_LINE/GL_POINT)Xiang, Haihao