There is no GPU initialization problem and here is overall summary: Upon boot, we cannot control which device, GPU or DSS, will get probed first and who ever gets probed first will get /dev/dri/card0 assigned. In general, your userspace application needs to query the /dev/dri device, identify the GPU or DSS card and create the appropriate application APIs. kmscube does not have such logic but the developers of kmscube allow their users to pass the /dev/dri card through the --device option. On the other hand, weston will go query your display card upon boot and use the appropriate /dev/dri/card node upon booting. In summary, your custom application needs to query the display device as part of it's init logic. Regards, Krunal
↧