martinayotte

It is there on the commit I did on Friday ... I'm currently running 5.0.y from the eMMC ... Oh ! you're right ! I've the eMMC still on 4.20.y ... I must have forgotten some thing ... Now checking !

Right ! Only 3 small commits :
https://github.com/janwillies/u-boot/commits/v2019.01-sopine-spi
 

Just thinking about the task, it remind be all my struggling between the 2 boot mode of Rockchip back in early December :
https://github.com/armbian/build/commit/c3e46a5d863ebc4d00d666b3a19eed00e3d0c17d#diff-ee77e238b43dce4af9e9f0b7d3f9978a
 
Personally, I like more this single u-boot binary using this method #2 !
 
I will see if that can be generalized on every Rockchip ...

Just after you have choosen rock64 board from the dialog, next dialog should show "default" or "dev" branch ...
 

Almost all H6 boards have problem with "reboot" command, we din't find solution yet, we need to re-cycle power to reboot.

Yes, it can be done ... Look at <kerneldir>/kernel/reboot.c
 
But we need to actually find the real issue in U-boot ...
 

WiFi is working on OPi3, but you need to manually tweak the firmware and reboot :
mv /lib/firmware/brcm/brcmfmac43455-sdio.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac43455-sdio.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt-ORIG cp /lib/firmware/rkwifi/fw_bcm43456c5_ag.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin cp /lib/firmware/rkwifi/nvram_ap6256.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt  

The error is rather this one :
net/wireguard/ratelimiter.c:60:2: error: implicit declaration of function ‘call_rcu’; did you mean ‘call_srcu’? [-Werror=implicit-function-declaration] call_rcu(&entry->rcu, entry_free); ^~~~~~~~ call_srcu cc1: some warnings being treated as errors You can try to add at command line "WIREGUARD=no" , it will skip this part of the build ...

Since 5.0.y is now committed, I'm now going back to the task of getting rid of this old U-Boot SPL 2017.09-armbian ...

During all my board migrations under 5.0.y, I've seen that copying OS into eMMC using "nand-sata-install", it now much faster !!!
I don't know if it 5.0.y related or if some tweaks have been done to "nand-sata-install", but time shrink from 20minutes to 4 or 5minutes...

The tour was successful ... So, the commit is now done !
 
I'm now going back to the task of getting rid of old U-Boot SPL 2017.09-armbian ...

During all my board migrations under 5.0.y, I've seen that copying OS into eMMC using "nand-sata-install", it now much faster !!!
I don't know if it 5.0.y related or if some tweaks have been done to "nand-sata-install", but time shrink from 20minutes to 4 or 5minutes...

RockPi-4B was simply copied from RockPro64 as a template.
I was thinking the reverse, and started exploring half hour to try Mainline U-Boot v2019.01 working with RockPro64, but it doesn't seem to be trivial for now (defconfig issues).
I will investigate more later ... For now, my task is to have 5.0.y on all my RK3399 boards : RockPro64 is done, now testing OrangePi-RK3399, next will be my NanoPCT4 and RockPi-4B ...
 

I've started looking at switching Rockchip64-DEV to 5.0.y ... I've now my RockPro64 under 5.0.y ...
It look much more easier task than the previous one with Sunxi-DEV !
 
@Igor , I've pushed a "rockchip64-4.20" tag that will allow to bring 4.20.y into NEXT if we wish ...
 
Also, is there any reason why RockPro64 still using U-Boot SPL 2017.09-armbian (from Ayufan's branch) instead of Mainline U-Boot such v2019.01 ?
If No, I will switch that too ...
 

Right ! Those are Ok !
That one of the reason there is no hurry to fix memory-leak issue, since I'm probably the only one who is using "dynamic" userspace method ...

I've committed the initial stuff !
Now, I will pursue the patch cleaning ...
Let me know if you are unable to build 5.0.y on some Allwinner boards ...

I've committed the initial stuff !
Now, I will pursue the patch cleaning ...
Let me know if you are unable to build 5.0.y on some Allwinner boards ...

I've done several local builds with success, although some patches are still failing, they don't prevent doing a build.
I will push preliminary stuff soon ...

Thanks ! Good to know !
Since I'm preparing Armbian-DEV to switch to 5.0.y, I've simply added it to OPiLite2 and OPiOne+, and it works (at least in plain text console) !
 

Thanks ! Good to know !
Since I'm preparing Armbian-DEV to switch to 5.0.y, I've simply added it to OPiLite2 and OPiOne+, and it works (at least in plain text console) !
 

Thanks ! Good to know !
Since I'm preparing Armbian-DEV to switch to 5.0.y, I've simply added it to OPiLite2 and OPiOne+, and it works (at least in plain text console) !
 

Right ! ... and it will soon be on 5.0.y ...

That is because it is your first build.
Redoing almost the same build later, it can take less than 30 mins, thanks to "ccache" ...

Ok ! Since switching U-Boot is a less painful task than kernel itself, maybe we can switch sooner !
I will try this afternoon ...

Armbian has now the new OrangePi3 WIP !
WiFi and eMMC tested ...