<tllim>
@ayufun, try 0.6.41 stil few R64 board cannot boot up, even one board with SPi boot
<tllim>
sorry, wrong IRC channel
Easyfab has quit [Quit: Leaving]
anarsoul|3 has joined #linux-rockchip
anarsoul|2 has quit [Ping timeout: 264 seconds]
<vagrantc>
beeble: i'm noticing that mainline u-boot sets fdtfile to rockchip/rk3399-puma-ddr1600.dtb but in mainline linux it's called rockchip/rk3399-puma-haikou.dtb
<beeble>
vagrantc: thought it would be rk3399-puma.dtb in uboot. that's something left because uboot support was first and for linux the files where splitted. will be changed in the next dts sync (waited for the spdx changes to do a fresh import)
<vagrantc>
beeble: so it will get changed in u-boot ?
<beeble>
maybe i can get it into this cycle, shouldn't be that big of a problem
<beeble>
yes
<beeble>
so the names match with mainline
<beeble>
have only to think about a migration plan for the 4.4 tree
lkcl has joined #linux-rockchip
<vagrantc>
beeble: so in the end, it will be rk3399-puma-haiku.dtb ?
<vagrantc>
beeble: just wondering so i could probably patch 2016.05 for debian to match linux
<vagrantc>
er, 2018.05 :)
<beeble>
thats my plan. will have to talk to philipp again since he have to merge it :)
<beeble>
so if you maybe can wait till tomorrow for an answer and maybe a patchset that is cherry pickable shortly after
<vagrantc>
beeble: cool
LargePrime has quit [Ping timeout: 260 seconds]
<beeble>
and hopefully a patch that will correctly do autoselect of the correct device for distroboot
<vagrantc>
yeah ... i'm guessing right now it just grabs CONFIG_DEFAULT_DEVICE_TREE or something?
* vagrantc
still needs to figure out what broke firefly-rk3399
<beeble>
yes and that config was developed independent from linux
<beeble>
wasn't an issue yet as it got overwritten by boot.scr. but you are probably doing it the extlinux.conf way right?
<vagrantc>
i've been using extlinux ... but if i were using debian's flash-kernel generated boot.scr it would have the same issue
<vagrantc>
i forget if i tested EFI support or not
<beeble>
so getting the correct filename from u-boot is definitly the right way to go
<beeble>
i still haven't tried efi yet. still on my todo to figure that out