[Task / Story]: Clean up old kernels/kernel patch leftovers

[ColorfulRhino]

Task description

This is part of #6820

The goal is to remove

1. deprecated/unused kernels from the code
2. kernel patch folder of kernels which are not used anymore (just forgotten to delete in the past)

Please add leftovers if you know of any. Feel free to discuss and improve :)
Please correct me if I do wrong assumptions. I am not familiar with all the families.

Remove kernel patch folders of unused kernels:

• rockchip-4.4 [Cleanup] Remove some leftover kernel patch folders #6831
• rockchip-5.10 [Cleanup] Remove some leftover kernel patch folders #6831
• rockchip-5.15 [Cleanup] Remove some leftover kernel patch folders #6831
• rockchip-6.1 [Cleanup] Remove some leftover kernel patch folders #6831
• rockchip64-6.1 [Cleanup] Remove some leftover kernel patch folders #6831
• meson64-5.10 [Cleanup] Remove some leftover kernel patch folders #6831

Remove unused kernels:

• rk322x: [Cleanup] Remove leftovers of former BOARDFAMILY rk322x (now integrated into the rockchip family) #6832
• Abandoned media kernel: Integrate media boards into the rockchip64 family #6834
• Remove OrangepiZero2 heavily outdated legacy kernel #6854
• [Task]: Deprecate rk3588-legacy in favor of rk3588-vendor #6835
• s5p6818 is unmaintained and stuck on ancient Linux 4.14: Purge s5p6818 board family #6869
• rockpi-s: Remove legacy kernel 4.4 support #6879
• mt7623: Bump legacy 4.19 to current 6.6 kernel #6902

[github-actions]

Jira ticket: AR-2392

[rpardini]

Nice initiative. I guess it's time to let those go. (I was personally attached to 5.10 meson64 as it took years for 6.x to reach the same level).

[igorpecovnik]

What's up with s5p6818? It's stuck on ancient Linux 4.14

Yes, unfortunately and u-boot is not build-able anymore. Full remove?

[ColorfulRhino]

Yes, unfortunately and u-boot is not build-able anymore. Full remove?

I was first thinking keeping it is better since this family has no other kernel than legacy. But the family has not seen any meaningful activity in 4 years and there are only 4 boards using this family (all NanoPi/NanoPC), without any maintainer.

So after seeing this information, I vote for dropping. especially if it doesn't even build.

I guess in that case we remove the boards as well? They're all just 9 lines of code, nothing worth keeping even in case someone wants to bring this back with an update.

Edit: Also there's mt7623 which has only legacy 4.19 kernel (no current or edge) and is only used for one board without a maintainer. What to do with that?

[ColorfulRhino]

Also I've discovered that the kernel family rockpis (which is only used by 1 board) is still on even more ancient Linux 4.4.
How should we proceed with that one? The board config doesn't even enable legacy so it's just dead code.

As proposed in the forums, it could simply be integrated into rockchip64: https://forum.armbian.com/topic/32916-ideas-on-how-to-make-soc-family-patches-more-manageable/
So the family is fully integrated.

@brentr would you like to do this yourself and move stuff from the family config that is still relevant?

For setting a fixed MAC we have also this btw, maybe it can help:

build/packages/bsp/common/usr/lib/armbian/armbian-common

Line 38 in ffe83ab

set_fixed_mac ()