Bug#907136: Please consider enabling etnaviv on arm64 after 18.2.0

[Guido Günther]

Source: mesa
Version: 26
Severity: wishlist
Version:

Hi,
with etnaviv kernel driver and libdrm shaping up on arm64 it would be
great to have this enabled as well. Not all patches for GC7000 (imx8)
are mainline yet:

https://github.com/laanwj/mesa/tree/gc7000

but most of them are and it would be nice to have this enabled for early
experiments.

Cheers,
-- Guido


-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[Debian Bug Tracking System]

Your message dated Fri, 16 Nov 2018 15:04:16 +0000
with message-id <E1gNffM-0003qL-***@fasolo.debian.org>
and subject line Bug#907136: fixed in mesa 18.2.4-1
has caused the Debian Bug report #907136,
regarding Please consider enabling etnaviv on arm64 after 18.2.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Mon, 19 Nov 2018 15:34:34 +0000
with message-id <E1gOlZK-0004bP-***@fasolo.debian.org>
and subject line Bug#907136: fixed in mesa 18.2.5-1
has caused the Debian Bug report #907136,
regarding Please consider enabling etnaviv on arm64 after 18.2.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)