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