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 69source "kernel/Kconfig.freezer" 70 71 72menu "Fujitsu FR-V system setup" 73 74config MMU 75 bool "MMU support" 76 help 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 80 featured MMU. 81 82config FRV_OUTOFLINE_ATOMIC_OPS 83 bool "Out-of-line the FRV atomic operations" 84 default n 85 help 86 Setting this option causes the FR-V atomic operations to be mostly 87 implemented out-of-line. 88 89 See Documentation/frv/atomic-ops.txt for more information. 90 91config HIGHMEM 92 bool "High memory support" 93 depends on MMU 94 default y 95 help 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 99 else must be kmapped. 100 101 The arch is, however, capable of supporting up to 3GB of SDRAM. 102 103config HIGHPTE 104 bool "Allocate page tables in highmem" 105 depends on HIGHMEM 106 default y 107 help 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. 111 112source "mm/Kconfig" 113 114choice 115 prompt "uClinux kernel load address" 116 depends on !MMU 117 default UCPAGE_OFFSET_C0000000 118 help 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 123 the I/O region. 124 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. 127 128config UCPAGE_OFFSET_20000000 129 bool "0x20000000" 130 131config UCPAGE_OFFSET_40000000 132 bool "0x40000000" 133 134config UCPAGE_OFFSET_60000000 135 bool "0x60000000" 136 137config UCPAGE_OFFSET_80000000 138 bool "0x80000000" 139 140config UCPAGE_OFFSET_A0000000 141 bool "0xA0000000" 142 143config UCPAGE_OFFSET_C0000000 144 bool "0xC0000000 (Recommended)" 145 146endchoice 147 148config PAGE_OFFSET 149 hex 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 155 default 0xC0000000 156 157config PROTECT_KERNEL 158 bool "Protect core kernel against userspace" 159 depends on !MMU 160 default y 161 help 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. 165 166choice 167 prompt "CPU Caching mode" 168 default FRV_DEFL_CACHE_WBACK 169 help 170 This option determines the default caching mode for the kernel. 171 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. 177 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. 181 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. 185 186 The final option is to turn of caching entirely. 187 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 190 caching. 191 192config FRV_DEFL_CACHE_WBACK 193 bool "Write-Back" 194 195config FRV_DEFL_CACHE_WBEHIND 196 bool "Write-Behind" 197 198config FRV_DEFL_CACHE_WTHRU 199 bool "Write-Through" 200 201config FRV_DEFL_CACHE_DISABLED 202 bool "Disabled" 203 204endchoice 205 206menu "CPU core support" 207 208config CPU_FR401 209 bool "Include FR401 core support" 210 depends on !MMU 211 default y 212 help 213 This enables support for the FR401, FR401A and FR403 CPUs 214 215config CPU_FR405 216 bool "Include FR405 core support" 217 depends on !MMU 218 default y 219 help 220 This enables support for the FR405 CPU 221 222config CPU_FR451 223 bool "Include FR451 core support" 224 default y 225 help 226 This enables support for the FR451 CPU 227 228config CPU_FR451_COMPILE 229 bool "Specifically compile for FR451 core" 230 depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551 231 default y 232 help 233 This causes appropriate flags to be passed to the compiler to 234 optimise for the FR451 CPU 235 236config CPU_FR551 237 bool "Include FR551 core support" 238 depends on !MMU 239 default y 240 help 241 This enables support for the FR555 CPU 242 243config CPU_FR551_COMPILE 244 bool "Specifically compile for FR551 core" 245 depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451 246 default y 247 help 248 This causes appropriate flags to be passed to the compiler to 249 optimise for the FR555 CPU 250 251config FRV_L1_CACHE_SHIFT 252 int 253 default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451 254 default "6" if CPU_FR551 255 256endmenu 257 258choice 259 prompt "System support" 260 default MB93091_VDK 261 262config MB93091_VDK 263 bool "MB93091 CPU board with or without motherboard" 264 265config MB93093_PDK 266 bool "MB93093 PDK unit" 267 268endchoice 269 270if MB93091_VDK 271choice 272 prompt "Motherboard support" 273 default MB93090_MB00 274 275config MB93090_MB00 276 bool "Use the MB93090-MB00 motherboard" 277 help 278 Select this option if the MB93091 CPU board is going to be used with 279 a MB93090-MB00 VDK motherboard 280 281config MB93091_NO_MB 282 bool "Use standalone" 283 help 284 Select this option if the MB93091 CPU board is going to be used 285 without a motherboard 286 287endchoice 288endif 289 290config FUJITSU_MB93493 291 bool "MB93493 Multimedia chip" 292 help 293 Select this option if the MB93493 multimedia chip is going to be 294 used. 295 296choice 297 prompt "GP-Relative data support" 298 default GPREL_DATA_8 299 help 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 304 per access). 305 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 308 signed number. 309 310 So if the linker starts complaining that accesses to GPREL data are 311 out of range, try changing this option from the default. 312 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. 315 316config GPREL_DATA_8 317 bool "Put data objects of up to 8 bytes into GP-REL" 318 319config GPREL_DATA_4 320 bool "Put data objects of up to 4 bytes into GP-REL" 321 322config GPREL_DATA_NONE 323 bool "Don't use GP-REL" 324 325endchoice 326 327config FRV_ONCPU_SERIAL 328 bool "Use on-CPU serial ports" 329 select SERIAL_8250 330 default y 331 332config PCI 333 bool "Use PCI" 334 depends on MB93090_MB00 335 default y 336 help 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. 340 341config RESERVE_DMA_COHERENT 342 bool "Reserve DMA coherent memory" 343 depends on PCI && !MMU 344 default y 345 help 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. 351 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. 355 356source "drivers/pci/Kconfig" 357 358source "drivers/pcmcia/Kconfig" 359 360#config MATH_EMULATION 361# bool "Math emulation support (EXPERIMENTAL)" 362# depends on EXPERIMENTAL 363# help 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. 369 370menu "Power management options" 371 372config ARCH_SUSPEND_POSSIBLE 373 def_bool y 374 depends on !SMP 375 376source kernel/power/Kconfig 377endmenu 378 379endmenu 380 381 382menu "Executable formats" 383 384source "fs/Kconfig.binfmt" 385 386endmenu 387 388source "net/Kconfig" 389 390source "drivers/Kconfig" 391 392source "fs/Kconfig" 393 394source "arch/frv/Kconfig.debug" 395 396source "security/Kconfig" 397 398source "crypto/Kconfig" 399 400source "lib/Kconfig" 401