Hi,
thanks for the answer. This is my kernel config:
developer@ubuntu:~/beaglebone/debian-fw/bb-kernel/KERNEL$ grep FW_LOADER_USER_HELPER .config
developer@ubuntu:~/beaglebone/debian-fw/bb-kernel/KERNEL$ grep DRM .config
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_LOAD_EDID_FIRMWARE=y
CONFIG_DRM_GEM_CMA_HELPER=y
CONFIG_DRM_KMS_CMA_HELPER=y
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
CONFIG_DRM_I2C_NXP_TDA998X=y
# CONFIG_DRM_UDL is not set
CONFIG_DRM_TILCDC=y
# CONFIG_DRM_OMAP is not set
I am quite sure that in the end kernel finds firmware because otherwise the display isn't working. I only get a image on the display if my edid file is used.
Robert
2015-01-14 11:40 GMT+01:00 Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx>:
On Wed, 14 Jan 2015, Robert Kuhn <spamhalde2@xxxxxxxxxxx> wrote:
> using drm_kms_helper.edid_firmware the boot time is much longer (~1min)
> than without it. I attach the boot log ("drm.debug=0x06"), one time
> with drm_kms_helper.edid_firmware, one time without.
>
> What could be the problem?
>
> I am using Kernel 3.8.13-bone69 on a Beaglebone black. I
> used drm_kms_helper.edid_firmware before and never saw this issue.
Just a guess, kernel doesn't find the firmware and you fallback to user
mode helper, which is no longer supported by udev.
Try ensuring you have the path right, and disable FW_LOADER_USER_HELPER
kernel config option.
HTH,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
