don't worry, we will get HD 5870 3D acceleration in full speed five years down the road. And to make things even better, you will be able to actually afford to buy an HD 5870 by then! It will cost only a handful of dollars!
Announcement
Collapse
No announcement yet.
The ATI Radeon R600/700 Gallium3D Driver
Collapse
X
-
Originally posted by elanthis View PostI'd be happy just to have OpenGL 2.1 support on r700 right now. That at least would bring things up to par with what most commercial OpenGL apps require as a minimum version these days.
Comment
-
I have zero problems with high res textures and resolution. I like it.
But what I hate is the insane shader post processing crap! For those of you who go like "Huh?", take a look at Need For Speed: Shift. Me and a friend of mine call if NFS: Shit. No wait... NFS: Underground. When you accelerate you get such an insane motion blur. There are purple flares everywhere around 'tracks' and hit the gas and the entire screen turns into giant purple poo. It's like: "hey we didn't get gameplay already but let's now destroy the entire vision to mask it". Ulgh...
Seriously... death to those games. Die in a fire. Those games need to me made ilegal. Gaming got too commercial and as a natural effect all games now need to apeal to john doe no brain who wants to be a super hero by playing semi-interactive b-movie action scenes.
What do I love about graphics? Everyday believability, like the outdoor 'scenes' of Half-Life 2. Death to the rest...
Comment
-
What does this mean: "r600g: add support for all R6XX/R7XX asic" ? Does it mean my r600 card can worth with Galliium now?
Comment
-
from the mesa/mesa git repo ( http://cgit.freedesktop.org/mesa/mesa/log/ ) I've found:
r600g: drop compiler stuff and switch over dumb tgsi assembler
Writing a compiler is time consuming and error prone in
order to allow r600g to further progress in the meantime
i wrote a simple tgsi assembler, it does stupid thing but
i would rather keep the code simple than having people
trying to optimize code it does.
Could someone comment onthat and explain what it means, please?
Comment
-
Jerome was working on a new shader compiler for 600g rather than re-using shader compiler code from the "classic" r600 mesa driver. That was something which needed to be done at some point (the shader compiler in 600c is really more of an assembler) but it sounds like Jerome didn't want to hold up getting the rest of the 600g driver going so he put in a simple shader compiler for now. It's what we ended up doing for the initial 600c driver so I certainly understand his rationale.
If your next question is "why didn't he use the shader compiler from 600c ?" part of the answer is that the input format is different between "classic" and Gallium3d drivers - one uses Mesa IR while the other uses TGSI. For 3xx-5xx the same compiler could be used because the Gallium3d wrapper code converted TGSI back to mesa IR allowing the use of the existing compiler.Test signature
Comment
-
Thanks for your quick answer
So, that part "...he put in a simple shader compiler for now." means, he's actually still working on that new shader compiler and that current solution (the TGSI assembler) is like a "quick and dirty" (not being really dirty) solution being less efficient/less featured/less complete?
Please correct me if I'm wrong.
Comment
-
Originally posted by mcgreg View PostThanks for your quick answer
So, that part "...he put in a simple shader compiler for now." means, he's actually still working on that new shader compiler and that current solution (the TGSI assembler) is like a "quick and dirty" (not being really dirty) solution being less efficient/less featured/less complete?
Please correct me if I'm wrong.
Comment
Comment