Originally posted by monkeynut
View Post
Announcement
Collapse
No announcement yet.
Progress On The ATI R600g Gallium3D Driver
Collapse
X
-
Originally posted by V!NCENT View PostI have a nasty feeling you had to work around added DRM, am I correct?Test signature
Comment
-
-
Originally posted by bridgman View PostActually no, we got lucky this time. Most of the effort went into finding a few new bits that had to be programmed in order for anything to work. The problem is that GPUs don't tell you *why* they aren't working, they just kinda sit there and laugh at you
Comment
-
Originally posted by bridgman View PostActually no, we got lucky this time. Most of the effort went into finding a few new bits that had to be programmed in order for anything to work. The problem is that GPUs don't tell you *why* they aren't working, they just kinda sit there and laugh at you
No.
Comment
-
Originally posted by nikai View PostI just noticed that with current mesa git, Oolite appears to run decently with r600 Gallium. Awesome!
Some days ago it was running for the first time, but with shaders enabled a number of textures were missing.
Comment
-
Originally posted by fa5hion View PostThanks for sharing this information. Mesa git log shows a number of r600g commits made in last few weeks. What is the overall state of functionality/performance of the r600g compared to the r600c? Wine experiences? Anyone?
Comment
-
Well, 300g in mesa git from 3 days ago is quite a lot slower and buggier than 300g from 2 or 3 weeks ago. There are problems with transparency in KWin for instance, that were not before.
I imagined that this has more to do with the new GLSL2 compiler than actual 300g commits, but sibnce I know very little about the whole stack, I'm probably wrong.
Comment
Comment