* the existing patches for rk3308 audio codec have been disabled:
the rk3308 driver has been mainlined and thus the patches
don't apply anymore
* add the missing i2s_8ch_0 and _1 i2s nodes
* adjust "acodec" with "codec" device tree labels, to match
mainline kernel nomenclature
Legacy: use TAG instead of BRANCH (gives us more control)
Current: update DTS files
Current: add needed patches up to v1.0.8
Fixup bluetooth node and disable by default (half broke anyway)
Misc fixups to bananapif3.wip and spacemit.conf file
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
Reverse commit 75317a0 since this is a special case.
Eliminate the real reason for the inability to boot the kernel.
Linux kernel hangs in early boot on 32-bit ARM platform,
when ftrace 4-byte "mcount" function call location for
"_raw_spin_unlock_irqrestore" function straddles icache lines.
The problem is present for (cross-compiler) GCC 10, 11, 12.
It does not happen when the kernel is compiled with GCC 9,
even when condition (1) is satisfied.
Detailed description:
https://forum.armbian.com/topic/41339-linux-image-legacy-sunxi2451-kernel-6192-is-broken-stuck-at-starting-kernel/?do=findComment&comment=196528
- **win**: notice how one can actually _spot_ revelevant changes now
- case in point, `1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch` -- will drop it in separate commit
NB: This family only has one board (BananaPi R2) and has not been properly maintained in many years, so 'current' LTS kernel is enough.
No need for 'edge' kernel unless someone plans to step in as maintainer who bumps and tests it on every new kernel release.
- Adjust BananaPi R2 board config (board is mainlined)
- Remove legacy kernel patch folder and kernel config
- Remove unstable WiFi stuff
* To modify the PWM-fan temperature control policy of fine3399 to adjust the fan speed to a lower level
* Integrating support for xiaobaonas boards into the rockchip64-6.9 kernel
Revert 07b37f227c8daa27e68f57b1c691fab34a06731e commit
For the sunxi (armhf) architecture, this commit results in
an inability to load the kernel. It's actually a crutch
that can break everything tomorrow.
Therefore, freeze the kernel version for better times.
