From dbfdeaeb46453d300b975dcfb6790f3b16f9e6b5 Mon Sep 17 00:00:00 2001 From: Waldemar Brodkorb Date: Fri, 26 Nov 2010 15:18:01 +0100 Subject: implement the concept of target choice by embedded system or architecture you can now choose between specific embedded systems like PC Engines ALIX boards, Foxboard, .. or between generic architecture support like x86, x86_64, mips, ... This does reduce the overhead of duplicate configuration files in target directory. Now qemu, toolchain and ibm x40 support is combined in one target directory target/x86. Distinguishing between hardware profiles happens via menu based configuration. (CPU choice for kernel, CFLAGS for package building, ..). We will see if this is the right direction. --- target/Config.in.mips64 | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 target/Config.in.mips64 (limited to 'target/Config.in.mips64') diff --git a/target/Config.in.mips64 b/target/Config.in.mips64 new file mode 100644 index 000000000..1dc8061e5 --- /dev/null +++ b/target/Config.in.mips64 @@ -0,0 +1,17 @@ +choice +depends on ADK_LINUX_MIPS64 +prompt "Hardware model" + +config ADK_HARDWARE_GENERIC_MIPS64 + bool "Generic mips64 system" + help + Generic mips64 system. + +config ADK_HARDWARE_GENERIC_MIPS64_TOOLCHAIN + bool "mips64 toolchain" + select ADK_TOOLCHAIN_ONLY + help + mips64 toolchain. + +endchoice + -- cgit v1.2.3