Originally posted by pingufunkybeat
View Post
Announcement
Collapse
No announcement yet.
Mesa Beginning To Need Application Workarounds
Collapse
X
-
-
Originally posted by siride View PostI guess you miss the point. The point is that we can wait for perfection before we go on to fix these incompatibilities.
Closed drivers have more workarounds than the entire Mesa stack + all of the linux kernel tree. OpenGL compliance (and other things I mentioned) are not only more important IMHO, but also more realistic than duplicating all those workarounds.
If a couple of high-profile workarounds make it into the tree and don't cause an unmaintainable mess, I won't complain -- it's the developers' choice after all. I just don't think that Unigine demos are all that important compared to power saving, for example.
Comment
-
Originally posted by pingufunkybeat View PostIt's not about perfection, it's about priorities.
Closed drivers have more workarounds than the entire Mesa stack + all of the linux kernel tree. OpenGL compliance (and other things I mentioned) are not only more important IMHO, but also more realistic than duplicating all those workarounds.
If a couple of high-profile workarounds make it into the tree and don't cause an unmaintainable mess, I won't complain -- it's the developers' choice after all. I just don't think that Unigine demos are all that important compared to power saving, for example.
Comment
-
Originally posted by curaga View PostUnigine folks already said these are fixed? Carry on on the general case though
In other news, Super Meat Boy and Shank still doesn't run on Mesa out-of-the-box, because it is "asshole correct".
Comment
-
Originally posted by lopho View Posti think workarounds should be handled off-tree in a seperate package, maybe through api.
that way its easy for users to choose if they want only specification compliance or compatibilty, maybe even easily switchable by configs files.
Comment
Comment