config/target.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Oct 12 11:22:46 2008 +0000 (2008-10-12)
changeset 920 44dd635202a4
parent 854 f347a40db591
child 1038 33f695f7773a
permissions -rw-r--r--
In generated choice menus, move the selection options outside the choice menu.

/trunk/kconfig/kconfig.mk | 60 35 25 0 +++++++++++++++++++++++++++++++----------------------
/trunk/config/kernel.in | 6 0 6 0 -----
/trunk/config/target.in | 6 0 6 0 -----
3 files changed, 35 insertions(+), 37 deletions(-)
yann@1
     1
# Target definition: architecture, optimisations, etc...
yann@1
     2
yann@1
     3
menu "Target options"
yann@1
     4
yann@47
     5
config ARCH
yann@47
     6
    string
yann@628
     7
yann@628
     8
# Pre-declare target optimisation variables
yann@631
     9
config ARCH_SUPPORT_ARCH
yann@631
    10
config ARCH_SUPPORT_ABI
yann@631
    11
config ARCH_SUPPORT_CPU
yann@631
    12
config ARCH_SUPPORT_TUNE
yann@631
    13
config ARCH_SUPPORT_FPU
yann@628
    14
config ARCH_SUPPORTS_BOTH_ENDIAN
yann@628
    15
config ARCH_DEFAULT_BE
yann@628
    16
config ARCH_DEFAULT_LE
yann@633
    17
config ARCH_ARCH
yann@633
    18
config ARCH_ABI
yann@633
    19
config ARCH_CPU
yann@633
    20
config ARCH_TUNE
yann@633
    21
config ARCH_FPU
yann@633
    22
config ARCH_BE
yann@633
    23
config ARCH_LE
yann@628
    24
config ARCH_FLOAT_HW
yann@628
    25
config ARCH_FLOAT_SW
yann@628
    26
config TARGET_CFLAGS
yann@791
    27
config TARGET_LDFLAGS
yann@628
    28
yann@628
    29
comment "General target options"
yann@47
    30
yann@628
    31
source config.gen/arch.in
yann@1
    32
yann@136
    33
config ARCH_SUPPORTS_BOTH_ENDIAN
yann@35
    34
    bool
yann@35
    35
    default n
yann@35
    36
yann@347
    37
config ARCH_DEFAULT_BE
yann@347
    38
    bool
yann@347
    39
    default n
yann@347
    40
yann@347
    41
config ARCH_DEFAULT_LE
yann@347
    42
    bool
yann@347
    43
    default n
yann@347
    44
yann@1
    45
choice
yann@1
    46
    bool
yann@1
    47
    prompt "Endianness:"
yann@136
    48
    depends on ARCH_SUPPORTS_BOTH_ENDIAN
yann@347
    49
    default ARCH_BE if ARCH_DEFAULT_BE
yann@347
    50
    default ARCH_LE if ARCH_DEFAULT_LE
yann@1
    51
yann@1
    52
config ARCH_BE
yann@1
    53
    bool
yann@1
    54
    prompt "Big endian"
yann@1
    55
yann@1
    56
config ARCH_LE
yann@1
    57
    bool
yann@1
    58
    prompt "Little endian"
yann@1
    59
yann@1
    60
endchoice
yann@1
    61
yann@1
    62
comment "Target optimisations"
yann@1
    63
yann@631
    64
config ARCH_SUPPORT_ARCH
yann@631
    65
    bool
yann@631
    66
    default n
yann@631
    67
yann@631
    68
config ARCH_SUPPORT_ABI
yann@631
    69
    bool
yann@631
    70
    default n
yann@631
    71
yann@631
    72
config ARCH_SUPPORT_CPU
yann@631
    73
    bool
yann@631
    74
    default n
yann@631
    75
yann@631
    76
config ARCH_SUPPORT_TUNE
yann@631
    77
    bool
yann@631
    78
    default n
yann@631
    79
yann@631
    80
config ARCH_SUPPORT_FPU
yann@631
    81
    bool
yann@631
    82
    default n
yann@631
    83
yann@47
    84
config ARCH_ARCH
yann@47
    85
    string
yann@425
    86
    prompt "Architecture level"
yann@631
    87
    depends on ARCH_SUPPORT_ARCH
yann@47
    88
    default ""
yann@47
    89
    help
yann@47
    90
      GCC uses this name to determine what kind of instructions it can emit
yann@47
    91
      when generating assembly code. This option can be used in conjunction
yann@47
    92
      with or instead of the ARCH_CPU option (above), or a (command-line)
yann@47
    93
      -mcpu= option.
yann@47
    94
      
yann@47
    95
      This is the configuration flag --with-arch=XXXX, and the runtime flag
yann@47
    96
      -march=XXX.
yann@47
    97
      
yann@47
    98
      Pick a value from the gcc manual for your choosen gcc version and your
yann@47
    99
      target CPU.
yann@47
   100
      
yann@47
   101
      Leave blank if you don't know, or if your target architecture does not
yann@47
   102
      offer this option.
yann@47
   103
yann@45
   104
config ARCH_ABI
yann@45
   105
    string
yann@45
   106
    prompt "Generate code for the specific ABI"
yann@631
   107
    depends on ARCH_SUPPORT_ABI
yann@45
   108
    default ""
yann@45
   109
    help
yann@45
   110
      Generate code for the given ABI.
yann@45
   111
yann@47
   112
      This is the configuration flag --with-abi=XXXX, and the runtime flag
yann@47
   113
      -mabi=XXX.
yann@47
   114
yann@45
   115
      Pick a value from the gcc manual for your choosen gcc version and your
yann@45
   116
      target CPU.
yann@45
   117
