On Tue, Nov 13, 2012 at 11:53 AM, Juan Erbes
In any case, both MESA and Catalyst break in a bad way when you invoke the API in unexpected (yet correct) ways. Mesa 7, for instance, segfaulted if you sent a vec4 for a float uniform. It shouldn't segfault, it should return an error code. Mesa 8 has that fixed, but has other issues I couldn't identify yet. It's not the kinds of bugs a graphical desktop runs into - only games. Not even blender makes such heavy use of shading capabilities.
Mesa 7 works right with the nouveau driver?
No, I always had to install nVidia's proprietary driver. You could say it was a MESA thing and not an ATI thing, but then again, our users report similar problems with Catalyst, so...
I could place some links to illustrate what You say?
Um... I think we could have some old discussions in our forums[0], or perhaps our tracker[1]. I could dig it up. But it would be a chore. It's old news anyway.
Or Linus Torvalds is wrong in what his said?
Again, from what I remember of the article, Linus didn't speak about the quality of the drivers, only the quality of collaboration. I'm 100% sure nVidia's drivers would be even better if they opened their sources so developers could look inside and spot bugs when they happen. But they already do a good job by themselves. AMD drivers got way better when they opensourced. I'm sure the same would happen for nVidia, but nVidia doesn't seem to agree. The whole matter is centered around that. [0] http://forums.vega-strike.org/ [1] http://sourceforge.net/tracker/?group_id=19507&atid=119507 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org