- Jul 13, 2008
-
-
Julien Cristau authored
-
Julien Cristau authored
01_fix-installdir.patch dropped, applied upstream 04_osmesa_version.diff needed fixing
-
git://anongit.freedesktop.org/git/mesa/mesaJulien Cristau authored
Conflicts: progs/tests/antialias.c progs/tools/trace/Makefile
-
Dave Airlie authored
Fixes bug 15477
-
- Jul 12, 2008
-
-
Nicolai Hähnle authored
Share almost all code with r500_fragprog now. This also fixes Piglit's texrect-many test, which means that the compiz bicubic plugin should work with hardware acceleration now.
-
Dan Nicholson authored
This just makes the use of mklib more consistent throughout Mesa where we always want to pass the linker and LDFLAGS when we might be making a shared library.
-
Dan Nicholson authored
Respect the user's choice of shell when running mklib rather than always using /bin/sh.
-
Dan Nicholson authored
Running minstall directly means that /bin/sh is always used as hte interpreter. If the user needs or wants to use a different shell fo minstall, they can use the SHELL make variable.
-
Dan Nicholson authored
Most make implementations will use /bin/sh as the interpreter for commands and only use a different shell when the $(SHELL) make variable is set. This makes the setting explicit and allows $(SHELL) to be used in the commands themselves.
-
Dan Nicholson authored
Establish the shell that make will use from configure. This is exactly how autoconf/automake operate, with the environment variable CONFIG_SHELL respected to override the autoconf checks. In the usual case where the user just executes `./configure', autoconf will pick a shell from the current shell, sh, bash, ksh or sh5 that meets its base criteria. The special Solaris case of looking for a POSIX shell has been changed to just set the SHELL variable since autoconf substitutes this already. The EXTRA_CONFIG_LINES substitution is dropped as it should no longer be needed.
-
Nicolai Hähnle authored
-
Nicolai Hähnle authored
-
Nicolai Hähnle authored
When an input is marked in gl_program.InputsRead but is not actually read in the final program (due to dead-code elimination or whatever), the order of input registers must still match gl_program.InputsRead. This is done even more explicitly now.
-
Nicolai Hähnle authored
This fixes the last r500 bug related to glean/fragProg1.
-
Nicolai Hähnle authored
Use an abstracted instruction scheduling and register allocation algorithm that we will be able to share with r300_fragprog. Unlike the original emit code, this code tries to pair instructions that only use the RGB part of the ALU with instructions that only use the alpha part. However, the pairing algorithm still has some shortcomings; for example, it doesn't generate optimal code for the emulation of LIT.
-
Nicolai Hähnle authored
In addition, this pass fixes non-native swizzles.
-
Nicolai Hähnle authored
-
- Jul 11, 2008
-
-
Alex Deucher authored
based on info from hw team
-
Dan Nicholson authored
-
Dan Nicholson authored
Try to tell the user that the --x-* options are only used when the X libraries can't be found by pkg-config.
-
Dan Nicholson authored
The documentation in autoconf.html is much more explicit about how the different configure options control the build. This adds a notice at the end of the `./configure --help' output to tell the user about it.
-
- Jul 10, 2008
-
-
Dave Airlie authored
pointed out and debugged by stringfellow on #dri-devel
-
- Jul 09, 2008
-
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Haihao Xiang authored
enabled for 1D texture. fix #12176
-
- Jul 08, 2008
-
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
The old implementation could overwrite the caller's param buffer.
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
-
Haihao Xiang authored
-
- Jul 07, 2008
-
-
George Sapountzis authored
this disables accelerated DRI and fallbacks to client-side software rendering. compile-tested only.
-
- Jul 06, 2008
-
-
Dan Nicholson authored
Explicitly allow the argument to --with-dri-drivers to contain comma-separated or space-separated drivers. A space-separated driver list worked by chance before.
-