Re:Chromium blacklists Nouveau
by geofft on Saturday January 05, 2019 @08:08PM
(#18835600)
But that's the part that's crashing. I'm suggesting Chrome use llvmpipe to do whatever they needed hardware acceleration for, generate a single boring texture on a single big rectangle, and pass that through to the graphics driver. That way Chrome itself isn't loading the Nouveau libGL and is much more insulated from incompatibilities between Chrome and Nouveau, whosever fault it might be.
[ Parent
| on HN ]
WebGL requires far more than just blitting onto a single boring texture.
That's why you go through llvmpipe - you use the Mesa OpeGL implementation in LLVM-JIT-accelerated but pure software mode to implement WebGL, get the results onto a texture, and pass that texture onto your actual graphics card.
That seems like something you'd prefer not to do if your OpenGL driver wasn't broken.
That's what swiftshader does.
Whoa, I totally missed that! https://blog.chromium.org/2016/06/universal-rendering-with-s... So is it the case that you get decent (though perhaps not great) WebGL performance even if you have no GL-compatible graphics driver at all?
Then are Nouveau users only losing performance and not functionality as a result of this Google decision?