logo

blog

My website can't be that messy, right? git clone https://anongit.hacktivis.me/git/blog.git/

Email to graphics-dev@chromium.org about nouveau blacklisting.xhtml (2727B)


  1. <!--
  2. Copyright © 2014 Haelwenn (lanodan) Monnier
  3. SPDX-License-Identifier: LAL-1.3
  4. -->
  5. <article lang="en" class="h-entry">
  6. <a href="/articles/Email%20to%20graphics-dev@chromium.org%20about%20nouveau%20blacklisting"><h1>Email to graphics-dev@chromium.org about nouveau blacklisting</h1></a>
  7. <pre>
  8. Date: Sun, 6 Jan 2019 01:54:46 +0100
  9. From: Haelwenn Monnier &lt;contact@hacktivis.me&gt;
  10. To: graphics-dev@chromium.org
  11. Subject: Nouveau blacklisting
  12. Message-ID: &lt;20190106005446.GA22465@cloudsdale.the-delta.net.eu.org&gt;
  13. MIME-Version: 1.0
  14. Content-Type: text/plain; charset=us-ascii
  15. Content-Disposition: inline
  16. User-Agent: Mutt/1.10.1 (2018-07-13)
  17. Hello,
  18. I would like to complain about the blacklisting of nouveau in the
  19. chromium graphics stack, nouveau is a useful replacement to the proprietary
  20. driver and linked tools from NVidia, notably, because of the following cases:
  21. - Ethics/Choice, nvidia being a proprietary driver, that litterally gets
  22. about everything graphics related passed to it, it can be very sensible, be it
  23. for privacy or politics (they could ban applications or some API).
  24. - Wayland, as the nvidia driver wrongfully provides their own API that only
  25. a very few compositors provide. wlroots, created for usage in Sway for example
  26. will never support their API<a href="#anchor-1">[1]</a>.
  27. - Up-to-date software, the proprietary driver has quite the history of lagging
  28. behind on the software it depends on, for example the 304.xx legacy branch
  29. needs a vulnerable Xorg branch(1.19.x) and when spectre/meltdown arrived a
  30. legacy branch was incompatible with the stable branch of the linux kernel
  31. at that time.
  32. Which honeslty is quite funny considering that you apparently banned it
  33. because of outdated mesa builds<a href="#anchor-2">[2]</a>, which just cannot be fixed with the legacy
  34. branch. Something which I think will probably get even worse if WebGL will have
  35. to use the slow and power-hungry software rendering.
  36. I do not think that chromium is very liked in a lot of the linux community,
  37. probably because of the overly large codebase and the link to Google, but doing
  38. this will probably raise quite a large and visible flag to even non-maintainers.
  39. 1: <a id="anchor-1" href="https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html">https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html</a>
  40. 2: <a id="anchor-2" href="https://www.phoronix.com/scan.php?page=news_item&amp;px=Chrome-Blacklisting-Nouveau">https://www.phoronix.com/scan.php?page=news_item&amp;px=Chrome-Blacklisting-Nouveau</a>
  41. --
  42. Haelwenn (lanodan) Monnier
  43. https://hacktivis.me/
  44. </pre>
  45. <p><a href="https://queer.hacktivis.me/objects/64041d50-d1b8-4195-a5e3-6d75507b6119">Post for comments and sharing on the fediverse.</a></p>
  46. </article>