Maybe one time we'll have subdirs in the config/ directory: find all dependencies for .config.
Remove never used include (was commented out anyway). Might come back later when we play with canadian-crosses.
1 # Target definition: architecture, optimisations, etc...
5 comment "General target options"
9 prompt "Target architecture:"
15 select ARCH_SUPPORTS_BE
16 select ARCH_SUPPORTS_LE
21 select ARCH_SUPPORTS_BE
22 select ARCH_SUPPORTS_LE
27 select ARCH_SUPPORTS_LE
32 select ARCH_SUPPORTS_LE
36 config ARCH_SUPPORTS_BE
40 config ARCH_SUPPORTS_LE
51 depends on ARCH_SUPPORTS_BE
55 prompt "Little endian"
56 depends on ARCH_SUPPORTS_LE
60 comment "Target optimisations"
64 prompt "Emit assembly for CPU"
67 This specifies the name of the target ARM processor. GCC uses this name
68 to determine what kind of instructions it can emit when generating
71 Pick a value from the gcc manual for your choosen gcc version and your
74 Leave blank if you don't know, or if your target architecture does not
82 This option is very similar to the ARCH_CPU option (above), except
83 that instead of specifying the actual target processor type, and hence
84 restricting which instructions can be used, it specifies that GCC should
85 tune the performance of the code as if the target were of the type
86 specified in this option, but still choosing the instructions that it
87 will generate based on the cpu specified by the ARCH_CPU option
88 (above), or a (command-line) -mcpu= option.
90 Pick a value from the gcc manual for your choosen gcc version and your
93 Leave blank if you don't know, or if your target architecture does not
98 prompt "Achitecture level"
101 GCC uses this name to determine what kind of instructions it can emit
102 when generating assembly code. This option can be used in conjunction
103 with or instead of the ARCH_CPU option (above), or a (command-line)
106 Pick a value from the gcc manual for your choosen gcc version and your
109 Leave blank if you don't know, or if your target architecture does not
117 On some targets (eg. ARM), you can specify the kind of FPU to emit
120 See below wether to actually emit FP opcodes, or to emulate them.
122 Pick a value from the gcc manual for your choosen gcc version and your
125 Leave blank if you don't know, or if your target architecture does not
130 prompt "Floating point:"
134 prompt "hardware (FPU)"
136 Emit hardware floating point opcodes.
138 If you've got a processor with a FPU, then you want that.
139 If your hardware has no FPU, you still can use HW floating point, but
140 need to compile support for FPU emulation in your kernel. Needless to
141 say that emulating the FPU is /slooowwwww/...
143 One situation you'd want HW floating point without a FPU is if you get
144 binary blobs from different vendors that are compiling this way and
145 can't (don't wan't to) change.
151 Do not emit any hardware floating point opcode.
153 If your processor has no FPU, then you most probably want this, as it
154 is faster than emulating the FPU in the kernel.
158 config ARCH_FLOAT_SW_LIBFLOAT
160 prompt "Use libfloat"
162 depends on ARCH_FLOAT_SW
164 For those targets upporting it, you can use libfloat for the software
165 floating point emulation.
167 Note that some versions of gcc have support code that supersedes libfloat,
168 while others don't. Known version of gcc that don't have support code are
169 versions prior to 3.0, and version above 4.0.
171 You should check gcc before deciding to use libfloat.
175 prompt "Target CFLAGS"
178 Used to add specific options when compiling libraries of the toolchain,
179 that will run on the target (eg. libc.so).
181 Note that the options above for CPU, tune, arch and FPU will be
182 automaticaly used. You don't need to specify them here.
184 Leave blank if you don't know better.