2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
14 config RWSEM_GENERIC_SPINLOCK
18 config RWSEM_XCHGADD_ALGORITHM
21 config GENERIC_FIND_NEXT_BIT
25 config GENERIC_HWEIGHT
29 config GENERIC_CALIBRATE_DELAY
33 config GENERIC_HARDIRQS
37 config GENERIC_HARDIRQS_NO__DO_IRQ
53 config ARCH_HAS_ILOG2_U32
57 config ARCH_HAS_ILOG2_U64
65 mainmenu "Fujitsu FR-V Kernel Configuration"
69 source "kernel/Kconfig.freezer"
72 menu "Fujitsu FR-V system setup"
77 This options switches on and off support for the FR-V MMU
78 (effectively switching between vmlinux and uClinux). Not all FR-V
79 CPUs support this. Currently only the FR451 has a sufficiently
82 config FRV_OUTOFLINE_ATOMIC_OPS
83 bool "Out-of-line the FRV atomic operations"
86 Setting this option causes the FR-V atomic operations to be mostly
87 implemented out-of-line.
89 See Documentation/frv/atomic-ops.txt for more information.
92 bool "High memory support"
96 If you wish to use more than 256MB of memory with your MMU based
97 system, you will need to select this option. The kernel can only see
98 the memory between 0xC0000000 and 0xD0000000 directly... everything
101 The arch is, however, capable of supporting up to 3GB of SDRAM.
104 bool "Allocate page tables in highmem"
108 The VM uses one page of memory for each page table. For systems
109 with a lot of RAM, this can be wasteful of precious low memory.
110 Setting this option will put user-space page tables in high memory.
115 prompt "uClinux kernel load address"
117 default UCPAGE_OFFSET_C0000000
119 This option sets the base address for the uClinux kernel. The kernel
120 will rearrange the SDRAM layout to start at this address, and move
121 itself to start there. It must be greater than 0, and it must be
122 sufficiently less than 0xE0000000 that the SDRAM does not intersect
125 The base address must also be aligned such that the SDRAM controller
126 can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.
128 config UCPAGE_OFFSET_20000000
131 config UCPAGE_OFFSET_40000000
134 config UCPAGE_OFFSET_60000000
137 config UCPAGE_OFFSET_80000000
140 config UCPAGE_OFFSET_A0000000
143 config UCPAGE_OFFSET_C0000000
144 bool "0xC0000000 (Recommended)"
150 default 0x20000000 if UCPAGE_OFFSET_20000000
151 default 0x40000000 if UCPAGE_OFFSET_40000000
152 default 0x60000000 if UCPAGE_OFFSET_60000000
153 default 0x80000000 if UCPAGE_OFFSET_80000000
154 default 0xA0000000 if UCPAGE_OFFSET_A0000000
157 config PROTECT_KERNEL
158 bool "Protect core kernel against userspace"
162 Selecting this option causes the uClinux kernel to change the
163 permittivity of DAMPR register covering the core kernel image to
164 prevent userspace accessing the underlying memory directly.
167 prompt "CPU Caching mode"
168 default FRV_DEFL_CACHE_WBACK
170 This option determines the default caching mode for the kernel.
172 Write-Back caching mode involves the all reads and writes causing
173 the affected cacheline to be read into the cache first before being
174 operated upon. Memory is not then updated by a write until the cache
175 is filled and a cacheline needs to be displaced from the cache to
176 make room. Only at that point is it written back.
178 Write-Behind caching is similar to Write-Back caching, except that a
179 write won't fetch a cacheline into the cache if there isn't already
180 one there; it will write directly to memory instead.
182 Write-Through caching only fetches cachelines from memory on a
183 read. Writes always get written directly to memory. If the affected
184 cacheline is also in cache, it will be updated too.
186 The final option is to turn of caching entirely.
188 Note that not all CPUs support Write-Behind caching. If the CPU on
189 which the kernel is running doesn't, it'll fall back to Write-Back
192 config FRV_DEFL_CACHE_WBACK
195 config FRV_DEFL_CACHE_WBEHIND
198 config FRV_DEFL_CACHE_WTHRU
201 config FRV_DEFL_CACHE_DISABLED
206 menu "CPU core support"
209 bool "Include FR401 core support"
213 This enables support for the FR401, FR401A and FR403 CPUs
216 bool "Include FR405 core support"
220 This enables support for the FR405 CPU
223 bool "Include FR451 core support"
226 This enables support for the FR451 CPU
228 config CPU_FR451_COMPILE
229 bool "Specifically compile for FR451 core"
230 depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
233 This causes appropriate flags to be passed to the compiler to
234 optimise for the FR451 CPU
237 bool "Include FR551 core support"
241 This enables support for the FR555 CPU
243 config CPU_FR551_COMPILE
244 bool "Specifically compile for FR551 core"
245 depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
248 This causes appropriate flags to be passed to the compiler to
249 optimise for the FR555 CPU
251 config FRV_L1_CACHE_SHIFT
253 default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
254 default "6" if CPU_FR551
259 prompt "System support"
263 bool "MB93091 CPU board with or without motherboard"
266 bool "MB93093 PDK unit"
272 prompt "Motherboard support"
276 bool "Use the MB93090-MB00 motherboard"
278 Select this option if the MB93091 CPU board is going to be used with
279 a MB93090-MB00 VDK motherboard
282 bool "Use standalone"
284 Select this option if the MB93091 CPU board is going to be used
285 without a motherboard
290 config FUJITSU_MB93493
291 bool "MB93493 Multimedia chip"
293 Select this option if the MB93493 multimedia chip is going to be
297 prompt "GP-Relative data support"
300 This option controls what data, if any, should be placed in the GP
301 relative data sections. Using this means that the compiler can
302 generate accesses to the data using GR16-relative addressing which
303 is faster than absolute instructions and saves space (2 instructions
306 However, the GPREL region is limited in size because the immediate
307 value used in the load and store instructions is limited to a 12-bit
310 So if the linker starts complaining that accesses to GPREL data are
311 out of range, try changing this option from the default.
313 Note that modules will always be compiled with this feature disabled
314 as the module data will not be in range of the GP base address.
317 bool "Put data objects of up to 8 bytes into GP-REL"
320 bool "Put data objects of up to 4 bytes into GP-REL"
322 config GPREL_DATA_NONE
323 bool "Don't use GP-REL"
327 config FRV_ONCPU_SERIAL
328 bool "Use on-CPU serial ports"
334 depends on MB93090_MB00
337 Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
338 onboard. If you have one of these boards and you wish to use the PCI
339 facilities, say Y here.
341 config RESERVE_DMA_COHERENT
342 bool "Reserve DMA coherent memory"
343 depends on PCI && !MMU
346 Many PCI drivers require access to uncached memory for DMA device
347 communications (such as is done with some Ethernet buffer rings). If
348 a fully featured MMU is available, this can be done through page
349 table settings, but if not, a region has to be set aside and marked
350 with a special DAMPR register.
352 Setting this option causes uClinux to set aside a portion of the
353 available memory for use in this manner. The memory will then be
354 unavailable for normal kernel use.
356 source "drivers/pci/Kconfig"
358 source "drivers/pcmcia/Kconfig"
360 #config MATH_EMULATION
361 # bool "Math emulation support (EXPERIMENTAL)"
362 # depends on EXPERIMENTAL
364 # At some point in the future, this will cause floating-point math
365 # instructions to be emulated by the kernel on machines that lack a
366 # floating-point math coprocessor. Thrill-seekers and chronically
367 # sleep-deprived psychotic hacker types can say Y now, everyone else
368 # should probably wait a while.
370 menu "Power management options"
372 config ARCH_SUSPEND_POSSIBLE
376 source kernel/power/Kconfig
382 menu "Executable formats"
384 source "fs/Kconfig.binfmt"
390 source "drivers/Kconfig"
394 source "arch/frv/Kconfig.debug"
396 source "security/Kconfig"
398 source "crypto/Kconfig"