diff options
| author | Waldemar Brodkorb <wbx@openadk.org> | 2016-03-05 12:51:42 +0100 |
|---|---|---|
| committer | Waldemar Brodkorb <wbx@openadk.org> | 2016-03-07 06:42:57 +0100 |
| commit | c384dc577bd32f3315bacb410fc31610b41f742c (patch) | |
| tree | 903aaed00f4b82d5e1eada2bd4fea8a7f3387ded /docs | |
| parent | 68d4e79f35039b31ae835e82241a567b0ad66aa8 (diff) | |
rework menu based config system
After the addition of bare metal toolchains the menu system allowed
to create non-valid configurations. I reworked it so we can also
add other operating system support if we wish.
So first you choose your operating system, then your architecture
and endianess, after that your embedded system, emulator or
generic device and then you choose your task you want to run.
Tasks may be toolchain, a new appliance/application or some preconfigured
sets of packages and configurations as kodi, mpd, firefox and more.
The tasks are limited to a plausible choice of hardware and software.
Deduplicate CPU configuration.
You don't wanna compile Kodi for a H8/300 microcontroller ;)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/adding-boards.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/adding-boards.txt b/docs/adding-boards.txt index 4066fd822..4f18dbc08 100644 --- a/docs/adding-boards.txt +++ b/docs/adding-boards.txt @@ -16,8 +16,8 @@ target/arm/systems/raspberry-pi2 --------------------- config ADK_TARGET_SYSTEM_RASPBERRY_PI2 bool "Raspberry PI 2" - select ADK_CPU_CORTEX_A7 - select ADK_TARGET_LITTLE_ENDIAN + depends on ADK_TARGET_LITTLE_ENDIAN + select ADK_TARGET_CPU_ARM_CORTEX_A7 select ADK_TARGET_CPU_WITH_NEON select ADK_TARGET_BOARD_BCM28XX select ADK_TARGET_WITH_VGA @@ -44,10 +44,10 @@ in OpenADK, you need to port it first. The hardware capabilities are optional. (f.e. ADK_TARGET_WITH_SD), but required when you configure the driver configuration later. -For architectures with a choice for endianess you should select either +For architectures with a choice for endianess you should depends on either ADK_TARGET_LITTLE_ENDIAN or ADK_TARGET_BIG_ENDIAN. -If the CPU type like in this example ADK_CPU_CORTEX_A7 is not yet available +If the CPU type like in this example ADK_TARGET_CPU_ARM_CORTEX_A7 is not yet available you need to add it to target/config/Config.in.cpu. For optimized code generation you should also add ADK_TARGET_GCC_CPU or ADK_TARGET_GCC_ARCH symbol for your CPU type. Furthermore you need to decide if your CPU has a MMU, FPU and NPTL support |