arch/frv/Kconfig

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