Re:Chromium blacklists Nouveau
by xyzzyz on Saturday January 05, 2019 @08:31PM
(#18835720)
Yes, and the distributor or administrator is free to rebuild the browser or just set the flag to disable blacklisting. It’s only default behavior that changed.
[ Parent
| on HN ]
Chrome has the special sauce — distributors and administrators cannot rebuild it, only Chromium.
Re:Chromium blacklists Nouveau
by magicalist on Saturday January 05, 2019 @11:15PM
(#18836534)
Flip the flag then.
It's crazy to suggest they should give web access (not just webgl, but CSS styling) to a buggy GPU driver by default without an opt in by the user.
Re:Chromium blacklists Nouveau
by smueller1234 on Sunday January 06, 2019 @06:48AM
(#18837854)
Is that different than the branding/trademark issue that Firefox also had for years?
(Not bring cynical, I genuinely don't know.)
Yes, it's different. You can build trademark Firefox so long as you do not modify it at all. You cannot build Chrome from the chromium sources — there are components which are not present in the open source repository. It's not just the trademark, unlike Firefox vs Iceweasel.
Re:Chromium blacklists Nouveau
by smueller1234 on Tuesday January 08, 2019 @02:54AM
(#18854023)
Thanks for the explanation!
From reading more about it, it seems these are all benign (in the sense of Chromium couldn't ship h264 because it's licensed but Chrome can).