Wow! Congratulations and THANK YOU to everyone who made it possible!
Better powersaving management and my 4200+6650 will be shine with opensource drivers.
Printable View
Wow! Congratulations and THANK YOU to everyone who made it possible!
Better powersaving management and my 4200+6650 will be shine with opensource drivers.
Can we please document all these various environment variables somewhere? As a driver tester I hate having to dig through the source to find these, and it's not every time that Michael documents which env vars he uses when he posts articles (sometimes he just says "a flag" and doesn't mention which one), and of course they aren't in any of the documentation.
A better way would be to ship a /etc/mesa-debug.conf config file in /etc with a simple var=value format, but only ship and read from that file if mesa is compiled in debug mode (i.e. with debug symbols etc). Might need an option like --enable-debug-conf in configure. Then, ship a default mesa-debug.conf that briefly documents all possible settings but leave them commented out, so the user can easily uncomment and change them as desired.
This method would also remove the need for the user to hack environment variables into the pipeline before starting X, because it seems that you might get strange behavior if some of your mesa-using programs are running with the flags, and some without. Especially e.g. tiling...
It's pretty easy to find these: grep debug_get_bool_option *
Anyway, going to all that trouble for something that's a, likely to disappear once these features are finished and b, only of interest to a very small number of people seems like a waste of time.
Setting up the debug configuration infrastructure would be a one-time investment. Anyone who wants to write a debug option into their code afterwards would still be calling ONE function; it's just that the name of the function would be different from "debug_get_bool_option". Or maybe, heck, we could change the implementation of that function to DO exactly what I've proposed.Quote:
Originally Posted by whizse
Then of course they'd have to write something like this:
#Enable GLSL 1.30 support on Radeon 2xxx or later
#R600_GLSL130=1
in the mesa-debug.conf.example file, but that would take about 3 seconds of a developer's valuable time :o Can't have that.
There's already drirc for that.
bridgman or anyone at AMD give this kid some money (lots of them preferably)
;);)
It's working, w00t w00t!
Thanks Marek and other devs!
why use environment variable and not enable those features by default?
it is patent issue again?
A dev commented here earlier:Quote:
Originally Posted by unknown2
Even after the drivers enable GL3 by default, it will still be disabled unless you enable the patented fp texture option - that's true of all the drivers, and it should be the only patented bit required.Quote:
Originally Posted by arlied
Yes, Still 2.1 on RS780Quote:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RS780
OpenGL version string: 2.1 Mesa 8.0-devel (git-f9f8ce3)
I also wonder that, if we could enable GPU acceleration at Firefox via layers.acceleration.force-enabled flag with full OpenGL3 support and have proper graphics??