Back on topic, for anyone who cares, Ian's announcement means that I have to make a decision about what to do with my GLSL to TGSI translator branch.
Right now, the main branch for the translator (called glsl-130) is stable, but in terms of performance, features, and generated code quality, it doesn't have any significant advantages (or disadvantages) over the GLSL->Mesa->TGSI path. What I'm working on now is a WIP branch called glsl-130-wip-integers, which supports native integers but will only work on softpipe until I finish making it compatible with drivers without support for integer opcodes.
So the announcement that the 7.11 feature freeze will be June 24 means that the GLSL to TGSI translator (and the associated changes to Mesa and st/mesa) will probably have to wait for 7.12 in January before making it into a stable release. It doesn't bring much benefit without GLSL 1.30 enabled, and I don't feel like rushing to finish it. ;)
Sorry for the long post, but I thought I should give a status update. :)
and you still don't understand my words. i don't argue about what is the default i tell you what should be the standard.
Originally Posted by droidhacker
i'm sick of the catalyst i reinstall today because the catalyst 11.5 break my system without any clue(maybe normal updates in dist-upgrade) so i need to reinstall the system to get back a graphic desktop and not only a shell (init 3 mode).
and the only shit that makes the radeon unusable on non passive cooled cards are the power management my hd5670 single slot card makes me ill with the noise.
ok maybe i just should buy an passive cooled card. but if you have an notebook you can't and your battery life sucked away.
amd should put a little box to every card they sell with letters on the box like this "if you use linux open this box" and after opening the box there are 2 other boxes with more letters : one of the box : "if you use catalyst here is a painkiller for your headache " and the other box : "if you use the radeon driver here are some ear protectors "
We're going to have to disagree. Sure, low by default would work out good for YOU. Not for ME. The default should by dynamic, and until that works it should just be the hardware default. Nothing else makes sense. It would be nice if KDE/Gnome included some little utilities to allow you to set this while dynamic pm is a WIP, though, and it could save the last value you set. I just don't see that as being part of the driver, it's a separate utility that someone just has to write. It would be really easy.
Originally Posted by Qaridarium
Thank you. That was interesting. Feel free to write even longer posts. :)
Originally Posted by Plombo
To others: I also have one of those broken vacuum-cleaner-by-default cards. The noise is just intolerable.
As matter of fact Alex decided not to use dynpm as default, because some cards can't work properly in their lowest state if the output resolution is too high. If I recall correctly. Or at least was something similar.
Originally Posted by Qaridarium
So the conclusion was that defaulting to low is not safe since in some cases it could result in an unstable system. Btw, ask Alex for more info or just dig up his posts from last year.