summaryrefslogtreecommitdiffstats
path: root/drivers/net/wan/Kconfig
diff options
context:
space:
mode:
authorMasahiro Yamada <masahiroy@kernel.org>2020-03-26 14:57:15 +0900
committerMasahiro Yamada <masahiroy@kernel.org>2020-03-29 22:37:53 +0900
commit63b903dfebdea92aa92ad337d8451a6fbfeabf9d (patch)
tree18a4f8ea2c78c5e719699ba757d58a1190ecece6 /drivers/net/wan/Kconfig
parentf463c3510d44ab11da607d7c3b289f90ea467d1b (diff)
downloadlinux-63b903dfebdea92aa92ad337d8451a6fbfeabf9d.tar.bz2
net: wan: wanxl: use allow to pass CROSS_COMPILE_M68k for rebuilding firmware
As far as I understood from the Kconfig help text, this build rule is used to rebuild the driver firmware, which runs on an old m68k-based chip. So, you need m68k tools for the firmware rebuild. wanxl.c is a PCI driver, but CONFIG_M68K does not select CONFIG_HAVE_PCI. So, you cannot enable CONFIG_WANXL_BUILD_FIRMWARE for ARCH=m68k. In other words, ifeq ($(ARCH),m68k) is false here. I am keeping the dead code for now, but rebuilding the firmware requires 'as68k' and 'ld68k', which I do not have in hand. Instead, the kernel.org m68k GCC [1] successfully built it. Allowing a user to pass in CROSS_COMPILE_M68K= is handier. [1] https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/9.2.0/x86_64-gcc-9.2.0-nolibc-m68k-linux.tar.xz Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'drivers/net/wan/Kconfig')
-rw-r--r--drivers/net/wan/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/wan/Kconfig b/drivers/net/wan/Kconfig
index 4530840e15ef..dbc0e3f7a3e2 100644
--- a/drivers/net/wan/Kconfig
+++ b/drivers/net/wan/Kconfig
@@ -200,7 +200,7 @@ config WANXL_BUILD_FIRMWARE
depends on WANXL && !PREVENT_FIRMWARE_BUILD
help
Allows you to rebuild firmware run by the QUICC processor.
- It requires as68k, ld68k and hexdump programs.
+ It requires m68k toolchains and hexdump programs.
You should never need this option, say N.