On Thu, Oct 24, 2019, at 23:34, Lukasz Janyst wrote: > My setup uses the master branch of uboot as of a couple of day ago. I > also use the master branch of arm-trusted-firmware as BL31 with the > 0aad563c commit reverted. I reverted this commit because the system > fails to boot with it in even though all the addresses processed by > arch/arm/mach-rockchip/make_fit_atf.py seem right. The kernel I try to > boot is a couple days old version of linux-next with defconfig, but I > see the same problems with any mainline kernel I tried. The code in uboot's drivers/ram/rockchip/sdram_rk3399.c seems to be broken even when looking from a standpoint of a layperson. Some error checks are incorrect, parameters are overridden in multiple places for no good reason, the way some loops and function calls are structured does not make much sense. Furthermore, it appears that the code in plat/rockchip/rk3399/drivers/dram of arm-trusted-firmware is undoing what the bootloader is doing. Has that ever worked for anyone? Lukasz _______________________________________________ Linux-rockchip mailing list Linux-rockchip@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-rockchip
