| Age | Commit message (Collapse) | Author |
|---|
|
This is for loading swrast_dri.so from libGL.
MakeContextCurrent() seems to unbind the context right after binding it and
DRI drivers also have a noop DriverAPI.UnbindContext ...
|
|
|
|
Someone changed the function parameters but didn't bother to update the
comments.
Also, whitespace changes, clean-ups.
|
|
|
|
|
|
This is an API breakage only.
|
|
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.
|
|
|
|
|
|
Also, build driverfuncs.c into libmesa.a since it's always needed.
|
|
|
|
|
|
This workaround is similar to the one found in r200_span.c.
It seems like some part of the read hardware doesn't realize that
VRAM has changed. By reading from an arbitrary position, this is fixed.
The piglit test bugs/r300-readcache is a regression test for this bug.
|
|
|
|
If an app does not use GL_EXT_tex_filter_aniso, this lets driconf set it instead.
|
|
This also fixes a bug with Zfunc set to GL_NEVER in glean/paths.
|
|
This fixes the glean/maskedClear test.
|
|
The glean/readPixSanity test passes now.
|
|
Thanks to Corbin for the initial cut today. Fixed some minor stuff (in
particular, make sure we still use a MIP_LINEAR filtering mode; anisotropy
without MIP_LINEAR filtering is not the truly pleasing anisotropy).
|
|
|
|
Not quite finished, maybe? Not sure.
|
|
To do: Add a slightly more accurate LIT. Will do later.
|
|
The texture layout calculations for mipmapped cubemaps used to be completely
wrong, since the GPU expects images to be grouped by miplevel instead of by
face number.
This has been fixed now, though the memory layout is still slightly incorrect
for the smaller miplevels. Unfortunately, the docs are lacking in that area.
|
|
Swap buffers is a fairly reasonable time to wait for the hardware for a
while; this keeps us from overrunning the ring.
|
|
This commit should not affect the functionality at all, just cleanup
some of the original texture filter guesswork using information from
the register documentation.
|
|
This variable was only ever written to, but nobody used its value.
|
|
|
|
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
|
