Age | Commit message (Collapse) | Author |
|
The objects are swappable, so we're less concerned by excessive object
allocation now, and it's about a 20% performance improvement. If we get
concerns about the memory consumption from others, we can look into a
compromise position later.
|
|
Swap buffers is a fairly reasonable time to wait for the hardware for a
while; this keeps us from overrunning the ring.
|
|
Conflicts:
src/mesa/drivers/dri/common/dri_bufmgr.h
src/mesa/drivers/dri/intel/intel_bufmgr_ttm.c
src/mesa/drivers/dri/intel/intel_bufmgr_ttm.h
src/mesa/drivers/dri/intel/intel_ioctl.c
|
|
I'll release a libdrm 2.3.1 without TTM apis included from a special
drm branch that should allow mesa 7.1 to build against it.
I've had to turn off DRI2 stuff.
|
|
|
|
This is only part of the fix. Someone with more autoconf-fu will have
to fix the rest
|
|
|
|
Thanks to nh for the r3xx version.
|
|
Setup fg_depth_src for depth writing programs and change early Z (ztop)
semantics.
Piglit's version of glean/fragprog test passes now (unlike Glean, its
dependency on EXT_fog_coord, which we don't support, is optional).
R3xx only at the moment, but should be straightforward to adapt to R5xx
(I don't own an R5xx, and I don't want to break anything.)
|
|
The KIL instruction only works if at least one texture unit is enabled
in hardware.
Texture instructions do not support swizzles, negations etc. natively,
so we now emit an explicit swizzling etc. operation when the texture coordinate
requires it.
This fixes the Piglit fp-kil test.
|
|
Why didn't anybody tell me we were missing this one? I thought I committed it ages ago!
|
|
This should also clean up LIT later on.
|
|
SIN/COS.
|
|
I wish I had a snarky commit message, but I'll save that for after I get the
trig working with this.
|
|
|
|
because really we should be able to just fix the driver.
|
|
This fixes transparency issues on r500 by enabling
backwards compatibility with the r300 alpha compare value.
|
|
This is good for about 5% on ipers on 965, and should help any cpu-bound app.
|
|
|
|
|
|
|
|
|
|
Mapping and unmapping buffers is expensive, and having the map around isn't
harmful (other than consuming address space). So, once mapped, just leave
buffers mapped in case they get re-used.
|
|
|
|
|
|
|
|
Bring in all the r500 3D code into master should be as stable as the r300
code it is landing on top off.
Conflicts:
src/mesa/drivers/dri/r300/r300_reg.h
src/mesa/drivers/dri/r300/r300_state.c
src/mesa/drivers/dri/radeon/radeon_screen.c
|
|
This removes lots of warnings to the user, and only allows the driver
to run on > .29 drms for r500 cards.
|
|
|
|
|
|
|
|
And we're officially finished with the ARB_fragment_program
instruction set. It's worth noting that LIT is still not reliable.
SIN and COS were fixed a few commits ago. We're finished with stage 1!
Whoohoo!
|
|
Still broken; will fix tomorrow.
|
|
Specifically, fix improper swizzling.
|
|
Also remove some unused bits of the r500 fragprog struct
|
|
this fixes texenv
|
|
|
|
Not sure if this is a good or bad plan, it certainly doesn't make things worse here.
|
|
|
|
One of the ref counters wasn't being added to the temp counter.
Yet another product of late-night coding...
|
|
|
|
|
|
|
|
Now we can add arbitrary sources and swizzles. Will make many things smoother.
|
|
Still not working, but getting closer.
|
|
|
|
Add both MI_FLUSH and intel_batchbuffer_flush to intelEmitCopyBlit.
This ensures that the data are flushed *and* the gem kernel driver sees the
various memory domain transitions.
|
|
Huh, could have sworn I already did this once before...
Maybe I forgot to commit it?
|
|
Use the new DRM_IOCTL_I915_GEM_BUSY ioctl to detect
idle buffers for re-use.
|
|
|