I will share what I found about the broken fb device issue on the i.MX6.
I got a reply from a developer within NXP that indicates there is a
known bug with their fb device support with the 4.14.98 kernel. It seems
that the last kernel where the fb works is probably 4.9.51, which they
recommend.
I suspect this may be the same issue which caused NXP to decide to drop
all support for fb (and X11) on the i.MX8. However, this issue affects
the i.MX6 also and I see no indication that it will ever be fixed, since
NXP's plan seems to be to support Wayland only, at least on the i.MX8.
This seems strange to me because it freezes development on the i.MX6 at
the 4.9.51 kernel, unless Wayland is used. Even a lot of NXP's own unit
tests for the GPU, VPU, IPU and V4L2 will not run without fb, even
though their release notes for their Yocto support claim they tested on
a lot of boards. It seems that testing merely means booting and not
actually running unit tests.
If I have this wrong or anyone can shed more light on this situation,
please do.
Thanks, Clay Montgomery
On 11/24/2019 2:54 PM, Clay D. Montgomery wrote:
Hello,
I am trying to migrate a project from Yocto Pyro (3.14 kernel) to
Sumo and a newer kernel on the i.MX6 Wandboard Quad.
I am following the instructions in the
i.MX_Yocto_Project_User's_Guide, to build. To summarize, I am using:
repo init -u
https://source.codeaurora.org/external/imx/imx-manifest -b
imx-linux-sumo -m imx-4.14.98-2.0.0_ga.xml
DISTRO=fsl-imx-fb MACHINE=wandboard source fsl-setup-release.sh
-b build-fb
bitbake fsl-image-machine-test
The problem is that the built linux image has no fb device and this
causes many other problems, such as with V4L2, OpenGL ES and even
NXP's unit tests, such as:
./mxc_vpu_test -D "-f0 -x0 -i akiyo.mp4"
[ERR] unable to open fb0
Even 'fbset' fails, with:
open /dev/fb0: No such file or directory
As best as I can tell, fb support should be enabled. Here is the
relevant portion of my defconfig:
CONFIG_DRM=y
CONFIG_DRM_VIVANTE=y
CONFIG_FB=y
CONFIG_FB_MXS=y
CONFIG_FB_MXC_SYNC_PANEL=y
CONFIG_FB_MXC_MIPI_DSI=y
CONFIG_FB_MXC_MIPI_DSI_SAMSUNG=y
CONFIG_FB_MXC_TRULY_WVGA_SYNC_PANEL=y
CONFIG_FB_MXC_TRULY_PANEL_TFT3P5079E=y
CONFIG_FB_MXC_TRULY_PANEL_TFT3P5581E=y
CONFIG_FB_MXC_LDB=y
CONFIG_FB_MXC_HDMI=y
CONFIG_FB_MXS_SII902X=y
CONFIG_FB_MXC_DCIC=m
CONFIG_HANNSTAR_CABC=y
CONFIG_FB_MXC_EINK_PANEL=y
CONFIG_FB_MXC_EINK_V2_PANEL=y
CONFIG_LCD_CLASS_DEVICE=y
CONFIG_LCD_L4F00242T03=y
CONFIG_LCD_PLATFORM=y
CONFIG_BACKLIGHT_PWM=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_MXC_IPU=y
CONFIG_MXC_IPU_V3_PRE=y
CONFIG_MXC_SIM=y
CONFIG_MXC_MIPI_CSI2=y
CONFIG_MXC_HDMI_CEC=y
CONFIG_MXC_GPU_VIV=y
I have found that the fb device will work if I select the
'CONFIG_DRM_ETNAVIV' option, instead of 'CONFIG_DRM_VIVANTE', but I
need the Vivante option to get their newer drivers.
Can someone please advise how I can resolve this issue?
Any assistance would be greatly appreciated.
Thank You, Clay Montgomery
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#24145):
https://lists.yoctoproject.org/g/meta-freescale/message/24145
Mute This Topic: https://lists.yoctoproject.org/mt/61881553/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
