arch/arm/Kconfig

   1 #
   2 # For a description of the syntax of this configuration file,
   3 # see Documentation/kbuild/kconfig-language.txt.
   4 #
   5
   6 mainmenu "Linux Kernel Configuration"
   7
   8 config ARM
   9         bool
  10         default y
  11         help
  12           The ARM series is a line of low-power-consumption RISC chip designs
  13           licensed by ARM ltd and targeted at embedded applications and
  14           handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
  15           manufactured, but  legacy ARM-based PC hardware remains popular in
  16           Europe.  There is an ARM Linux project with a web page at
  17           <http://www.arm.linux.org.uk/>.
  18
  19 config MMU
  20         bool
  21         default y
  22
  23 config EISA
  24         bool
  25         ---help---
  26           The Extended Industry Standard Architecture (EISA) bus was
  27           developed as an open alternative to the IBM MicroChannel bus.
  28
  29           The EISA bus provided some of the features of the IBM MicroChannel
  30           bus while maintaining backward compatibility with cards made for
  31           the older ISA bus.  The EISA bus saw limited use between 1988 and
  32           1995 when it was made obsolete by the PCI bus.
  33
  34           Say Y here if you are building a kernel for an EISA-based machine.
  35
  36           Otherwise, say N.
  37
  38 config SBUS
  39         bool
  40
  41 config MCA
  42         bool
  43         help
  44           MicroChannel Architecture is found in some IBM PS/2 machines and
  45           laptops.  It is a bus system similar to PCI or ISA. See
  46           <file:Documentation/mca.txt> (and especially the web page given
  47           there) before attempting to build an MCA bus kernel.
  48
  49 config UID16
  50         bool
  51         default y
  52
  53 config RWSEM_GENERIC_SPINLOCK
  54         bool
  55         default y
  56
  57 config RWSEM_XCHGADD_ALGORITHM
  58         bool
  59
  60 config GENERIC_CALIBRATE_DELAY
  61         bool
  62         default y
  63
  64 config GENERIC_BUST_SPINLOCK
  65         bool
  66
  67 config GENERIC_ISA_DMA
  68         bool
  69
  70 config GENERIC_IOMAP
  71         bool
  72         default y
  73
  74 config FIQ
  75         bool
  76
  77 source "init/Kconfig"
  78
  79 menu "System Type"
  80
  81 choice
  82         prompt "ARM system type"
  83         default ARCH_RPC
  84
  85 config ARCH_CLPS7500
  86         bool "Cirrus-CL-PS7500FE"
  87         select TIMER_ACORN
  88
  89 config ARCH_CLPS711X
  90         bool "CLPS711x/EP721x-based"
  91
  92 config ARCH_CO285
  93         bool "Co-EBSA285"
  94         select FOOTBRIDGE
  95         select FOOTBRIDGE_ADDIN
  96
  97 config ARCH_EBSA110
  98         bool "EBSA-110"
  99         help
 100           This is an evaluation board for the StrongARM processor available
 101           from Digital. It has limited hardware on-board, including an onboard
 102           Ethernet interface, two PCMCIA sockets, two serial ports and a
 103           parallel port.
 104
 105 config ARCH_CAMELOT
 106         bool "Epxa10db"
 107         help
 108           This enables support for Altera's Excalibur XA10 development board.
 109           If you would like to build your kernel to run on one of these boards
 110           then you must say 'Y' here. Otherwise say 'N'
 111
 112 config ARCH_FOOTBRIDGE
 113         bool "FootBridge"
 114         select FOOTBRIDGE
 115
 116 config ARCH_INTEGRATOR
 117         bool "Integrator"
 118         select ARM_AMBA
 119         select ICST525
 120
 121 config ARCH_IOP3XX
 122         bool "IOP3xx-based"
 123
 124 config ARCH_IXP4XX
 125         bool "IXP4xx-based"
 126         select DMABOUNCE
 127
 128 config ARCH_IXP2000
 129         bool "IXP2400/2800-based"
 130
 131 config ARCH_L7200
 132         bool "LinkUp-L7200"
 133         select FIQ
 134         help
 135           Say Y here if you intend to run this kernel on a LinkUp Systems
 136           L7200 Software Development Board which uses an ARM720T processor.
 137           Information on this board can be obtained at:
 138
 139           <http://www.linkupsys.com/>
 140
 141           If you have any questions or comments about the Linux kernel port
 142           to this board, send e-mail to <sjhill@cotw.com>.
 143
 144 config ARCH_PXA
 145         bool "PXA2xx-based"
 146
 147 config ARCH_RPC
 148         bool "RiscPC"
 149         select ARCH_ACORN
 150         select FIQ
 151         select TIMER_ACORN
 152         help
 153           On the Acorn Risc-PC, Linux can support the internal IDE disk and
 154           CD-ROM interface, serial and parallel port, and the floppy drive.
 155
 156 config ARCH_SA1100
 157         bool "SA1100-based"
 158
 159 config ARCH_S3C2410
 160         bool "Samsung S3C2410"
 161         help
 162           Samsung S3C2410X CPU based systems, such as the Simtec Electronics
 163           BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
 164           the Samsung SMDK2410 development board (and derviatives).
 165
 166 config ARCH_SHARK
 167         bool "Shark"
 168
 169 config ARCH_LH7A40X
 170         bool "Sharp LH7A40X"
 171         help
 172           Say Y here for systems based on one of the Sharp LH7A40X
 173           System on a Chip processors.  These CPUs include an ARM922T
 174           core with a wide array of integrated devices for
 175           hand-held and low-power applications.
 176
 177 config ARCH_OMAP
 178         bool "TI OMAP"
 179
 180 config ARCH_VERSATILE
 181         bool "Versatile"
 182         select ARM_AMBA
 183         select ICST307
 184         help
 185           This enables support for ARM Ltd Versatile board.
 186
 187 config ARCH_IMX
 188         bool "IMX"
 189
 190 config ARCH_H720X
 191         bool "Hynix-HMS720x-based"
 192         help
 193           This enables support for systems based on the Hynix HMS720x
 194
 195 endchoice
 196
 197 source "arch/arm/mach-clps711x/Kconfig"
 198
 199 source "arch/arm/mach-epxa10db/Kconfig"
 200
 201 source "arch/arm/mach-footbridge/Kconfig"
 202
 203 source "arch/arm/mach-integrator/Kconfig"
 204
 205 source "arch/arm/mach-iop3xx/Kconfig"
 206
 207 source "arch/arm/mach-ixp4xx/Kconfig"
 208
 209 source "arch/arm/mach-ixp2000/Kconfig"
 210
 211 source "arch/arm/mach-pxa/Kconfig"
 212
 213 source "arch/arm/mach-sa1100/Kconfig"
 214
 215 source "arch/arm/mach-omap/Kconfig"
 216
 217 source "arch/arm/mach-s3c2410/Kconfig"
 218
 219 source "arch/arm/mach-lh7a40x/Kconfig"
 220
 221 source "arch/arm/mach-imx/Kconfig"
 222
 223 source "arch/arm/mach-h720x/Kconfig"
 224
 225 source "arch/arm/mach-versatile/Kconfig"
 226
 227 # Definitions to make life easier
 228 config ARCH_ACORN
 229         bool
 230
 231 source arch/arm/mm/Kconfig
 232
 233 #  bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
 234 config XSCALE_PMU
 235         bool
 236         depends on CPU_XSCALE && !XSCALE_PMU_TIMER
 237         default y
 238
 239 endmenu
 240
 241 source "arch/arm/common/Kconfig"
 242
 243 config FORCE_MAX_ZONEORDER
 244         int
 245         depends on SA1111
 246         default "9"
 247
 248 menu "Bus support"
 249
 250 config ARM_AMBA
 251         bool
 252
 253 config ISA
 254         bool
 255         depends on FOOTBRIDGE_HOST || ARCH_SHARK || ARCH_CLPS7500 || ARCH_EBSA110 || ARCH_CDB89712 || ARCH_EDB7211 || ARCH_SA1100 || ARCH_MX1ADS
 256         default y
 257         help
 258           Find out whether you have ISA slots on your motherboard.  ISA is the
 259           name of a bus system, i.e. the way the CPU talks to the other stuff
 260           inside your box.  Other bus systems are PCI, EISA, MicroChannel
 261           (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
 262           newer boards don't support it.  If you have ISA, say Y, otherwise N.
 263
 264 config ISA_DMA
 265         bool
 266         depends on FOOTBRIDGE_HOST || ARCH_SHARK
 267         default y
 268
 269 config ISA_DMA_API
 270         bool
 271         default y
 272
 273 config PCI
 274         bool "PCI support" if ARCH_INTEGRATOR_AP
 275         default y if ARCH_SHARK || FOOTBRIDGE_HOST || ARCH_IOP3XX || ARCH_IXP4XX || ARCH_IXP2000
 276         help
 277           Find out whether you have a PCI motherboard. PCI is the name of a
 278           bus system, i.e. the way the CPU talks to the other stuff inside
 279           your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
 280           VESA. If you have PCI, say Y, otherwise N.
 281
 282           The PCI-HOWTO, available from
 283           <http://www.tldp.org/docs.html#howto>, contains valuable
 284           information about which PCI hardware does work under Linux and which
 285           doesn't.
 286
 287 # Select the host bridge type
 288 config PCI_HOST_VIA82C505
 289         bool
 290         depends on PCI && ARCH_SHARK
 291         default y
 292
 293 source "drivers/pci/Kconfig"
 294
 295 source "drivers/pcmcia/Kconfig"
 296
 297 endmenu
 298
 299 menu "Kernel Features"
 300
 301 config SMP
 302         bool "Symmetric Multi-Processing (EXPERIMENTAL)"
 303         depends on EXPERIMENTAL && n
 304         help
 305           This enables support for systems with more than one CPU. If you have
 306           a system with only one CPU, like most personal computers, say N. If
 307           you have a system with more than one CPU, say Y.
 308
 309           If you say N here, the kernel will run on single and multiprocessor
 310           machines, but will use only one CPU of a multiprocessor machine. If
 311           you say Y here, the kernel will run on many, but not all, single
 312           processor machines. On a single processor machine, the kernel will
 313           run faster if you say N here.
 314
 315           See also the <file:Documentation/smp.tex>,
 316           <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
 317           <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
 318           <http://www.linuxdoc.org/docs.html#howto>.
 319
 320           If you don't know what to do here, say N.
 321
 322 config NR_CPUS
 323         int "Maximum number of CPUs (2-32)"
 324         range 2 32
 325         depends on SMP
 326         default "4"
 327
 328 config PREEMPT
 329         bool "Preemptible Kernel (EXPERIMENTAL)"
 330         depends on EXPERIMENTAL
 331         help
 332           This option reduces the latency of the kernel when reacting to
 333           real-time or interactive events by allowing a low priority process to
 334           be preempted even if it is in kernel mode executing a system call.
 335           This allows applications to run more reliably even when the system is
 336           under load.
 337
 338           Say Y here if you are building a kernel for a desktop, embedded
 339           or real-time system.  Say N if you are unsure.
 340
 341 config DISCONTIGMEM
 342         bool
 343         depends on ARCH_EDB7211 || ARCH_SA1100 || (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
 344         default y
 345         help
 346           Say Y to support efficient handling of discontiguous physical memory,
 347           for architectures which are either NUMA (Non-Uniform Memory Access)
 348           or have huge holes in the physical address space for other reasons.
 349           See <file:Documentation/vm/numa> for more.
 350
 351 config LEDS
 352         bool "Timer and CPU usage LEDs"
 353         depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
 354                    ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
 355                    ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
 356                    ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
 357                    ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
 358         help
 359           If you say Y here, the LEDs on your machine will be used
 360           to provide useful information about your current system status.
 361
 362           If you are compiling a kernel for a NetWinder or EBSA-285, you will
 363           be able to select which LEDs are active using the options below. If
 364           you are compiling a kernel for the EBSA-110 or the LART however, the
 365           red LED will simply flash regularly to indicate that the system is
 366           still functional. It is safe to say Y here if you have a CATS
 367           system, but the driver will do nothing.
 368
 369 config LEDS_TIMER
 370         bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
 371                             MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
 372         depends on LEDS
 373         default y if ARCH_EBSA110
 374         help
 375           If you say Y here, one of the system LEDs (the green one on the
 376           NetWinder, the amber one on the EBSA285, or the red one on the LART)
 377           will flash regularly to indicate that the system is still
 378           operational. This is mainly useful to kernel hackers who are
 379           debugging unstable kernels.
 380
 381           The LART uses the same LED for both Timer LED and CPU usage LED
 382           functions. You may choose to use both, but the Timer LED function
 383           will overrule the CPU usage LED.
 384
 385 config LEDS_CPU
 386         bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
 387                         !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
 388         depends on LEDS
 389         help
 390           If you say Y here, the red LED will be used to give a good real
 391           time indication of CPU usage, by lighting whenever the idle task
 392           is not currently executing.
 393
 394           The LART uses the same LED for both Timer LED and CPU usage LED
 395           functions. You may choose to use both, but the Timer LED function
 396           will overrule the CPU usage LED.
 397
 398 config ALIGNMENT_TRAP
 399         bool
 400         default y if !ARCH_EBSA110
 401         help
 402           ARM processors can not fetch/store information which is not
 403           naturally aligned on the bus, i.e., a 4 byte fetch must start at an
 404           address divisible by 4. On 32-bit ARM processors, these non-aligned
 405           fetch/store instructions will be emulated in software if you say
 406           here, which has a severe performance impact. This is necessary for
 407           correct operation of some network protocols. With an IP-only
 408           configuration it is safe to say N, otherwise say Y.
 409
 410 endmenu
 411
 412 menu "Boot options"
 413
 414 # Compressed boot loader in ROM.  Yes, we really want to ask about
 415 # TEXT and BSS so we preserve their values in the config files.
 416 config ZBOOT_ROM_TEXT
 417         hex "Compressed ROM boot loader base address"
 418         default "0"
 419         help
 420           The physical address at which the ROM-able zImage is to be
 421           placed in the target.  Platforms which normally make use of
 422           ROM-able zImage formats normally set this to a suitable
 423           value in their defconfig file.
 424
 425           If ZBOOT_ROM is not enabled, this has no effect.
 426
 427 config ZBOOT_ROM_BSS
 428         hex "Compressed ROM boot loader BSS address"
 429         default "0"
 430         help
 431           The base address of 64KiB of read/write memory in the target
 432           for the ROM-able zImage, which must be available while the
 433           decompressor is running.  Platforms which normally make use of
 434           ROM-able zImage formats normally set this to a suitable
 435           value in their defconfig file.
 436
 437           If ZBOOT_ROM is not enabled, this has no effect.
 438
 439 config ZBOOT_ROM
 440         bool "Compressed boot loader in ROM/flash"
 441         depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
 442         help
 443           Say Y here if you intend to execute your compressed kernel image
 444           (zImage) directly from ROM or flash.  If unsure, say N.
 445
 446 config CMDLINE
 447         string "Default kernel command string"
 448         default ""
 449         help
 450           On some architectures (EBSA110 and CATS), there is currently no way
 451           for the boot loader to pass arguments to the kernel. For these
 452           architectures, you should supply some command-line options at build
 453           time by entering them here. As a minimum, you should specify the
 454           memory size and the root device (e.g., mem=64M root=/dev/nfs).
 455
 456 config XIP_KERNEL
 457         bool "Kernel Execute-In-Place from ROM"
 458         depends on !ZBOOT_ROM
 459         help
 460           Execute-In-Place allows the kernel to run from non-volatile storage
 461           directly addressable by the CPU, such as NOR flash. This saves RAM
 462           space since the text section of the kernel is not loaded from flash
 463           to RAM.  Read-write sections, such as the data section and stack,
 464           are still copied to RAM.  The XIP kernel is not compressed since
 465           it has to run directly from flash, so it will take more space to
 466           store it.  The flash address used to link the kernel object files,
 467           and for storing it, is configuration dependent. Therefore, if you
 468           say Y here, you must know the proper physical address where to
 469           store the kernel image depending on your own flash memory usage.
 470
 471           Also note that the make target becomes "make xipImage" rather than
 472           "make zImage" or "make Image".  The final kernel binary to put in
 473           ROM memory will be arch/arm/boot/xipImage.
 474
 475           If unsure, say N.
 476
 477 config XIP_PHYS_ADDR
 478         hex "XIP Kernel Physical Location"
 479         depends on XIP_KERNEL
 480         default "0x00080000"
 481         help
 482           This is the physical address in your flash memory the kernel will
 483           be linked for and stored to.  This address is dependent on your
 484           own flash usage.
 485
 486 endmenu
 487
 488 if (ARCH_SA1100 || ARCH_INTEGRATOR)
 489
 490 menu "CPU Frequency scaling"
 491
 492 source "drivers/cpufreq/Kconfig"
 493
 494 config CPU_FREQ_SA1100
 495         bool
 496         depends on CPU_FREQ && (SA1100_LART || SA1100_PLEB)
 497         default y
 498
 499 config CPU_FREQ_SA1110
 500         bool
 501         depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
 502         default y
 503
 504 config CPU_FREQ_INTEGRATOR
 505         tristate "CPUfreq driver for ARM Integrator CPUs"
 506         depends on ARCH_INTEGRATOR && CPU_FREQ
 507         default y
 508         help
 509           This enables the CPUfreq driver for ARM Integrator CPUs.
 510
 511           For details, take a look at <file:Documentation/cpu-freq>.
 512
 513           If in doubt, say Y.
 514
 515 endmenu
 516
 517 endif
 518
 519 menu "Floating point emulation"
 520
 521 comment "At least one emulation must be selected"
 522
 523 config FPE_NWFPE
 524         bool "NWFPE math emulation"
 525         ---help---
 526           Say Y to include the NWFPE floating point emulator in the kernel.
 527           This is necessary to run most binaries. Linux does not currently
 528           support floating point hardware so you need to say Y here even if
 529           your machine has an FPA or floating point co-processor podule.
 530
 531           You may say N here if you are going to load the Acorn FPEmulator
 532           early in the bootup.
 533
 534 config FPE_NWFPE_XP
 535         bool "Support extended precision"
 536         depends on FPE_NWFPE && !CPU_BIG_ENDIAN
 537         help
 538           Say Y to include 80-bit support in the kernel floating-point
 539           emulator.  Otherwise, only 32 and 64-bit support is compiled in.
 540           Note that gcc does not generate 80-bit operations by default,
 541           so in most cases this option only enlarges the size of the
 542           floating point emulator without any good reason.
 543
 544           You almost surely want to say N here.
 545
 546 config FPE_FASTFPE
 547         bool "FastFPE math emulation (EXPERIMENTAL)"
 548         depends on !CPU_32v3 && EXPERIMENTAL
 549         ---help---
 550           Say Y here to include the FAST floating point emulator in the kernel.
 551           This is an experimental much faster emulator which now also has full
 552           precision for the mantissa.  It does not support any exceptions.
 553           It is very simple, and approximately 3-6 times faster than NWFPE.
 554
 555           It should be sufficient for most programs.  It may be not suitable
 556           for scientific calculations, but you have to check this for yourself.
 557           If you do not feel you need a faster FP emulation you should better
 558           choose NWFPE.
 559
 560 config VFP
 561         bool "VFP-format floating point maths"
 562         depends on CPU_V6 || CPU_ARM926T
 563         help
 564           Say Y to include VFP support code in the kernel. This is needed
 565           if your hardware includes a VFP unit.
 566
 567           Please see <file:Documentation/arm/VFP/release-notes.txt> for
 568           release notes and additional status information.
 569
 570           Say N if your target does not have VFP hardware.
 571
 572 endmenu
 573
 574 menu "Userspace binary formats"
 575
 576 source "fs/Kconfig.binfmt"
 577
 578 config ARTHUR
 579         tristate "RISC OS personality"
 580         help
 581           Say Y here to include the kernel code necessary if you want to run
 582           Acorn RISC OS/Arthur binaries under Linux. This code is still very
 583           experimental; if this sounds frightening, say N and sleep in peace.
 584           You can also say M here to compile this support as a module (which
 585           will be called arthur).
 586
 587 endmenu
 588
 589 menu "Power management options"
 590
 591 config PM
 592         bool "Power Management support"
 593         ---help---
 594           "Power Management" means that parts of your computer are shut
 595           off or put into a power conserving "sleep" mode if they are not
 596           being used.  There are two competing standards for doing this: APM
 597           and ACPI.  If you want to use either one, say Y here and then also
 598           to the requisite support below.
 599
 600           Power Management is most important for battery powered laptop
 601           computers; if you have a laptop, check out the Linux Laptop home
 602           page on the WWW at <http://www.linux-on-laptops.com/> or
 603           Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
 604           and the Battery Powered Linux mini-HOWTO, available from
 605           <http://www.tldp.org/docs.html#howto>.
 606
 607           Note that, even if you say N here, Linux on the x86 architecture
 608           will issue the hlt instruction if nothing is to be done, thereby
 609           sending the processor to sleep and saving power.
 610
 611 config APM
 612         tristate "Advanced Power Management Emulation"
 613         depends on PM
 614         ---help---
 615           APM is a BIOS specification for saving power using several different
 616           techniques. This is mostly useful for battery powered laptops with
 617           APM compliant BIOSes. If you say Y here, the system time will be
 618           reset after a RESUME operation, the /proc/apm device will provide
 619           battery status information, and user-space programs will receive
 620           notification of APM "events" (e.g. battery status change).
 621
 622           If you select "Y" here, you can disable actual use of the APM
 623           BIOS by passing the "apm=off" option to the kernel at boot time.
 624
 625           Note that the APM support is almost completely disabled for
 626           machines with more than one CPU.
 627
 628           In order to use APM, you will need supporting software. For location
 629           and more information, read <file:Documentation/pm.txt> and the
 630           Battery Powered Linux mini-HOWTO, available from
 631           <http://www.tldp.org/docs.html#howto>.
 632
 633           This driver does not spin down disk drives (see the hdparm(8)
 634           manpage ("man 8 hdparm") for that), and it doesn't turn off
 635           VESA-compliant "green" monitors.
 636
 637           This driver does not support the TI 4000M TravelMate and the ACER
 638           486/DX4/75 because they don't have compliant BIOSes. Many "green"
 639           desktop machines also don't have compliant BIOSes, and this driver
 640           may cause those machines to panic during the boot phase.
 641
 642           Generally, if you don't have a battery in your machine, there isn't
 643           much point in using this driver and you should say N. If you get
 644           random kernel OOPSes or reboots that don't seem to be related to
 645           anything, try disabling/enabling this option (or disabling/enabling
 646           APM in your BIOS).
 647
 648           Some other things you should try when experiencing seemingly random,
 649           "weird" problems:
 650
 651           1) make sure that you have enough swap space and that it is
 652           enabled.
 653           2) pass the "no-hlt" option to the kernel
 654           3) switch on floating point emulation in the kernel and pass
 655           the "no387" option to the kernel
 656           4) pass the "floppy=nodma" option to the kernel
 657           5) pass the "mem=4M" option to the kernel (thereby disabling
 658           all but the first 4 MB of RAM)
 659           6) make sure that the CPU is not over clocked.
 660           7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
 661           8) disable the cache from your BIOS settings
 662           9) install a fan for the video card or exchange video RAM
 663           10) install a better fan for the CPU
 664           11) exchange RAM chips
 665           12) exchange the motherboard.
 666
 667           To compile this driver as a module, choose M here: the
 668           module will be called apm.
 669
 670 endmenu
 671
 672 menu "Device Drivers"
 673
 674 source "drivers/base/Kconfig"
 675
 676 if ALIGNMENT_TRAP
 677 source "drivers/mtd/Kconfig"
 678 endif
 679
 680 source "drivers/parport/Kconfig"
 681
 682 source "drivers/pnp/Kconfig"
 683
 684 source "drivers/block/Kconfig"
 685
 686 source "drivers/acorn/block/Kconfig"
 687
 688 if ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
 689 source "drivers/ide/Kconfig"
 690 endif
 691
 692 source "drivers/scsi/Kconfig"
 693
 694 source "drivers/md/Kconfig"
 695
 696 source "drivers/message/fusion/Kconfig"
 697
 698 source "drivers/ieee1394/Kconfig"
 699
 700 source "drivers/message/i2o/Kconfig"
 701
 702 source "net/Kconfig"
 703
 704 source "drivers/isdn/Kconfig"
 705
 706 # input before char - char/joystick depends on it. As does USB.
 707
 708 source "drivers/input/Kconfig"
 709
 710 source "drivers/char/Kconfig"
 711
 712 source "drivers/i2c/Kconfig"
 713
 714 #source "drivers/l3/Kconfig"
 715
 716 source "drivers/misc/Kconfig"
 717
 718 source "drivers/media/Kconfig"
 719
 720 source "drivers/video/Kconfig"
 721
 722 source "sound/Kconfig"
 723
 724 source "drivers/usb/Kconfig"
 725
 726 source "drivers/mmc/Kconfig"
 727
 728 endmenu
 729
 730 source "fs/Kconfig"
 731
 732 source "arch/arm/oprofile/Kconfig"
 733
 734 source "arch/arm/Kconfig.debug"
 735
 736 source "security/Kconfig"
 737
 738 source "crypto/Kconfig"
 739
 740 source "lib/Kconfig"