Thank you for the answer. For imx51evk which u-boot is better? u-boot-fslc or u-boot-imx?

I'd go with dunfell as you need Linux mainline for it. Em ter., 25 de ago. de 2020 às 06:08, Mauro Ziliani <mauro@...> escreveu: -- Otavio Salvador O.S.

Hi all. I'm working on a imx51evk clone board and  Zeus. U-boot-fslc restart with POR cause. Where i can find good docs for Zeus and imx51evk? Best regards,   MZ

Hello, I want to connect 2 identical FHD screens (timing-wise) to my imx6q board. One is LCD and the other one (dualchannel) LVDS. I only want to render content once (for perfomance) and output it on

Hi Wouter, <w.vanhauwaert@...> wrote: Yes, when I looked at the commit you referred to I thought initially that it only added drivers/video/fbdev/mxsfb.c, which is the eLCDIF controller. In

Sorry, but I think that's not correct... Indeed, you can use fsl,imx-parallel-display, but then you're using the opensource/drm mainline way of addressing the ipu, and not the freescale proprietary

Hi Wouter, <w.vanhauwaert@...> wrote: eLCDIF is a different display controller that is found on other i.MX SoCs like imx23/imx28/imx6sl/imx6sx. On imx6q/dl the display controller is the

Hello Christian, Do you see the same behavior with linux-fslc-imx kernel tree? It is basically NXP kernel + latest patch level from upstream. Can you test that one and let here know if you have the

Hi Christian, What is the Ethernet PHY on your board? Is it getting detected by looking at the dmesg log? Could you share the schematics and device tree?

Hi, I'm porting a custom MX6DL board from linux-imx to linux-fslc (along with use-mainline-bsp in FEATURES). The primary reason for this choice was for etnaviv support and a general preference for a

Hmm, it doesn't work. But is this endpoint-setup not meant to be used together with DRM? Whereas before it was for mxcfb? I'm stilll a bit lost...

Ok, I'll try it out. Still I don't understand why they would only change half of the functionality.... (And who decides or follows up)

Great, thanks!

<tessadriandrea@...> wrote: This is definitely a wrong list for those changes, it should go to LKML instead. This list is used for discussions regarding Yocto Project distribution, and I believe

On Thu, Aug 13, 2020 at 9:49 AM Christian Betz via lists.yoctoproject.org <christian.betz=gmail.com@...> wrote: I forgot to mention: I am using "use-mainline-bsp" here and I think that matters, as

Hi. I recently faced a similar problem on a custom imx6dl board, also with linux-fslc. In my case i only have a single panel but it seems I had to define two panels to make the devicetree compiler

I've just developed and tested cyclic DMA transfer for a SPI device on a IMX6UL with kernel 4.9.88 I wanted to have a single SPI transfer repeated continuously in order to feed a DAC for generation of

But that's the mainline way of working, no? When using etnaviv/drm/imx-ipu... ? Why would the old ldb-style still work, but the old lcd isn't?

Yes this has completely changed, look at NXP's MEK devicetrees to figure that out, at least I was once able to figure it out like that. On Colibri-iMX8X I once had it running with something like

How do you correctly put a parallel lcd display in linux 5.4? Uptill 4.9, there was a mxc_lcdif.c, but seems to be missing now? In the devicetree, you used to add a node which had