Re: [PATCH] xf86drm: continue after drmProcessPlatformDevice failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 19 July 2017 at 16:37, Gurchetan Singh <gurchetansingh@xxxxxxxxxxxx> 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
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel




[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux