08:11 <kszaq> xdarklight: I tried running your meson-mx-integration-5.3-20190516 on a meson8b device - can you tell me if after modifying device tree HDMI output should work or is this something still in progress?

16:59 <mjourdan> Darkmatter66: Currently stuck on "Wait bl30..." followed by a reboot, no idea what's happening.. Can't even reach u-boot on the C2. Here's my build+deploy script in case anyone sees something wrong in it: https://pastebin.com/uqwdrtyG

17:34 <kszaq> mjourdan: Perhaps one line missing? https://github.com/kszaq/LibreELEC.tv/blob/amlogic/projects/Amlogic/bootloader/mkimage#L32

17:36 <kszaq> Ah no, I can see that you have it in the last one.

17:40 <kszaq> Nonetheless u-boot readme splits this in two lines: https://github.com/kszaq/LibreELEC.tv/blob/amlogic/projects/Amlogic/bootloader/mkimage#L32

17:41 <kszaq> Sorry, wrong link: https://github.com/u-boot/u-boot/blob/master/board/amlogic/p200/README.odroid-c2#L58-L66

21:28 <mjourdan> kszaq: thanks, tried splitting the u-boot img in 2xdd like is done in that README, but it doesn't change anything, still stuck on "Wait bl30..." https://pastebin.com/3BBKRHQb

22:05 <mjourdan> huh, so the fip_create tool doesn't put the various bl3* images in the same order in fip.bin as a "healthy" fip.bin, and it looks like aml bootloader fetches the first entry as bl30 no matter what is depicted in the fip header

22:10 <mjourdan> mkay, deleting fip.bin and letting the tool creating it from scratch instead of updating it did the trick to get one with the right file order.. ugh