yann@45
   118
      Leave blank if you don't know, or if your target architecutre does not
yann@45
   119
      offer this option.
yann@45
   120
yann@1
   121
config ARCH_CPU
yann@1
   122
    string
yann@1
   123
    prompt "Emit assembly for CPU"
yann@631
   124
    depends on ARCH_SUPPORT_CPU
yann@1
   125
    default ""
yann@1
   126
    help
yann@283
   127
      This specifies the name of the target processor. GCC uses this name
yann@1
   128
      to determine what kind of instructions it can emit when generating
yann@1
   129
      assembly code.
yann@1
   130
      
yann@47
   131
      This is the configuration flag --with-cpu=XXXX, and the runtime flag
yann@47
   132
      -mcpu=XXX.
yann@47
   133
yann@1
   134
      Pick a value from the gcc manual for your choosen gcc version and your
yann@1
   135
      target CPU.
yann@1
   136
      
yann@1
   137
      Leave blank if you don't know, or if your target architecture does not
yann@1
   138
      offer this option.
yann@1
   139
yann@1
   140
config ARCH_TUNE
yann@1
   141
    string
yann@1
   142
    prompt "Tune for CPU"
yann@631
   143
    depends on ARCH_SUPPORT_TUNE
yann@1
   144
    default ""
yann@1
   145
    help
yann@1
   146
      This option is very similar to the ARCH_CPU option (above), except
yann@1
   147
      that instead of specifying the actual target processor type, and hence
yann@1
   148
      restricting which instructions can be used, it specifies that GCC should
yann@1
   149
      tune the performance of the code as if the target were of the type
yann@1
   150
      specified in this option, but still choosing the instructions that it
yann@1
   151
      will generate based on the cpu specified by the ARCH_CPU option
yann@1
   152
      (above), or a (command-line) -mcpu= option.
yann@1
   153
      
yann@47
   154
      This is the configuration flag --with-tune=XXXX, and the runtime flag
yann@47
   155
      -mtune=XXX.
yann@1
   156
      
yann@1
   157
      Pick a value from the gcc manual for your choosen gcc version and your
yann@1
   158
      target CPU.
yann@1
   159
      
yann@1
   160
      Leave blank if you don't know, or if your target architecture does not
yann@1
   161
      offer this option.
yann@1
   162
yann@1
   163
config ARCH_FPU
yann@1
   164
    string
yann@47
   165
    prompt "Use specific FPU"
yann@631
   166
    depends on ARCH_SUPPORT_FPU
yann@1
   167
    default ""
yann@1
   168
    help
yann@1
   169
      On some targets (eg. ARM), you can specify the kind of FPU to emit
yann@1
   170
      code for.
yann@47
   171
yann@47
   172
      This is the configuration flag --with-fpu=XXX, and the runtime flag
yann@47
   173
      -mfpu=XXX.
yann@1
   174
      
yann@1
   175
      See below wether to actually emit FP opcodes, or to emulate them.
yann@1
   176
      
yann@1
   177
      Pick a value from the gcc manual for your choosen gcc version and your
yann@1
   178
      target CPU.
yann@1
   179
      
yann@1
   180
      Leave blank if you don't know, or if your target architecture does not
yann@1
   181
      offer this option.
yann@1
   182
yann@1
   183
choice
yann@1
   184
    bool
yann@1
   185
    prompt "Floating point:"
yann@1
   186
yann@1
   187
config ARCH_FLOAT_HW
yann@1
   188
    bool
yann@1
   189
    prompt "hardware (FPU)"
yann@1
   190
    help
yann@1
   191
      Emit hardware floating point opcodes.
yann@1
   192
      
yann@1
   193
      If you've got a processor with a FPU, then you want that.
yann@1
   194
      If your hardware has no FPU, you still can use HW floating point, but
yann@1
   195
      need to compile support for FPU emulation in your kernel. Needless to
yann@1
   196
      say that emulating the FPU is /slooowwwww/...
yann@1
   197
      
yann@1
   198
      One situation you'd want HW floating point without a FPU is if you get
yann@1
   199
      binary blobs from different vendors that are compiling this way and
yann@1
   200
      can't (don't wan't to) change.
yann@1
   201
yann@1
   202
config ARCH_FLOAT_SW
yann@1
   203
    bool
yann@1
   204
    prompt "software"
yann@1
   205
    help
yann@1
   206
      Do not emit any hardware floating point opcode.
yann@1
   207
      
yann@1
   208
      If your processor has no FPU, then you most probably want this, as it
yann@1
   209
      is faster than emulating the FPU in the kernel.
yann@1
   210
yann@1
   211
endchoice
yann@1
   212
yann@1
   213
config TARGET_CFLAGS
yann@1
   214
    string
yann@41
   215
    prompt "Target CFLAGS"
yann@1
   216
    default ""
yann@1
   217
    help
yann@1
   218
      Used to add specific options when compiling libraries of the toolchain,
yann@1
   219
      that will run on the target (eg. libc.so).
yann@1
   220
      
yann@531
   221
      Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
yann@1
   222
      automaticaly used. You don't need to specify them here.
yann@1
   223
      
yann@1
   224
      Leave blank if you don't know better.
yann@1
   225
yann@767
   226
config TARGET_LDFLAGS
yann@767
   227
    string
yann@767
   228
    prompt "Target LDFLAGS"
yann@767
   229
    default ""
yann@767
   230
    help
yann@767
   231
      Used to add specific options when linking libraries of the toolchain,
yann@767
   232
      that will run on your target.
yann@767
   233
      
yann@767
   234
      Leave blank if you don't know better.
yann@767
   235
yann@1
   236
endmenu