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