Make bare-metal a kernel selection.
/trunk/config/kernel.in | 22 14 8 0 ++++++++++++++--------
/trunk/config/target.in | 13 0 13 0 -------------
2 files changed, 14 insertions(+), 21 deletions(-)
1 # Target definition: architecture, optimisations, etc...
8 # Pre-declare target optimisation variables
9 config ARCH_SUPPORT_ARCH
10 config ARCH_SUPPORT_ABI
11 config ARCH_SUPPORT_CPU
12 config ARCH_SUPPORT_TUNE
13 config ARCH_SUPPORT_FPU
14 config ARCH_SUPPORTS_BOTH_ENDIAN
15 config ARCH_DEFAULT_BE
16 config ARCH_DEFAULT_LE
29 comment "General target options"
33 prompt "Target architecture:"
35 source config.gen/arch.in
39 config ARCH_SUPPORTS_BOTH_ENDIAN
43 config ARCH_DEFAULT_BE
47 config ARCH_DEFAULT_LE
54 depends on ARCH_SUPPORTS_BOTH_ENDIAN
55 default ARCH_BE if ARCH_DEFAULT_BE
56 default ARCH_LE if ARCH_DEFAULT_LE
64 prompt "Little endian"
68 comment "Target optimisations"
70 config ARCH_SUPPORT_ARCH
74 config ARCH_SUPPORT_ABI
78 config ARCH_SUPPORT_CPU
82 config ARCH_SUPPORT_TUNE
86 config ARCH_SUPPORT_FPU
92 prompt "Architecture level"
93 depends on ARCH_SUPPORT_ARCH
96 GCC uses this name to determine what kind of instructions it can emit
97 when generating assembly code. This option can be used in conjunction
98 with or instead of the ARCH_CPU option (above), or a (command-line)
101 This is the configuration flag --with-arch=XXXX, and the runtime flag
104 Pick a value from the gcc manual for your choosen gcc version and your
107 Leave blank if you don't know, or if your target architecture does not
112 prompt "Generate code for the specific ABI"
113 depends on ARCH_SUPPORT_ABI
116 Generate code for the given ABI.
118 This is the configuration flag --with-abi=XXXX, and the runtime flag
121 Pick a value from the gcc manual for your choosen gcc version and your
124 Leave blank if you don't know, or if your target architecutre does not
129 prompt "Emit assembly for CPU"
130 depends on ARCH_SUPPORT_CPU
133 This specifies the name of the target processor. GCC uses this name
134 to determine what kind of instructions it can emit when generating
137 This is the configuration flag --with-cpu=XXXX, and the runtime flag
140 Pick a value from the gcc manual for your choosen gcc version and your
143 Leave blank if you don't know, or if your target architecture does not
148 prompt "Tune for CPU"
149 depends on ARCH_SUPPORT_TUNE
152 This option is very similar to the ARCH_CPU option (above), except
153 that instead of specifying the actual target processor type, and hence
154 restricting which instructions can be used, it specifies that GCC should
155 tune the performance of the code as if the target were of the type
156 specified in this option, but still choosing the instructions that it
157 will generate based on the cpu specified by the ARCH_CPU option
158 (above), or a (command-line) -mcpu= option.
160 This is the configuration flag --with-tune=XXXX, and the runtime flag
163 Pick a value from the gcc manual for your choosen gcc version and your
166 Leave blank if you don't know, or if your target architecture does not
171 prompt "Use specific FPU"
172 depends on ARCH_SUPPORT_FPU
175 On some targets (eg. ARM), you can specify the kind of FPU to emit
178 This is the configuration flag --with-fpu=XXX, and the runtime flag
181 See below wether to actually emit FP opcodes, or to emulate them.
183 Pick a value from the gcc manual for your choosen gcc version and your
186 Leave blank if you don't know, or if your target architecture does not
191 prompt "Floating point:"
195 prompt "hardware (FPU)"
197 Emit hardware floating point opcodes.
199 If you've got a processor with a FPU, then you want that.
200 If your hardware has no FPU, you still can use HW floating point, but
201 need to compile support for FPU emulation in your kernel. Needless to
202 say that emulating the FPU is /slooowwwww/...
204 One situation you'd want HW floating point without a FPU is if you get
205 binary blobs from different vendors that are compiling this way and
206 can't (don't wan't to) change.
212 Do not emit any hardware floating point opcode.
214 If your processor has no FPU, then you most probably want this, as it
215 is faster than emulating the FPU in the kernel.
221 prompt "Target CFLAGS"
224 Used to add specific options when compiling libraries of the toolchain,
225 that will run on the target (eg. libc.so).
227 Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
228 automaticaly used. You don't need to specify them here.
230 Leave blank if you don't know better.
232 config TARGET_LDFLAGS
234 prompt "Target LDFLAGS"
237 Used to add specific options when linking libraries of the toolchain,
238 that will run on your target.
240 Leave blank if you don't know better.