18:38 <warpme_> stikonas: is https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ applicable also to rk3328?

18:58 <stikonas> warpme_: with some modifications I guess

18:58 <stikonas> different u-boot/atf target

18:58 <stikonas> but I suspect you can mostly follow it

19:00 <warpme_> ok. so i already tried (with diff.PLAT in ATF, and defconfig in uboot) and my rk3328 beelink a1 hangs at boot. still thinkning where issue might be.....

20:12 <mrjay> rk3066 boot: irq 28: nobody cared (try booting with the "irqpoll" option)

20:12 <mrjay>  some new undocumented irq on rk3066

20:12 <mrjay> ????

21:51 <hexdump01> warpme_: i remember that jock from armbian and me did some tries on rk3318 and rk3328 tv boxes with different u-boots and in the end we had to go back to the blobs at least fro the mem timing as the u-boot internal one did not work well with the mem in those boxes

21:56 <hexdump01> warpme_: this is the procedure to only use the ddr.bin blob and the rest from mainline u-boot: https://github.com/hexdump0815/u-boot-misc/blob/master/readme.rk3328#L87-L118

21:58 <hexdump01> warpme_: in the misc.rk3328 dir you can find some ddr.bin files - 1.15 worked for most boxes - i also hacked one together with 666mhz instread of 333mhz which worked on some boxes

21:58 <hexdump01> warpme_: if you use mainline atf you will not have dmc, so the memory will stay at the boot clock (i.e. usually quite slow)