Hello all,
(cc'ing everybody who I think might care - please ignore if you don't)
Chromium [as of 71] now defaults to software rendering when it detects
the nouveau driver. This is bad for the ARM ecosystem, since it is the
only driver we have for NVIDIA hardware, and it has fewer issues than
AMD GPU drivers + hardware running on ARM systenms.
https://lists.freedesktop.org/archives/nouveau/2019-January/031798.html
It can be addressed by setting the 'ignore-gpu-blacklist' option, but
this requires an explicit action from the user, which is unfortunate
and undesirable.
Is there any way we can influence this?
Hi folks,
In the hope this might be interesting for people...
I've just finished with my analysis of rebuilding the Debian archive
for armel and armhf using arm64 build machines. I've been rebuilding
the archive *specifically* to check if we would have any problems
building our 32-bit Arm ports (armel and armhf) using 64-bit arm64
hardware. I might have found other issues too, but that was my goal.
Executive summary:
As far as I can see we're basically fine to use arm64 hosts for
building armel and armhf, *so long as* those hosts include hardware
support for the 32-bit A32 instruction set. As I've mentioned before
in Debian, that's not a given on *all* arm64 machines, but there are
sufficient machine types available that I think we should be
fine. There are a couple of things we'll need to do in terms of setup.
See
https://blog.einval.com/2019/01/07#rebuilding_on_arm64
for the full article.
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs