From c6d478cce58f26be1a25fc5c09f31a7c23b9845b Mon Sep 17 00:00:00 2001 From: Christian Breunig Date: Thu, 1 Oct 2026 18:23:56 +0200 Subject: Kernel: T9014: build WWAN drivers in on arm64, completing T8938 T8938 consolidated the WWAN build time options into config/12-wwan.config and requested the USB WWAN drivers as built-in. That only ever took effect on amd64. On arm64 all of them silently ended up as modules, because a tristate can never exceed the value of what it depends on and the arm64 base config had USB_USBNET=m and USB_SERIAL=m, while amd64 had both =y. Pull the two parents into the snippet so the requested =y is reachable on every architecture - this is a no-op on amd64 where they were already =y. --- scripts/package-build/linux-kernel/config/12-wwan.config | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'scripts') diff --git a/scripts/package-build/linux-kernel/config/12-wwan.config b/scripts/package-build/linux-kernel/config/12-wwan.config index c989376b..1e3280ac 100644 --- a/scripts/package-build/linux-kernel/config/12-wwan.config +++ b/scripts/package-build/linux-kernel/config/12-wwan.config @@ -8,7 +8,18 @@ CONFIG_IOSM=m CONFIG_MTK_T7XX=m # end of Wireless WAN -CONFIG_USB_SERIAL_WWAN=y +# The USB WWAN drivers below are requested as built-in, so their parent +# symbols must be built-in too - a tristate can never exceed the value of +# what it depends on. amd64 already had both =y, arm64 only had =m which +# silently demoted every driver in this snippet to a module. +CONFIG_USB_USBNET=y +CONFIG_USB_SERIAL=y + +# USB_SERIAL_WWAN has no prompt - it is only ever reached via select, +# so it has to be pulled in by building its users in. amd64 already did this, +# arm64 had them as modules and therefore got USB_SERIAL_WWAN=m. +CONFIG_USB_SERIAL_QUALCOMM=y +CONFIG_USB_SERIAL_SIERRAWIRELESS=y CONFIG_USB_NET_CDCETHER=y CONFIG_USB_NET_CDC_EEM=y CONFIG_USB_NET_CDC_NCM=y -- cgit v1.2.3