Mxc_sdc_fb Mxc_sdc_fb.2 No Mxc Display Driver Found
Mxc_sdc_fb Mxc_sdc_fb.2 No Mxc Display Driver Found Windows 7
The LVDS modes are somewhat confusing. With fbdev devices you can rather easily test which device belongs to which display by simply write random data to a framebuffer device: dd if=/dev/urandom of=/dev/fb0There is some valuable information also in our article, especially the mxcfbX to /dev/fbX assignment!Since I do not have the setup I cannot test here, so my instructions are based on my understanding and my best guesses.The 4 framebuffer devices mxcfb0-3 are connected to IPU 1 Display 1, IPU 1 Display 2, IPU 2 Display 1 and IPU 2 Display 2 (note that often a zero based ID is used). The LVDS peripheral LDB allows to route its channels to any of those four IPU displays. By default lvds-channel@0 is configured to use ipu2-di1 hence should be available on mxcfb3 and lvds-channel@1 to ipu1-di0 hence should be on mxcfb0.With that I would assume that setenv vidargs 'video=mxcfb0:dev=ldb video=mxcfb1:off video=mxcfb2:off video=mxcfb3:dev=ldb fbmem=512M' should enable mxcfb0 and mxcfb3. This works pretty good.Thank you so much.The display with the mxcfb3 framebuffer has the wrong colour depth and I will check how to fix that, (Do you have any Idea why that could happen?) but now I can see two different applications on both screens with 62fps from the 'Cinematic Experience Demo'.I have also tried to switch to the mxcfb2, but this doesn't seem to work.
I think this is because of the overlapping frame buffers mxcfb0 and mxcfb2.Last but not least: I get the following error: X.X mmc2: Switching to 3.3V signalling voltage failed. Should I open a new thread for that? There is no 1:1 relationship between the mxcfbX devices you specify on the command line and the /dev/fbY device files.The i.MX6D/Q has two IPU's, each capable of driving two display interfaces DI0 and DI1. DI0 allows to use addionally an overlay framebuffer while DI1 does not. The IPU driver will create two /dev/fbX devices for DI0 while it will only create one for DI1.I guess your device tree uses 'crtc = 'ipu2-di1';' for the first LDB channel and 'crtc = 'ipu1-di0';' for the second.
Thus mxcfb0 will be mapped /dev/fb0 (DI1 - one device file) and mxcfb3 will be mapped to /dev/fb1 and /dev/fb2./dev/fb2 will by default only have a small resolution. The application using the overlay can then change its size and the position on /dev/fb1 which it wants to use.