Root/arch/frv/Kconfig

1config FRV
2    bool
3    default y
4    select HAVE_IDE
5    select HAVE_ARCH_TRACEHOOK
6    select HAVE_IRQ_WORK
7    select HAVE_PERF_EVENTS
8
9config ZONE_DMA
10    bool
11    default y
12
13config 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
24config GENERIC_HWEIGHT
25    bool
26    default y
27
28config GENERIC_CALIBRATE_DELAY
29    bool
30    default n
31
32config GENERIC_HARDIRQS
33    bool
34    default y
35
36config GENERIC_HARDIRQS_NO__DO_IRQ
37    bool
38    default y
39
40config TIME_LOW_RES
41    bool
42    default y
43
44config QUICKLIST
45    bool
46    default y
47
48config ARCH_HAS_ILOG2_U32
49    bool
50    default y
51
52config ARCH_HAS_ILOG2_U64
53    bool
54    default y
55
56config HZ
57    int
58    default 1000
59
60source "init/Kconfig"
61
62source "kernel/Kconfig.freezer"
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/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
105source "mm/Kconfig"
106
107choice
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 PAGE_OFFSET
142    hex
143    default 0x20000000 if UCPAGE_OFFSET_20000000
144    default 0x40000000 if UCPAGE_OFFSET_40000000
145    default 0x60000000 if UCPAGE_OFFSET_60000000
146    default 0x80000000 if UCPAGE_OFFSET_80000000
147    default 0xA0000000 if UCPAGE_OFFSET_A0000000
148    default 0xC0000000
149
150config PROTECT_KERNEL
151    bool "Protect core kernel against userspace"
152    depends on !MMU
153    default y
154    help
155      Selecting this option causes the uClinux kernel to change the
156      permittivity of DAMPR register covering the core kernel image to
157      prevent userspace accessing the underlying memory directly.
158
159choice
160    prompt "CPU Caching mode"
161    default FRV_DEFL_CACHE_WBACK
162    help
163      This option determines the default caching mode for the kernel.
164
165      Write-Back caching mode involves the all reads and writes causing
166      the affected cacheline to be read into the cache first before being
167      operated upon. Memory is not then updated by a write until the cache
168      is filled and a cacheline needs to be displaced from the cache to
169      make room. Only at that point is it written back.
170
171      Write-Behind caching is similar to Write-Back caching, except that a
172      write won't fetch a cacheline into the cache if there isn't already
173      one there; it will write directly to memory instead.
174
175      Write-Through caching only fetches cachelines from memory on a
176      read. Writes always get written directly to memory. If the affected
177      cacheline is also in cache, it will be updated too.
178
179      The final option is to turn of caching entirely.
180
181      Note that not all CPUs support Write-Behind caching. If the CPU on
182      which the kernel is running doesn't, it'll fall back to Write-Back
183      caching.
184
185config FRV_DEFL_CACHE_WBACK
186    bool "Write-Back"
187
188config FRV_DEFL_CACHE_WBEHIND
189    bool "Write-Behind"
190
191config FRV_DEFL_CACHE_WTHRU
192    bool "Write-Through"
193
194config FRV_DEFL_CACHE_DISABLED
195    bool "Disabled"
196
197endchoice
198
199menu "CPU core support"
200
201config CPU_FR401
202    bool "Include FR401 core support"
203    depends on !MMU
204    default y
205    help
206      This enables support for the FR401, FR401A and FR403 CPUs
207
208config CPU_FR405
209    bool "Include FR405 core support"
210    depends on !MMU
211    default y
212    help
213      This enables support for the FR405 CPU
214
215config CPU_FR451
216    bool "Include FR451 core support"
217    default y
218    help
219      This enables support for the FR451 CPU
220
221config CPU_FR451_COMPILE
222    bool "Specifically compile for FR451 core"
223    depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
224    default y
225    help
226      This causes appropriate flags to be passed to the compiler to
227      optimise for the FR451 CPU
228
229config CPU_FR551
230    bool "Include FR551 core support"
231    depends on !MMU
232    default y
233    help
234      This enables support for the FR555 CPU
235
236config CPU_FR551_COMPILE
237    bool "Specifically compile for FR551 core"
238    depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
239    default y
240    help
241      This causes appropriate flags to be passed to the compiler to
242      optimise for the FR555 CPU
243
244config FRV_L1_CACHE_SHIFT
245    int
246    default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
247    default "6" if CPU_FR551
248
249endmenu
250
251choice
252    prompt "System support"
253    default MB93091_VDK
254
255config MB93091_VDK
256    bool "MB93091 CPU board with or without motherboard"
257
258config MB93093_PDK
259    bool "MB93093 PDK unit"
260
261endchoice
262
263if MB93091_VDK
264choice
265    prompt "Motherboard support"
266    default MB93090_MB00
267
268config MB93090_MB00
269    bool "Use the MB93090-MB00 motherboard"
270    help
271      Select this option if the MB93091 CPU board is going to be used with
272      a MB93090-MB00 VDK motherboard
273
274config MB93091_NO_MB
275    bool "Use standalone"
276    help
277      Select this option if the MB93091 CPU board is going to be used
278      without a motherboard
279
280endchoice
281endif
282
283config FUJITSU_MB93493
284    bool "MB93493 Multimedia chip"
285    help
286      Select this option if the MB93493 multimedia chip is going to be
287      used.
288
289choice
290    prompt "GP-Relative data support"
291    default GPREL_DATA_8
292    help
293      This option controls what data, if any, should be placed in the GP
294      relative data sections. Using this means that the compiler can
295      generate accesses to the data using GR16-relative addressing which
296      is faster than absolute instructions and saves space (2 instructions
297      per access).
298
299      However, the GPREL region is limited in size because the immediate
300      value used in the load and store instructions is limited to a 12-bit
301      signed number.
302
303      So if the linker starts complaining that accesses to GPREL data are
304      out of range, try changing this option from the default.
305
306      Note that modules will always be compiled with this feature disabled
307      as the module data will not be in range of the GP base address.
308
309config GPREL_DATA_8
310    bool "Put data objects of up to 8 bytes into GP-REL"
311
312config GPREL_DATA_4
313    bool "Put data objects of up to 4 bytes into GP-REL"
314
315config GPREL_DATA_NONE
316    bool "Don't use GP-REL"
317
318endchoice
319
320config FRV_ONCPU_SERIAL
321    bool "Use on-CPU serial ports"
322    select SERIAL_8250
323    default y
324
325config PCI
326    bool "Use PCI"
327    depends on MB93090_MB00
328    default y
329    help
330      Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
331      onboard. If you have one of these boards and you wish to use the PCI
332      facilities, say Y here.
333
334config RESERVE_DMA_COHERENT
335    bool "Reserve DMA coherent memory"
336    depends on PCI && !MMU
337    default y
338    help
339      Many PCI drivers require access to uncached memory for DMA device
340      communications (such as is done with some Ethernet buffer rings). If
341      a fully featured MMU is available, this can be done through page
342      table settings, but if not, a region has to be set aside and marked
343      with a special DAMPR register.
344
345      Setting this option causes uClinux to set aside a portion of the
346      available memory for use in this manner. The memory will then be
347      unavailable for normal kernel use.
348
349source "drivers/pci/Kconfig"
350
351source "drivers/pcmcia/Kconfig"
352
353#config MATH_EMULATION
354# bool "Math emulation support (EXPERIMENTAL)"
355# depends on EXPERIMENTAL
356# help
357# At some point in the future, this will cause floating-point math
358# instructions to be emulated by the kernel on machines that lack a
359# floating-point math coprocessor. Thrill-seekers and chronically
360# sleep-deprived psychotic hacker types can say Y now, everyone else
361# should probably wait a while.
362
363menu "Power management options"
364
365config ARCH_SUSPEND_POSSIBLE
366    def_bool y
367    depends on !SMP
368
369source kernel/power/Kconfig
370endmenu
371
372endmenu
373
374
375menu "Executable formats"
376
377source "fs/Kconfig.binfmt"
378
379endmenu
380
381source "net/Kconfig"
382
383source "drivers/Kconfig"
384
385source "fs/Kconfig"
386
387source "arch/frv/Kconfig.debug"
388
389source "security/Kconfig"
390
391source "crypto/Kconfig"
392
393source "lib/Kconfig"
394

Archive Download this file



interactive