00:15 <vagrantc> tuxd3v: i can confirm that u-boot 2020.01 boots

00:15 <tuxd3v> what is the atf you are using?

00:16 <vagrantc> 2.2

00:16 <tuxd3v> humm..

00:16 <vagrantc> 2.2-3 from debian

00:16 <tuxd3v> you have a extlinux.conf file?

00:16 <vagrantc> yes

00:17 <tuxd3v> maybe I am doing something wrong..

00:17 <tuxd3v> I am with atf mainline

00:17 <tuxd3v> one of those..

00:17 <tuxd3v> what are your bootargs?

00:17 <tuxd3v> I tried with:

00:17 <vagrantc> i don't think i set any bootargs

00:18 <tuxd3v> earlyprintk loglevel=8 earlycon=uart8250,mmio32,0xff1a0000 console=ttyS2,1500000n8 root=PARTLABEL="rootfs" rootfstype=ext4 fsck.repair=yes rw rootwait panic=10 init=/sbin/init net.ifnames=0 biosdevname=0 ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} video=HDMI-A-1:1680x1050@60 video=eDP-1:1680x1050@60 vga=current coherent_pool=1m

00:18 <vagrantc> try with an empty bootargs

00:19 <tuxd3v> maybe the best option :)

00:19 <vagrantc> tuxd3v: but are you saying you are getting to a u-boot prompt?

00:19 <vagrantc> with u-boot 2020.04 ? or some other version?

00:19 <tuxd3v> no I don't have boot prompt

00:20 <tuxd3v> I tried with 2 diferent aproachs

00:20 <tuxd3v> one using the extlinux.conf

00:20 <vagrantc> how far does it boot? bootargs doesn't matter until it tries loading the kernel and so on

00:20 <tuxd3v> the other using a boot.scr script

00:20 <tuxd3v> I believe it stays always in SPL

00:20 <vagrantc> because for me, it fails to even load u-boot, just u-boot TPL and u-boot SPL

00:21 <vagrantc> then bootargs, extlinux.conf, boot.scr ... all aren't even relevent yet

00:21 <vagrantc> you haven't gotten that far

00:21 <vagrantc> try with u-boot 2020.01 ... i'll try to bisect the issue and report it upstream

00:21 <tuxd3v> I succeded once in going that far, but never more

00:22 <tuxd3v> until I gave up that time tried

00:22 <tuxd3v> So I never managed to pass that faze and majority of time I don't even see that faze

00:23 <tuxd3v> faze -> phase

00:23 <tuxd3v> nice you succeded :)

00:24 <tuxd3v> yeah I tried with atf mainline and uboot 2020.04-rc3 I think

00:28 <vagrantc> since i have a good point 2020.01 to bisect from ... annoying though it may be ... i'd like to get it fixed

00:42 <vagrantc> huh. i wonder if the issue breaking u-boot MMC on rockpro64 is the same as breaking MMC on pinebook-pro with mainline u-boot

00:42 <vagrantc> they're fairly similar platforms ....

00:50 <tuxd3v> it could be

21:11 <vagrantc> so apparently, my issues with rockpro64 not able to get past SPL (hanging on trying MMC) ... might be toolchain or optimization flags issues

21:18 <vagrantc> and there are apparently two models of rockpro64-rk3399 ? v2.1 and v2.0 ...

21:19 <vagrantc> which have confusingly named .dts files ...

21:19 <vagrantc> rk3399-rockpro64.dts: model = "Pine64 RockPro64 v2.1";

21:19 <vagrantc> rk3399-rockpro64-v2.dts: model = "Pine64 RockPro64 v2.0";

21:20 <vagrantc> why they didn't call -v2 -v2.0 is beyond me

21:20 <vagrantc> i could see the first model supported happening to be v2.1, sure

21:21 <vagrantc> and then not wanting to change the device-tree to break compatibility