jernej

@Christos, you can easily check if /boot device tree files are taken into account. Change board name and read it back through sysfs after reboot. If this doesn't work, you can always try to overload dts loaded by U-Boot by stopping autoboot and manually load kernel and device tree.

@Igor, values here are a bit high. I would suggest divider (second column) 2 and pll_video value of 294. 588 is extremely high clock and datasheet says that HW limit is around 600 MHz. Also HDMI PHY will probably be set better for such bandwith. Oh, and rounding frequency in table to nearest MHz would be also better. Slightly lower frequency doesn't really matter to the display, but driver works mostly by MHz.

Unfortunatelly, I don't have full insight in the DRM driver yet. From what I understand, full DRM drivers are preferred against simplefb, so in the process of DRM driver initialization simplefb driver gets disabled. So the only answer I can give you this time is that you can use U-Boot abbility to patch DT and disable DRM driver.

Nevermind the picture then. Well, while I certainly agree about 1080p limitation for older SoCs, because this is HW limitation, I disagree for newer ones. At least for mainline U-Boot. This functionality is also used for simplefb driver, where it is desirable to have native resolution. But you can always add your own patch a top of mainline.

Excellent. Can you make a picture of it? In the evening I will make a bit more chatty U-Boot so we will hopefully see where the problem lies. After that I can try to fix BSP kernel.

Uh, sorry, I forgot to update max framebuffer size. Can you please test again my U-Boot branch? Simple FEL boot should suffice.

I make some additional changes like disabling HDCP. @igor, can you please test if latest commit fixes issue with 4K monitor?

No, 297 is default value and the only correct one for 1080p

hm... you can try to enter u-boot console and change settings with fdt commands. I didn't yet analyze whole boot sequence...

IMO that would be good. I must check if LED section is using this defines but AFAIK Armbian doesn't use them anyway.

You mean during boot? This will come with next update. At least U-Boot didn't support video output until recently and driver is still experimental.

yes, it has same or better functionality and it must be present anyway (pinctrl) if you want to have useful kernel.

I think we care too much for [gpio_para] section. It is used only by sunxi-gpio driver, which is not loaded by default (it is module). This driver is even dropped by later Allwinner BSP revisions.

Just for fun - there is still something like this: https://github.com/saitoha/libsixel But I'm pretty sure this is not useful to OP.

GPIO sysfs interface should be the same on both, mainline and BSP, kernels. I checked that a month or so back. I think the only work which needs to be done here is identifying differences between the boards and implement this in a sane way.

Ah, ok, that works too. But given that you are not the first person with this question, I guess it would be nice to solve it in more general way. But then again, TV out is rarely used.

serial console, ssh, wherever you have access to the console... You can also add command to load it at boot, but for that you still have to have access to some kind of console. @igor, maybe you can make tv driver built-in? Seems that this is common issue and mostly chicken - egg problem if user has fresh image without access to the serial console and hdmi monitor.

Having separate script.bin file is only community invented trick for easier script.bin manipulation. Allwinner build tools integrate script.bin in U-Boot binary. I recommend that you get fex file from sources, change it, convert it to bin and extend boot script to load it to address 0x43000000 just before kernel is loaded and run. EDIT: We are talking about 64 bits... There is no fex/bin files for 64 bit arm, only dts/dtb. For that you have to have dtc, if you want to modify it. I'm not sure if this file is loaded from filesystem or like in bin case, integrated to U-Boot binary.

you have to load tv driver by: modprobe tv

You could also interact with serial console or recompile image for yourself with kernel config "CONFIG_TV_DISP2_SUNXI=y"

This sounds more like "splashpos=m,m" present in u-boot environment along with CONFIG_SPLASH_SCREEN_ALIGN enabled at compile time. Do you have by any chance Armbian splash patch enabled?

I cleaned up driver a bit and another test would be welcomed. Uh, another reason why this driver can be used is boot selection menu, grub style, albeit more simpler. Dual boot (or more), in simpler terms.

That means that kernel crashed somewhere at the beginning. It happened to me when I was adjusting CMA (ION) memory size. You may have luck with enabling earlyprintk. Note that it must be enabled in kernel config and in kernel arguments.

Don't forget to update to latest version through apt-get dist-upgrade I don't know about notification e-mails as I don't use them.

This patch was just a guess. Thanks for info. Given that your ouput complains about not properly terminated string, could you please provide binary edid? As I said, it should be somewhere in /sys, or if there isn't, in /proc.