On 1/6/19 9:37 AM, Jason Ekstrand wrote:
On Sat, Jan 5, 2019 at 2:40 PM Ilia Mirkin <imir...@alum.mit.edu
<mailto:imir...@alum.mit.edu>> wrote:
It looks like as of Chromium 71, nouveau is completely blacklisted.
That's rather unfortunate. :-( The intel mesa drivers were also
blacklisted for quite some time a while back. I'm not really sure what
we did to get blacklisted or what we did to get unblacklisted.
We had lots of GPU hangs from WebGL tests. We fixed things until in some
point things were passing and our web team sent a patch to Chromium to
enable it back again. This is probably the best route to get Nouveau
enabled as well.
Have to note that we do have currently some WebGL issues on i965 too ..
should take a look at some point.
I don't really see a way back from this, since they don't cite any
easily reproducible issues, except that some people had some issues
with indeterminate hardware and indeterminate versions of mesa.
In the bug that triggered this
(https://bugs.chromium.org/p/chromium/issues/detail?id=876523), where
I might have slightly lost my cool, they (at the end) suggested that
we try to make nouveau a first-class citizen with chromium. However I
will never be able to present concrete evidence that inconcrete issues
are resolved. I did run the WebGL CTS suite, but that resulted in some
hangs from the the max-texture-size-equivalent test, and some
browser-level weirdness after some tests where later tests all fail
(due to what I have to assume is a browser bug). I don't think I
managed to properly track down the true reason why. I didn't want to
reach out to them with such results, as that's just further evidence
of nouveau not working perfectly.
If you want concrete bugs to fix, I highly recommend OpenGL[ES]
conformance tests, dEQP, and the WebGL CTS (which is mostly a re-hash of
the OpenGL ES 3.0 CTS). Google cares quite a bit about driver
conformance and are much more likely to consider nouveau to be
high-quality if those test suites are in good shape. Years of
experience dealing with Google says that dEQP results speak much louder
than philosophical arguments about who should decide whether or not
Chromium should accept the distro GL. Fortunately for you, the well
funded driver teams (Intel and AMD) have already done a lot of the
painful work of getting a lot of the bugs and "bugs" out of core mesa
and galium. What's left are likely real back-end driver bugs which may
be affecting some user somewhere so they're worth fixing.
In the meanwhile, end users are losing accelerated WebGL which in
practice worked just fine (at least in my usage of it), and probably
some other functionality.
One idea is to flip GL_VENDOR to some random string if chromium is
running. I don't like this idea, but I also don't have any great
alternatives. We can also just take this, as yet-another nail in the
nouveau coffin.
You asked for opinions, so here you go. :-P In my personal (and rather
disinterested) opinion, I would recommend against such measures. The
last thing anyone needs is an arms race between nouveau and Chromium
teams. I think the better short-term thing to do would be to provide
some documentation about WebGL and educate users about Chromium's
--ignore-gpu-blacklist option. This documentation could go on the mesa
website or, likely more usefully, it could go in various distro wiki
entries about nouveau and/or general nvidia issues. In the long term,
what's needed is improving nouveau quality and stability and re-building
trust with the Chromium team. I'm not trying to attack nouveau here but
the fact is that trust has been lost due to an unfortunate history of
mis-filed (against Chromium) bugs. That trust doesn't get re-built by
nuclear solutions.
--Jason
_______________________________________________
mesa-dev mailing list
mesa-...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
