diff options
author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-08-27 16:10:38 +0200 |
---|---|---|
committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-08-27 16:36:18 +0200 |
commit | 6e936591f0737d4e5735973807aa9f088fc49927 (patch) | |
tree | c9aae08f413aebd5ce937ba124a085dd1315ed4e | |
parent | bc19481826e0da9119945eaae4f25736306f023b (diff) | |
download | upstream-6e936591f0737d4e5735973807aa9f088fc49927.tar.gz upstream-6e936591f0737d4e5735973807aa9f088fc49927.tar.bz2 upstream-6e936591f0737d4e5735973807aa9f088fc49927.zip |
at91: explicitly set CONFIG_USB_SUPPORT for sam9x subtarget
The at91 target sets
FEATURES:=usb usbgadget ...
in the target Makefile, which sets CONFIG_USB_SUPPORT=y in the
.config file for both subtargets.
However, when building with all kmods, the build fails with the
following error message:
ERROR: module [...]/drivers/bluetooth/btusb.ko is missing.
It appears that only a part of the bluetooth files are compiled.
The package depends @USB_SUPPORT.
This can be easily healed by adding CONFIG_USB_SUPPORT=y to the
sam9x subtarget configuration. Before the 4.14->5.4 bump, the
same was also set in the target's config-4.14 file along with
several other USB config options that are not reimplemented.
Still, it remains a mystery to me why setting the same symbol
via target kernel config creates a different result than the
feature setting the same symbol in target-metadata.pl.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
-rw-r--r-- | target/linux/at91/sam9x/config-default | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/target/linux/at91/sam9x/config-default b/target/linux/at91/sam9x/config-default index 43e2a02dd9..a05831fe17 100644 --- a/target/linux/at91/sam9x/config-default +++ b/target/linux/at91/sam9x/config-default @@ -181,6 +181,7 @@ CONFIG_TIMER_PROBE=y CONFIG_TINY_SRCU=y CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h" CONFIG_UNWINDER_ARM=y +CONFIG_USB_SUPPORT=y CONFIG_USE_OF=y # CONFIG_VFP is not set CONFIG_ZBOOT_ROM_BSS=0x0 |