Age | Commit message (Collapse) | Author |
|
When a make target doesn't result in a file of the same name, adding it
to a .PHONY target means make won't look for such a file, speeding the
build up a bit. This allows `make doxygen' to work since otherwise make
will consider the doxygen directory as up to date.
|
|
Minor tweak so that running config.status will entirely recreate the
configure settings by replacing the configs/current symlink.
|
|
Accessing tiled surfaces without using the fence registers requires that
software deal with the address swizzling itself.
|
|
In classic mode googleearth triggered a case where vbos weren't getting accounted properly.
|
|
|
|
Two fixes to the asm configuration:
- Disable when the user is cross-compiling for x86 or x86_64 since it
requires running an executable compiled for the target host.
- If the user has specified --enable-32-bit on x86_64 or --enable-64-bit
on x86, respect that and choose the correct asm architecture.
|
|
in insert_wpos.
fixes bug 15447
|
|
The DRI modules can only be built against libdrm master (currently
version 2.3.1), so this should be enforced to save people from trying to
build against older versions.
Added a section at the top of the script to consolidate all required
versions.
|
|
|
|
|
|
|
|
|
|
The variable no_x was being set to yes when libX11 was not found through
pkg-config. This causes AC_PATH_XTRA to skip its search for the X11
libraries, which was not the intended effect. Also switched to using the
PKG_CHECK_EXISTS autoconf macro.
|
|
Added the make script version.mk to print the various version numbers
from configs/default. This is used to substitute the version in autoconf
rather than duplicating it in both places.
|
|
|
|
small integers are much prettier, and let me correlate to DRM debug output.
|
|
This is just cosmetic, to produce less scary values when the ioctl fails and
doesn't return values there.
|
|
|
|
|
|
Instead of attempting to fix these for GEM, just disable until GEM is
working.
|
|
based on patch by Dan Nicholson <dbn.lists@gmail.com>
|
|
you cannot change a tex into an output so this means we have to actually
do another instruction after this one to mov if its an output
|
|
|
|
This makes constant work which are 32-bit on r500 unlike r300.
Switch MOV to using MAD no idea if we might have negative things MAX 0,-5 is
likely to do the wrong thing..
|
|
We don't appear to update max_temp_idx yet anywhere though
|
|
We really need to update the shader state so the texrect parameters work.
This should fix compiz looking crappy on rs480 and rs690
|
|
Negative value means other errors, not aperture overflow. fix bug #15752
|
|
We really need to update the shader state so the texrect parameters work.
This should fix compiz looking crappy on rs480 and rs690
(cherry picked from commit 66a5562ce2906fbf5b96d1cee18f9a31a78c4360)
|
|
(cherry picked from commit 026ef8111a94f6449dfa5e5cc0ae91fca4e68c0c)
|
|
|
|
adapted from Markus' patch on bug 15386 with updates for non-TCL
and R500.
|
|
Thanks to dli in IRC for pointing this out.
|
|
For some reason, FGLRX doesn't actually set R500_US_INST_TEX.
Let us not make that same mistake.
|
|
r500-support
|
|
|
|
|
|
|
|
|
|
This gets non-tcl cards working again on this branch..
at least texrect and glxgears
|
|
|
|
Bringing the FPS code up-to-date.
Conflicts:
src/mesa/drivers/dri/r300/r300_emit.c
src/mesa/drivers/dri/r300/r300_ioctl.c
src/mesa/drivers/dri/r300/r300_state.c
src/mesa/drivers/dri/r300/r300_swtcl.c
src/mesa/drivers/dri/r300/r500_fragprog.c
src/mesa/drivers/dri/r300/r500_fragprog.h
|
|
(And fix a nearby whitespace nit)
|
|
|
|
|
|
|
|
r500test
Adding Alex's cleanup patches. This adds r5xx TCL! Whoo-hoo!
Conflicts:
src/mesa/drivers/dri/r300/r300_state.c
src/mesa/drivers/dri/radeon/radeon_chipset.h
src/mesa/drivers/dri/radeon/radeon_screen.c
|
|
Yet more evidence that I am incompetent with git.
|
|
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).
|
|
|
|
|