Am Donnerstag, den 06.09.2018, 16:43 +0200 schrieb Lukas F. Hartmann:
> Hi,
>
> I've updated to and rebuilt the latest git versions of linux, drm, mesa
> and kmscube on an imx6qp system. I tried both with etnaviv as a module
> and compiled into the kernel (no difference).
>
> Mesa no longer picks up etnaviv for GL rendering, but always reverts to
> softpipe. A bit of debugging revealed that the following codepath fails:
>
> imx_drm_screen_create -> loader_open_render_node("etnaviv") ->
> drmGetDevices2 -> drmProcessPlatformDevice(... "/dev/dri/renderD128") ->
> drmParsePlatformBusInfo -> sysfs_uevent_get
>
> The latter function opens /sys/dev/char/226:128/device/uevent and looks
> for OF_FULLNAME, but this key is not present on my system. The node
> contains only:
>
> DRIVER=etnaviv
> MODALIAS=platform:etnaviv
>
> Whereas /sys/dev/char/226:0/device/uevent contains:
>
> DRIVER=imx-drm
> OF_NAME=display-subsystem
> OF_FULLNAME=/display-subsystem
> OF_COMPATIBLE_0=fsl,imx-display-subsystem
> OF_COMPATIBLE_N=1
>
> Which is not the render node.
>
> > According to https://patchwork.kernel.org/patch/9487631/#19940985 there
> should be more lines (device tree related?) in the uevent file for the
> render node, and I wonder why they don't exist.
Since kernel 4.17 (drm/etnaviv: remove the need for a gpu-subsystem DT
node) the etnaviv DRM driver doesn't have an associated DT node
anymore. This is technically correct, as the etnaviv device is a
virtual device driving multiple hardware devices.
libdrm should be fixed to properly deal with this.
Regards,
Lucas
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
