AW: running etnaviv driver on i.mx6

[Wagner Andre]

Hi Fabio,

thanks for your fast answer!
A few hours ago, i just found an old article of you where you  described howto do it ;):

https://imxdev.gitlab.io/tutorial/Running_kmscube_with_Etnaviv_on_mx6sabresd_board/

I try to do the setup you described there, but i still got no plan how to port the devicetree i got for my board from the NXP kernel variant to the mainline, without causing a bunch of new problems.

 A thing I directly noticed as a difference between the setup you described there and mine is that the "2204000.gpu" (i think thats the imx-drm) does not show up in /proc/interrupts only the other two (130000.gpu and 134000.gpu) also with interrupt 10 and 11 as yours. The imx-drm shows up as /dev/dri/card1. Do you have a guess if i am just missing something obvious? Would be nice if i would only need a small change and not changing everything...

Grettings,
André


[https://www.richard-wolf.com/mam/data/Typo3/banner/e-mail-banner-DGU25.png]<https://www.richard-wolf.com/de/unternehmen/kongresse/messe-detail/77-kongress-der-deutschen-gesellschaft-fuer-urologie-dgu><https://www.richard-wolf.com/de/academy-prima-vista/masterclass-workshops/masterclass-workshop-minimally-invasive-upper-gi-surgery-2><https://www.richard-wolf.com/en/company/congresses/congress-detail/arab-health-2025>

Richard Wolf GmbH, Pforzheimer Strasse 32, 75438 Knittlingen
Managing Directors: Juergen Pfab, Juergen Steinbeck. Trade Register: Mannheim HRB 510031

Richard Wolf GmbH routinely monitors the content of e-mail sent and received via its network for the purposes of ensuring compliance with its policies and procedures. Richard Wolf GmbH is not responsible for any changes made to the message after it has been sent. Where opinions are expressed, they are not necessarily those of Richard Wolf GmbH. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended addressee, or the person responsible for delivering it to them, you may not copy, forward, disclose, or otherwise use it or any part of it in any way. To do so may be unlawful. If you receive this e-mail by mistake, please advise the sender immediately.

Data Protection Policy<https://www.richard-wolf.com/en/data-protection-policy>  |  Legal Information<https://www.richard-wolf.com/en/legal-information/>  |  Terms & Conditions<https://www.richard-wolf.com/en/terms-conditions/>

________________________________
Von: Fabio Estevam <festevam at gmail.com>
Gesendet: Montag, 4. August 2025 16:39
An: Wagner Andre <andre.wagner at richard-wolf.com>
Cc: etnaviv at lists.freedesktop.org <etnaviv at lists.freedesktop.org>
Betreff: Re: running etnaviv driver on i.mx6

Hi Andre,

On Mon, Aug 4, 2025 at 8:11 AM Wagner Andre
<andre.wagner at richard-wolf.com> wrote:
>
> Hello everyone,
>
> I try to run a run an (qt) app accelerated by the upstream etnaviv driver on an i.MX6 DL based SBC, but I just cannot get it working...
>
> What I did so far:
>
> I patched the imx-drm back from NXP version (since its adapted to their closed source galcore driver) to vanilla version, which should work with etnaviv. Dmesg shows also "Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0" and "  Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1". So I expect both kernel drivers to work.
> I installed a Ubuntu 22.04 with a slightly modified NXP Linux kernel in version 5.15.148 and used from Ubuntu 22.04 mesa in version 23.2.1

It's better not to use the NXP kernel at all if you want to use Etnaviv.

Just use a mainline kernel from kernel.org with the
imx_v6_v7_defconfig, boot it, and the Etnaviv driver will be loaded by
default.

You can then try to run the 'kmscube' application to confirm that the
driver is functional.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/etnaviv/attachments/20250804/8609e427/attachment-0001.htm>