mt7623: Bump legacy 4.19 to current 6.6 kernel

[ColorfulRhino]

Description

The mt7623 family only has one board (BananaPi R2) and has not been properly maintained in many years. Instead of fully removing the family, bump the kernel to 'current' 6.6 since the SoC and also the BananaPi R2 is mainlined and shouldn't cause too many troubles.
No need for 'edge' kernel unless someone plans to step in as maintainer who bumps and tests it on every new kernel release.

Please note: I do not own the hardware. Inspiration for changes were made from this 1.5 years old PR: #4873

---

By the way, when this is done, there will be no 4.x kernels anymore 🎉
(5.x I'm coming for you soon™ as well 😈)

---

GitHub issue reference: #6821
Jira reference number AR-2392

How Has This Been Tested?

• ./compile.sh BOARD=bananapir2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie
• ./compile.sh BOARD=bananapir2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[rpardini]

Nice. Please, move the main-config.sh change to a separate PR? It's impact is far beyond the bumping of a kernel.

[rpardini]

• Add armhf support to Trixie (was this disabled for a specific reason? If so, please let me know. It builds fine though)

It used to be broken upstream, Igor (AFAIK) disabled it and we forgot?

[rpardini]

cpufrequtils: if it is still available on some release, it won't be for long. Suggest this is left alone

[ColorfulRhino]

Nice. Please, move the main-config.sh change to a separate PR? It's impact is far beyond the bumping of a kernel.

Agreed. I have included it in this PR though since the family config needs to make use of it:

build/config/sources/families/mt7623.conf

Line 33 in a52ca59

declare -g NETWORKING_STACK="systemd-networkd" # Always use systemd-networkd since 'family_tweaks()' includes some network config that currently is only available for networkd; @TODO Change this config to Netplan config

I can add it to a separate PR though no problem 👍

It would be nice to be able to set this after post_family_config hook so that boards can set this variable in their config as well (or can they already? Not sure when board config is loaded), but that didn't work since extension manager is then initialized already.

It used to be broken upstream, Igor (AFAIK) disabled it and we forgot?

Ah I see. I guess it's fine now? At least my image built with Trixie and I couldn't find any package related warnings or errors scrolling through the build log.

cpufrequtils: if it is still available on some release, it won't be for long. Suggest this is left alone

The effect is still the same, cpufrequtils is only removed if release Trixie or Arch riscv. I have only converted the denylist (remove on x) to an allowlist (don't remove on a,b,c,d) in order to allow for easy maintenance (can be left alone for ages, new releases automatically have cpufrequtils removed without needing to change anything).
Is your opinion still the same after the explanation? 😄

[ColorfulRhino]

Nice. Please, move the main-config.sh change to a separate PR? It's impact is far beyond the bumping of a kernel.

Dropped 4 commits from this PR, moved 3 of them over to #6911

Completely dropped cpufrequtils

[adeepn]

build ok. commit and let's go fix this later :)