2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
9 select HAVE_ARCH_TRACEHOOK
10 select HAVE_PERF_COUNTERS
16 config RWSEM_GENERIC_SPINLOCK
20 config RWSEM_XCHGADD_ALGORITHM
23 config GENERIC_FIND_NEXT_BIT
27 config GENERIC_HWEIGHT
31 config GENERIC_CALIBRATE_DELAY
35 config GENERIC_HARDIRQS
39 config GENERIC_HARDIRQS_NO__DO_IRQ
55 config ARCH_HAS_ILOG2_U32
59 config ARCH_HAS_ILOG2_U64
67 mainmenu "Fujitsu FR-V Kernel Configuration"
71 source "kernel/Kconfig.freezer"
74 menu "Fujitsu FR-V system setup"
79 This options switches on and off support for the FR-V MMU
80 (effectively switching between vmlinux and uClinux). Not all FR-V
81 CPUs support this. Currently only the FR451 has a sufficiently
84 config FRV_OUTOFLINE_ATOMIC_OPS
85 bool "Out-of-line the FRV atomic operations"
88 Setting this option causes the FR-V atomic operations to be mostly
89 implemented out-of-line.
91 See Documentation/frv/atomic-ops.txt for more information.
94 bool "High memory support"
98 If you wish to use more than 256MB of memory with your MMU based
99 system, you will need to select this option. The kernel can only see
100 the memory between 0xC0000000 and 0xD0000000 directly... everything
101 else must be kmapped.
103 The arch is, however, capable of supporting up to 3GB of SDRAM.
106 bool "Allocate page tables in highmem"
110 The VM uses one page of memory for each page table. For systems
111 with a lot of RAM, this can be wasteful of precious low memory.
112 Setting this option will put user-space page tables in high memory.
117 prompt "uClinux kernel load address"
119 default UCPAGE_OFFSET_C0000000
121 This option sets the base address for the uClinux kernel. The kernel
122 will rearrange the SDRAM layout to start at this address, and move
123 itself to start there. It must be greater than 0, and it must be
124 sufficiently less than 0xE0000000 that the SDRAM does not intersect
127 The base address must also be aligned such that the SDRAM controller
128 can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.
130 config UCPAGE_OFFSET_20000000
133 config UCPAGE_OFFSET_40000000
136 config UCPAGE_OFFSET_60000000
139 config UCPAGE_OFFSET_80000000
142 config UCPAGE_OFFSET_A0000000
145 config UCPAGE_OFFSET_C0000000
146 bool "0xC0000000 (Recommended)"
152 default 0x20000000 if UCPAGE_OFFSET_20000000
153 default 0x40000000 if UCPAGE_OFFSET_40000000
154 default 0x60000000 if UCPAGE_OFFSET_60000000
155 default 0x80000000 if UCPAGE_OFFSET_80000000
156 default 0xA0000000 if UCPAGE_OFFSET_A0000000
159 config PROTECT_KERNEL
160 bool "Protect core kernel against userspace"
164 Selecting this option causes the uClinux kernel to change the
165 permittivity of DAMPR register covering the core kernel image to
166 prevent userspace accessing the underlying memory directly.
169 prompt "CPU Caching mode"
170 default FRV_DEFL_CACHE_WBACK
172 This option determines the default caching mode for the kernel.
174 Write-Back caching mode involves the all reads and writes causing
175 the affected cacheline to be read into the cache first before being
176 operated upon. Memory is not then updated by a write until the cache
177 is filled and a cacheline needs to be displaced from the cache to
178 make room. Only at that point is it written back.
180 Write-Behind caching is similar to Write-Back caching, except that a
181 write won't fetch a cacheline into the cache if there isn't already
182 one there; it will write directly to memory instead.
184 Write-Through caching only fetches cachelines from memory on a
185 read. Writes always get written directly to memory. If the affected
186 cacheline is also in cache, it will be updated too.
188 The final option is to turn of caching entirely.
190 Note that not all CPUs support Write-Behind caching. If the CPU on
191 which the kernel is running doesn't, it'll fall back to Write-Back
194 config FRV_DEFL_CACHE_WBACK
197 config FRV_DEFL_CACHE_WBEHIND
200 config FRV_DEFL_CACHE_WTHRU
203 config FRV_DEFL_CACHE_DISABLED
208 menu "CPU core support"
211 bool "Include FR401 core support"
215 This enables support for the FR401, FR401A and FR403 CPUs
218 bool "Include FR405 core support"
222 This enables support for the FR405 CPU
225 bool "Include FR451 core support"
228 This enables support for the FR451 CPU
230 config CPU_FR451_COMPILE
231 bool "Specifically compile for FR451 core"
232 depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
235 This causes appropriate flags to be passed to the compiler to
236 optimise for the FR451 CPU
239 bool "Include FR551 core support"
243 This enables support for the FR555 CPU
245 config CPU_FR551_COMPILE
246 bool "Specifically compile for FR551 core"
247 depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
250 This causes appropriate flags to be passed to the compiler to
251 optimise for the FR555 CPU
253 config FRV_L1_CACHE_SHIFT
255 default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
256 default "6" if CPU_FR551
261 prompt "System support"
265 bool "MB93091 CPU board with or without motherboard"
268 bool "MB93093 PDK unit"
274 prompt "Motherboard support"
278 bool "Use the MB93090-MB00 motherboard"
280 Select this option if the MB93091 CPU board is going to be used with
281 a MB93090-MB00 VDK motherboard
284 bool "Use standalone"
286 Select this option if the MB93091 CPU board is going to be used
287 without a motherboard
292 config FUJITSU_MB93493
293 bool "MB93493 Multimedia chip"
295 Select this option if the MB93493 multimedia chip is going to be
299 prompt "GP-Relative data support"
302 This option controls what data, if any, should be placed in the GP
303 relative data sections. Using this means that the compiler can
304 generate accesses to the data using GR16-relative addressing which
305 is faster than absolute instructions and saves space (2 instructions
308 However, the GPREL region is limited in size because the immediate
309 value used in the load and store instructions is limited to a 12-bit
312 So if the linker starts complaining that accesses to GPREL data are
313 out of range, try changing this option from the default.
315 Note that modules will always be compiled with this feature disabled
316 as the module data will not be in range of the GP base address.
319 bool "Put data objects of up to 8 bytes into GP-REL"
322 bool "Put data objects of up to 4 bytes into GP-REL"
324 config GPREL_DATA_NONE
325 bool "Don't use GP-REL"
329 config FRV_ONCPU_SERIAL
330 bool "Use on-CPU serial ports"
336 depends on MB93090_MB00
339 Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
340 onboard. If you have one of these boards and you wish to use the PCI
341 facilities, say Y here.
343 config RESERVE_DMA_COHERENT
344 bool "Reserve DMA coherent memory"
345 depends on PCI && !MMU
348 Many PCI drivers require access to uncached memory for DMA device
349 communications (such as is done with some Ethernet buffer rings). If
350 a fully featured MMU is available, this can be done through page
351 table settings, but if not, a region has to be set aside and marked
352 with a special DAMPR register.
354 Setting this option causes uClinux to set aside a portion of the
355 available memory for use in this manner. The memory will then be
356 unavailable for normal kernel use.
358 source "drivers/pci/Kconfig"
360 source "drivers/pcmcia/Kconfig"
362 #config MATH_EMULATION
363 # bool "Math emulation support (EXPERIMENTAL)"
364 # depends on EXPERIMENTAL
366 # At some point in the future, this will cause floating-point math
367 # instructions to be emulated by the kernel on machines that lack a
368 # floating-point math coprocessor. Thrill-seekers and chronically
369 # sleep-deprived psychotic hacker types can say Y now, everyone else
370 # should probably wait a while.
372 menu "Power management options"
374 config ARCH_SUSPEND_POSSIBLE
378 source kernel/power/Kconfig
384 menu "Executable formats"
386 source "fs/Kconfig.binfmt"
392 source "drivers/Kconfig"
396 source "arch/frv/Kconfig.debug"
398 source "security/Kconfig"
400 source "crypto/Kconfig"