[PATCH] xf86drm: continue after drmProcessPlatformDevice failure
Emil Velikov
emil.l.velikov at gmail.com
Thu Jul 20 11:33:25 UTC 2017
On 19 July 2017 at 16:37, Gurchetan Singh <gurchetansingh at chromium.org> wrote:
> On ChromeOS devices, readdir() processes the directory in
> the following order:
>
> -NAME- -TYPE-
> . n/a
> .. n/a
> vgem n/a
> card1 DRM_BUS_PLATFORM
> renderD129 DRM_BUS_PLATFORM
> card0 DRM_BUS_PCI
> renderD128 DRM_BUS_PCI
> controlD64 DRM_BUS_PCI
>
> In drmGetDevices2, after drmProcessPlatformDevice fails for
> /dev/dri/card1, we don't process the remaining directory entries.
> As such, Vulkan fails to initialize since Mesa uses drmGetDevices2.
> To fix this, continue if drmProcessPlatformDevice fails.
Added a fixes tag and addressed the host1x + usb instances.
Thank you!
Emil
More information about the dri-devel
mailing list