We are using the i.MX6DP processor on a custom board. Our project was previously based on Yocto Morty but at some point we have decided to migrate to Yocto Rocko. The Linux Kernel version which we used when we ran Morty was 4.1.15. During the migration to Rocko we obviously had to adapt to a newer version of the Linux Kernel.
Our first attempt was to use the 4.9.11 kernel from the meta-freescale repository. We got the following errors:
[ 0.518654] ldb 2000000.aips-bus:ldb@020e0008: split mode
[ 0.524420] ldb 2000000.aips-bus:ldb@020e0008: split mode or dual mode, ignoring second output
[ 0.533710] mxc_sdc_fb fb@0: registered mxc display driver ldb
[ 0.574678] imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
[ 1.575154] imx-prg 21cd000.prg: wait for buffer ready timeout
[ 1.609004] imx-pre 21cb000.pre: timeout waiting for PRE to run out of problematic window for shadow update
[ 1.609016] imx-ipuv3 2800000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000
[ 2.657904] mxc_sdc_fb fb@0: MXCFB_WAIT_FOR_VSYNC: timeout 0
[ 3.671258] mxc_sdc_fb fb@0: MXCFB_WAIT_FOR_VSYNC: timeout 0
[ 4.177912] mxc_sdc_fb fb@0: timeout when waiting for on the fly config irq
[ 4.177917] fbcon_init: detected unhandled fb_set_par error, error code -110
[ 6.309572] imx-pre 21cb000.pre: timeout waiting for PRE to run out of problematic window for shadow update
[ 6.336961] Console: switching to colour frame buffer device 240x45
[ 6.844580] mxc_sdc_fb fb@0: timeout when waiting for flip irq
Later on we have also attempted to use the 4.9.88 kernel from the NXP layers and got the same errors. We have also tried various combinations of layers (like fully using NXP's instead of the community ones), all to no avail, we keep getting the fb errors above.
Some other things worth mentioning:
- We did not have these issues in 4.1.15 when we were using Morty.
- We are currently using Rocko with the 4.1.15 kernel. We don't get these issues.
- We are using framebuffer and eglfs. No X11 and no Wayland.
Has anyone had similar problems? Any ideas on what the issue could be? We would really like to upgrade to a newer kernel version but these errors are preventing us from doing so.