@NewBee, thank you for your answer. I have done this already (Vivado 2020.2). The design includes HDMI in/out with updated dvi2rgb and rgb2dvi IPs, so now they are compatible with the newer Vivado versions.
This design (zVP-Lnx) is based on other design (zVP) with only one difference - zVP uses 1 VDMA for HDMI in/out, while zVP-Lnx uses 2 separate VDMA - one for write (HDMI in) and one for read (HDMI out). Nothing else is different. zVP is tested with bare metal code and is working perfectly when started from debug session. I expect the same for zVP-Lnx, but to be honest - I didn't tested it in this way.
So I have zVP-Lnx up and running - fsbl, u-boot and kernel. But my kernel panic within xvtc_probe (I can copy/paste the exact error later today). My first thought was about something related to reset signals and/or dts clock description. But so far I can't find anything out of ordinary, and as I noted it will work with bare-metal code. So my hope was to cross-check with some newer version of base linux design provided from digilent which I use as reference (2017.4) and to be able to locate the problem. Well, I'm stuck here...
i.shugov got a reaction from flyingfork in ZYBO 7Z-20 bsp for 2020.1 or 2020.2