[PATCH] gemini: Bump to kernel v5.10

Christian Lamparter chunkeey at gmail.com
Mon Apr 12 19:32:39 BST 2021


On 12/04/2021 00:11, Linus Walleij wrote:
> Only two patches against mainline remains. Switch to v5.10
> which works very nicely with all Gemini devices.
> 
> Signed-off-by: Linus Walleij <linus.walleij at linaro.org>
> ---
>   target/linux/gemini/Makefile                  |   2 +-
>   target/linux/gemini/config-5.10               | 465 ++++++++++++++++++
>   ...t-fotg2-add-Gemini-specific-handling.patch | 131 +++++
>   ...-DIR-685-partition-table-for-OpenWrt.patch |  37 ++
>   4 files changed, 634 insertions(+), 1 deletion(-)
>   create mode 100644 target/linux/gemini/config-5.10
>   create mode 100644 target/linux/gemini/patches-5.10/0001-usb-host-fotg2-add-Gemini-specific-handling.patch
>   create mode 100644 target/linux/gemini/patches-5.10/0002-ARM-dts-Augment-DIR-685-partition-table-for-OpenWrt.patch
> 
> diff --git a/target/linux/gemini/Makefile b/target/linux/gemini/Makefile
> index d2acb52facf7..95a5a87eaa4d 100644
> --- a/target/linux/gemini/Makefile
> +++ b/target/linux/gemini/Makefile
> @@ -10,7 +10,7 @@ BOARDNAME:=Cortina Systems CS351x
>   FEATURES:=squashfs pci rtc usb dt gpio display ext4 rootfs-part boot-part
>   CPU_TYPE:=fa526
>   
> -KERNEL_PATCHVER:=5.4
> +KERNEL_PATCHVER:=5.10

Hmm, when building this with the BUILDBOT config (CONFIG_BUILDBOT)
and throw in the CONFIG_ALL_* for userspace + kernel modules for
good measure. It fails with the default world build (without the
V=s option) because the following symbols are not yet defined in
either the generic or gemini-specific kernel config.

CONFIG_COMPAT_32BIT_TIME
CONFIG_PCIEASPM
CONFIG_MTD_PHYSMAP_IXP4XX
CONFIG_GPIO_CDEV_V1
CONFIG_CPU_THERMAL
CONFIG_DMA_PERNUMA_CMA

At least CPU_THERMAL is also a show-stopper for apm82181 5.10,
so should these just be added added as either disabled
(# CONFIG_ ... is not set) or in case of CONFIG_PCIEASPM=X
(whatever the default is there) in target/linux/generic/config-5.10?

Or CPU_THERMAL could be an issue for some high-powered x86 or ARM?

Cheers,
Christian



More information about the openwrt-devel mailing list