Open-Source AMD/ATI Linux | Forum profile

Quote: Originally Posted by zika OOps! I've been drinking water from that pipe "under construction" for a couple of days already ... Silly me ... Is there a medicine ... ? Please keep the good work, constructing it, on. I'll wait ... Give us a wink when the construction is finished. water or Holy water ? "Is there a medicine ... ?" cure for the fglrx ...... ? Holy Water cure?

Well do you see Arma2 running on Linux? You never get something right - really. Id Tech 5 will be definitely the best multiplatform engine that will most likely get a Linux port, can you say this for your example too? wine with d3d emulation might be possible but thats like slowing down the speed from f1 racer to a truck.

Panix, pretty sure I've posted this before but AFAIK what you are seeing is the result of the open source 3D driver going through a significant rewrite in preparation for moving to KMS/GEM/TTM and the testing focus has generally moved to KMS code paths. Distros won't generally be moving to KMS and letting you see the benefits of this work until the spring releases, but predictably "the bugs are available to you...

Quote: Originally Posted by monraaf btw. Wine does appear to use the dFdx/dFdy functions, which if I'm not mistaken haven't been implemented yet. I just see that Andre Maasikas has implemented these functions... http://cgit.freedesktop.org/~andrem/...abb557b6121a8d ...and they seem to be working okay here. Great to see that Richard isn't the only person working on the R600 DRI driver.

Quote: Originally Posted by mirv Hmm, nvidia provided a working solution to changes by looking ahead, not by reacting. Early work into providing their own bits & pieces of X paid off in that regard. And "in the future, possibly" does come into real life practices - not all of them perhaps, and not if you're buying for a system that's already in place and won't be changing much, but people who...

What is the status of GLSL in r600_dri? I know that it can be experimentally enabled by uncommenting something in one source file, but it's incomplete/unstable. Will it be enabled in legacy dri driver ever? For example FoFiX works quite good, but without GLSL it looks weird in some cases (like fretboard being bright yellow in which case I can't distingish notes from fretboard). Additionally AFAIK wine in many places makes heavy use...

Quote: Originally Posted by Zajec We do some single things incorrectly (Alex has that fixed locally) but generally most of the code is fine. If Alex will get permission to release his fixes, he will just fix some bits in current code and probably will give us real names of registers. Please don't take my comment as a dig at the ported code, but I know that not all chips are supported yet and figured the fix will have to come from the IP...

I think DRI2 depends on KMS. Having DRI2 functionality is well worth the performance drop from KMS even on my slow 200M. I would use it on my main HD4850, but I haven't figured out how to do it (remember reading something about digital monitors causing problems with KMS).

enough's enough, stop the trolling, move the engine discussions to another thread.

Dave sent the pull request to Linus earlier this week. If you want to track radeon development, follow Dave's tree: http://git.kernel.org/?p=linux/kerne....git;a=summary