* DFI driver fix to let DDR3 rk322x handle DMC driver
* edge kernel: removal for Gigabit Ethernet DMA
workaround for rk3288
* reinstate CONFIG_DEBUG_FS=y with both current/edge kernels
Switch to NO_HZ_IDLE for energy saving. Also enable Menu cpuidle
governor for tickless systems.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Signed-off-by: Igor Pecovnik <igor@armbian.com>
- having CONFIG_DUMMY=y causes a fake/dummy interface `dummy0` to be
_always_ present
- that in turn can confuse things like cloud-init in nocloud-net mode
- changing it to module, it can still be used (just modprobe)
- I found this using `linux-rk35xx-vendor`, but I reason it applies to
all kernels; most other kernels already have it `=m`
A couple of these configs have gotten out of sync with is making it
difficult for the automation scripting to properly re-write these
configs correctly. Mostly due to the "edge" kernel being updated
to the latest v6.18 kernel, but also due to the RT config not being
updated in some time. Manually update these configs and check for
correctness.
Signed-off-by: Andrew Davis <afd@ti.com>
The "current" and "edge" branches point to the same kernel and u-boot.
No need to have both so just remove "edge" as it was not any more
up-to-date than the standard "current" branch.
Signed-off-by: Andrew Davis <afd@ti.com>
- `=m` is not a valid value for options that are `bool`
- so change them to `=y` manually
- from olddefconfig:
- `.config:82:warning: symbol value 'm' invalid for BT_RFCOMM_TTY`
- `.config:84:warning: symbol value 'm' invalid for BT_BNEP_MC_FILTER`
- `.config:85:warning: symbol value 'm' invalid for BT_BNEP_PROTO_FILTER`
- `.config:87:warning: symbol value 'm' invalid for BT_HS`
- `.config:89:warning: symbol value 'm' invalid for BT_LEDS`
- `.config:90:warning: symbol value 'm' invalid for BT_MSFTEXT`
- `.config:92:warning: symbol value 'm' invalid for BT_HCIBTUSB_AUTOSUSPEND`
- `.config:93:warning: symbol value 'm' invalid for BT_HCIBTUSB_MTK`
- `.config:96:warning: symbol value 'm' invalid for BT_HCIUART_BCSP`
- `.config:97:warning: symbol value 'm' invalid for BT_HCIUART_ATH3K`
- `.config:99:warning: symbol value 'm' invalid for BT_HCIUART_BCM`
- `.config💯warning: symbol value 'm' invalid for BT_HCIUART_RTL`
- `.config:101:warning: symbol value 'm' invalid for BT_HCIUART_QCA`
- `.config:102:warning: symbol value 'm' invalid for BT_HCIUART_AG6XX`
- `.config:250:warning: symbol value 'm' invalid for AIC_WLAN_SUPPORT`
- this is to workaround e3ec97c3ab
- I talked to the maintainer (Wei Liu) upstream, they are aware of the problem, but haven't a solution
- the cloud variants are not affected (already had =y)
eMMC installs on the A20-OLinuXino-LIME2 eMMC hang during boot.
This is because we need the eMMC power sequencing module in early boot.
Compile it in to the kernel so we can boot from eMMC again.
* Wireless driver patching: fix inconsistency in matching
Mathing Allwinner family via LINUXFAMILY is giving different results. sunxi doesn't cover sun5* ...
* Re-adding wireless drivers that fall out of this bug + few additional
