Adding / Modifying Boards - What is the right approach?

[Daniel Andersen]

I am working on a new version of the Luckfox Core3566 Board and Patches, as well as adding the Orange PI CM4 board to Armbian. Both rely on the Rockchip RK3566. 

Luckfox Core3566

Starting with the Core3566: The current board is just the vendor u-boot and kernel. It lacks PCIe support, but surely it is helpful to be as near to manufacturer configuration in their patches. My board config on the other side is not supporting the vendor specific patches, but based on a clean u-boot v2025.10 and runs nicely with current and edge kernels and also runs smoothly with nvme storage. 

The luckfox-core3566 config is currently maintainerless, but maybe users would like to have this vendor kernel version. 

 

My question: 
1) Would the Armbian rather like to replace the vendor board config with a more future proof board config like mine  

or

2) Keep both board versions ( like rename config/boards/luckfox-core3566.csc to config/boards/luckfox-core3566_vendor.csc ) and let my variant replace the config/boards/luckfox-core3566.csc as default? 

 

3)rd option would be combine both configs, but I had struggle to do so, as my version is using a different u-boot, using a simplified partition setup etc. 

Orange Pi cm4 

I created a new board configuration to let Orange PI CM4 to work with Armbian as well. It is pretty similar to the bigtreetech cb2, but it's ethernet wiring and pcie powering device config differs from latter.  
Is it okay to create a MR directly in Github or does it need alignment with Moderators first? 

 

Cheers,

Daniel 

 

PS: Nice to have time to work on embedded arm systems again. I did work on the sunxi based cubieboard and cubietruck back in the days, but job, family and basically life pulled me away from it for such a long time. 

 

Edited 54 minutes ago by Daniel Andersen