blob: 74eef7111f2bd429e60d93e1a5d021dd3ca5f50d [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5config FRV
6 bool
7 default y
8
Christoph Lameter66701b12007-02-10 01:43:09 -08009config ZONE_DMA
10 bool
11 default y
12
Linus Torvalds1da177e2005-04-16 15:20:36 -070013config RWSEM_GENERIC_SPINLOCK
14 bool
15 default y
16
17config RWSEM_XCHGADD_ALGORITHM
18 bool
19
20config GENERIC_FIND_NEXT_BIT
21 bool
22 default y
23
Akinobu Mita1f6d7a92006-03-26 01:39:22 -080024config GENERIC_HWEIGHT
25 bool
26 default y
27
Linus Torvalds1da177e2005-04-16 15:20:36 -070028config GENERIC_CALIBRATE_DELAY
29 bool
30 default n
31
32config GENERIC_HARDIRQS
33 bool
David Howells1bcbba32006-09-25 23:32:04 -070034 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -070035
David Howellsaf8c65b2006-09-25 23:32:07 -070036config GENERIC_HARDIRQS_NO__DO_IRQ
37 bool
38 default y
39
john stultzebd6c172006-09-06 11:02:45 +010040config GENERIC_TIME
41 bool
42 default y
43
Ingo Molnar06027bd2006-02-14 13:53:15 -080044config TIME_LOW_RES
45 bool
46 default y
47
Christoph Lameter8defab32007-05-09 02:32:48 -070048config QUICKLIST
49 bool
50 default y
51
David Howellsf0d1b0b2006-12-08 02:37:49 -080052config ARCH_HAS_ILOG2_U32
53 bool
54 default y
55
56config ARCH_HAS_ILOG2_U64
57 bool
58 default y
59
Linus Torvalds1da177e2005-04-16 15:20:36 -070060mainmenu "Fujitsu FR-V Kernel Configuration"
61
62source "init/Kconfig"
63
64
65menu "Fujitsu FR-V system setup"
66
67config MMU
68 bool "MMU support"
69 help
70 This options switches on and off support for the FR-V MMU
71 (effectively switching between vmlinux and uClinux). Not all FR-V
72 CPUs support this. Currently only the FR451 has a sufficiently
73 featured MMU.
74
75config FRV_OUTOFLINE_ATOMIC_OPS
76 bool "Out-of-line the FRV atomic operations"
77 default n
78 help
79 Setting this option causes the FR-V atomic operations to be mostly
80 implemented out-of-line.
81
82 See Documentation/fujitsu/frv/atomic-ops.txt for more information.
83
84config HIGHMEM
85 bool "High memory support"
86 depends on MMU
87 default y
88 help
89 If you wish to use more than 256MB of memory with your MMU based
90 system, you will need to select this option. The kernel can only see
91 the memory between 0xC0000000 and 0xD0000000 directly... everything
92 else must be kmapped.
93
94 The arch is, however, capable of supporting up to 3GB of SDRAM.
95
96config HIGHPTE
97 bool "Allocate page tables in highmem"
98 depends on HIGHMEM
99 default y
100 help
101 The VM uses one page of memory for each page table. For systems
102 with a lot of RAM, this can be wasteful of precious low memory.
103 Setting this option will put user-space page tables in high memory.
104
Dave Hansen3f22ab22005-06-23 00:07:43 -0700105source "mm/Kconfig"
106
Linus Torvalds1da177e2005-04-16 15:20:36 -0700107choice
108 prompt "uClinux kernel load address"
109 depends on !MMU
110 default UCPAGE_OFFSET_C0000000
111 help
112 This option sets the base address for the uClinux kernel. The kernel
113 will rearrange the SDRAM layout to start at this address, and move
114 itself to start there. It must be greater than 0, and it must be
115 sufficiently less than 0xE0000000 that the SDRAM does not intersect
116 the I/O region.
117
118 The base address must also be aligned such that the SDRAM controller
119 can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.
120
121config UCPAGE_OFFSET_20000000
122 bool "0x20000000"
123
124config UCPAGE_OFFSET_40000000
125 bool "0x40000000"
126
127config UCPAGE_OFFSET_60000000
128 bool "0x60000000"
129
130config UCPAGE_OFFSET_80000000
131 bool "0x80000000"
132
133config UCPAGE_OFFSET_A0000000
134 bool "0xA0000000"
135
136config UCPAGE_OFFSET_C0000000
137 bool "0xC0000000 (Recommended)"
138
139endchoice
140
141config PROTECT_KERNEL
142 bool "Protect core kernel against userspace"
143 depends on !MMU
144 default y
145 help
146 Selecting this option causes the uClinux kernel to change the
147 permittivity of DAMPR register covering the core kernel image to
148 prevent userspace accessing the underlying memory directly.
149
150choice
151 prompt "CPU Caching mode"
152 default FRV_DEFL_CACHE_WBACK
153 help
154 This option determines the default caching mode for the kernel.
155
156 Write-Back caching mode involves the all reads and writes causing
157 the affected cacheline to be read into the cache first before being
158 operated upon. Memory is not then updated by a write until the cache
159 is filled and a cacheline needs to be displaced from the cache to
160 make room. Only at that point is it written back.
161
162 Write-Behind caching is similar to Write-Back caching, except that a
163 write won't fetch a cacheline into the cache if there isn't already
164 one there; it will write directly to memory instead.
165
166 Write-Through caching only fetches cachelines from memory on a
167 read. Writes always get written directly to memory. If the affected
168 cacheline is also in cache, it will be updated too.
169
170 The final option is to turn of caching entirely.
171
172 Note that not all CPUs support Write-Behind caching. If the CPU on
173 which the kernel is running doesn't, it'll fall back to Write-Back
174 caching.
175
176config FRV_DEFL_CACHE_WBACK
177 bool "Write-Back"
178
179config FRV_DEFL_CACHE_WBEHIND
180 bool "Write-Behind"
181
182config FRV_DEFL_CACHE_WTHRU
183 bool "Write-Through"
184
185config FRV_DEFL_CACHE_DISABLED
186 bool "Disabled"
187
188endchoice
189
190menu "CPU core support"
191
192config CPU_FR401
193 bool "Include FR401 core support"
194 depends on !MMU
195 default y
196 help
197 This enables support for the FR401, FR401A and FR403 CPUs
198
199config CPU_FR405
200 bool "Include FR405 core support"
201 depends on !MMU
202 default y
203 help
204 This enables support for the FR405 CPU
205
206config CPU_FR451
207 bool "Include FR451 core support"
208 default y
209 help
210 This enables support for the FR451 CPU
211
212config CPU_FR451_COMPILE
213 bool "Specifically compile for FR451 core"
214 depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
215 default y
216 help
217 This causes appropriate flags to be passed to the compiler to
218 optimise for the FR451 CPU
219
220config CPU_FR551
221 bool "Include FR551 core support"
222 depends on !MMU
223 default y
224 help
225 This enables support for the FR555 CPU
226
227config CPU_FR551_COMPILE
228 bool "Specifically compile for FR551 core"
229 depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
230 default y
231 help
232 This causes appropriate flags to be passed to the compiler to
233 optimise for the FR555 CPU
234
235config FRV_L1_CACHE_SHIFT
236 int
237 default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
238 default "6" if CPU_FR551
239
240endmenu
241
242choice
243 prompt "System support"
244 default MB93091_VDK
245
246config MB93091_VDK
247 bool "MB93091 CPU board with or without motherboard"
248
249config MB93093_PDK
250 bool "MB93093 PDK unit"
251
252endchoice
253
254if MB93091_VDK
255choice
256 prompt "Motherboard support"
257 default MB93090_MB00
258
259config MB93090_MB00
260 bool "Use the MB93090-MB00 motherboard"
261 help
262 Select this option if the MB93091 CPU board is going to be used with
263 a MB93090-MB00 VDK motherboard
264
265config MB93091_NO_MB
266 bool "Use standalone"
267 help
268 Select this option if the MB93091 CPU board is going to be used
269 without a motherboard
270
271endchoice
272endif
273
David Howells1bcbba32006-09-25 23:32:04 -0700274config FUJITSU_MB93493
275 bool "MB93493 Multimedia chip"
276 help
277 Select this option if the MB93493 multimedia chip is going to be
278 used.
279
Linus Torvalds1da177e2005-04-16 15:20:36 -0700280choice
281 prompt "GP-Relative data support"
282 default GPREL_DATA_8
283 help
284 This option controls what data, if any, should be placed in the GP
285 relative data sections. Using this means that the compiler can
286 generate accesses to the data using GR16-relative addressing which
287 is faster than absolute instructions and saves space (2 instructions
288 per access).
289
290 However, the GPREL region is limited in size because the immediate
291 value used in the load and store instructions is limited to a 12-bit
292 signed number.
293
294 So if the linker starts complaining that accesses to GPREL data are
295 out of range, try changing this option from the default.
296
297 Note that modules will always be compiled with this feature disabled
298 as the module data will not be in range of the GP base address.
299
300config GPREL_DATA_8
301 bool "Put data objects of up to 8 bytes into GP-REL"
302
303config GPREL_DATA_4
304 bool "Put data objects of up to 4 bytes into GP-REL"
305
306config GPREL_DATA_NONE
307 bool "Don't use GP-REL"
308
309endchoice
310
David Howellsf8aec752006-01-08 01:01:23 -0800311config FRV_ONCPU_SERIAL
312 bool "Use on-CPU serial ports"
313 select SERIAL_8250
314 default y
315
Linus Torvalds1da177e2005-04-16 15:20:36 -0700316config PCI
317 bool "Use PCI"
318 depends on MB93090_MB00
319 default y
320 help
321 Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
322 onboard. If you have one of these boards and you wish to use the PCI
323 facilities, say Y here.
324
325 The PCI-HOWTO, available from
326 <http://www.tldp.org/docs.html#howto>, contains valuable
327 information about which PCI hardware does work under Linux and which
328 doesn't.
329
330config RESERVE_DMA_COHERENT
331 bool "Reserve DMA coherent memory"
332 depends on PCI && !MMU
333 default y
334 help
335 Many PCI drivers require access to uncached memory for DMA device
336 communications (such as is done with some Ethernet buffer rings). If
337 a fully featured MMU is available, this can be done through page
338 table settings, but if not, a region has to be set aside and marked
339 with a special DAMPR register.
340
341 Setting this option causes uClinux to set aside a portion of the
342 available memory for use in this manner. The memory will then be
343 unavailable for normal kernel use.
344
345source "drivers/pci/Kconfig"
346
David Howells7a758312006-01-08 01:01:22 -0800347source "drivers/pcmcia/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700348
349#config MATH_EMULATION
350# bool "Math emulation support (EXPERIMENTAL)"
351# depends on EXPERIMENTAL
352# help
353# At some point in the future, this will cause floating-point math
354# instructions to be emulated by the kernel on machines that lack a
355# floating-point math coprocessor. Thrill-seekers and chronically
356# sleep-deprived psychotic hacker types can say Y now, everyone else
357# should probably wait a while.
358
359menu "Power management options"
360source kernel/power/Kconfig
361endmenu
362
363endmenu
364
365
366menu "Executable formats"
367
368source "fs/Kconfig.binfmt"
369
370endmenu
371
Sam Ravnborgd5950b42005-07-11 21:03:49 -0700372source "net/Kconfig"
373
Linus Torvalds1da177e2005-04-16 15:20:36 -0700374source "drivers/Kconfig"
375
376source "fs/Kconfig"
377
378source "arch/frv/Kconfig.debug"
379
380source "security/Kconfig"
381
382source "crypto/Kconfig"
383
384source "lib/Kconfig"