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