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. Before 4.17 the userspace had access to the following information: # cat /sys/dev/char/226:128/device/uevent DRIVER=etnaviv OF_NAME=gpu-subsystem OF_FULLNAME=/gpu-subsystem OF_COMPATIBLE_0=fsl,imx-gpu-subsystem OF_COMPATIBLE_N=1 MODALIAS=of:Ngpu-subsystemT<NULL>Cfsl,imx-gpu-subsystem DRIVER=imx-drm OF_NAME=display-subsystem OF_FULLNAME=/display-subsystem OF_COMPATIBLE_0=fsl,imx-display-subsystem OF_COMPATIBLE_N=1 Afer 4.17: # cat /sys/dev/char/226:128/device/uevent DRIVER=etnaviv MODALIAS=platform:etnaviv As a consequence we need to add fallback mechanism to handle this change. This series fixes kmscube and friends when using mesa's loader_open_render_node(..). Christian Gmeiner (2): xf86drm: fallback to DRIVER uevent entry when OF_FULLNAME fails xf86drm: handle non existing OF_COMPATIBLE_N uevent entry xf86drm.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) -- 2.17.2 _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
