Igor

> testing before merging. For CSC, that is not possible. We don't have time nor hardware. The only way to allow "anything" is establishing "community supported section". Which switches this...

> PR acceptance criteria could be tightened True, some additional guidance can help a bit on a long run. Feel free to improve the text: https://docs.armbian.com/User-Guide_Board-Support-Rules/ https://github.com/armbian/build/blob/main/.github/PULL_REQUEST_TEMPLATE.md (perhaps some parts...

> and the power connector is an unusual 1.7mm x 4.75mm or so. I can sent you some of these if you want - have lots of cables and PSUs...

`config/bootscripts/boot-rockchip64-ttyS4.cmd` Also dedicated bootloader script just for this board is not acceptable. We already have a maintaining nightmare and @djurny is trying to come out with some generic solution. Perhaps...

Can you also try to switch CURRENT to 6.12.y, which is going to be LTS?

> iMHO, it would be best to first switch edge to 6.12 so that 6.12 gets some testing on it. Then move legacy to 6.6, current to 6.12 and edge...

This should go straight to 6.16.y if you can adjust it?

> It feels like sketchy behaviour Indeed. This is known dirty workaround, but have to scratch my head to understand why we had to use this. IIRC it was due...

This must be similar issues as "compile" action. Works for me :)

For info: we are developing this part - userspace assembly, initially for desktops - from scratch: https://github.com/armbian/apa But it is in early stages. This should resolve some of such troubles.