2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
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/>.
26 The Extended Industry Standard Architecture (EISA) bus was
27 developed as an open alternative to the IBM MicroChannel bus.
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.
34 Say Y here if you are building a kernel for an EISA-based machine.
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.
53 config RWSEM_GENERIC_SPINLOCK
57 config RWSEM_XCHGADD_ALGORITHM
60 config GENERIC_CALIBRATE_DELAY
64 config GENERIC_BUST_SPINLOCK
67 config GENERIC_ISA_DMA
78 prompt "ARM system type"
82 bool "Cirrus-CL-PS7500FE"
87 bool "CLPS711x/EP721x-based"
92 select FOOTBRIDGE_ADDIN
98 This is an evaluation board for the StrongARM processor available
99 from Digital. It has limited hardware on-board, including an onboard
100 Ethernet interface, two PCMCIA sockets, two serial ports and a
106 This enables support for Altera's Excalibur XA10 development board.
107 If you would like to build your kernel to run on one of these boards
108 then you must say 'Y' here. Otherwise say 'N'
110 config ARCH_FOOTBRIDGE
114 config ARCH_INTEGRATOR
129 bool "IXP2400/2800-based"
136 Say Y here if you intend to run this kernel on a LinkUp Systems
137 L7200 Software Development Board which uses an ARM720T processor.
138 Information on this board can be obtained at:
140 <http://www.linkupsys.com/>
142 If you have any questions or comments about the Linux kernel port
143 to this board, send e-mail to <sjhill@cotw.com>.
154 On the Acorn Risc-PC, Linux can support the internal IDE disk and
155 CD-ROM interface, serial and parallel port, and the floppy drive.
160 select ARCH_DISCONTIGMEM_ENABLE
163 bool "Samsung S3C2410"
165 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
166 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
167 the Samsung SMDK2410 development board (and derviatives).
178 Say Y here for systems based on one of the Sharp LH7A40X
179 System on a Chip processors. These CPUs include an ARM922T
180 core with a wide array of integrated devices for
181 hand-held and low-power applications.
186 config ARCH_VERSATILE
191 This enables support for ARM Ltd Versatile board.
197 bool "Hynix-HMS720x-based"
199 This enables support for systems based on the Hynix HMS720x
202 bool "Agilent AAEC-2000 based"
204 This enables support for systems based on the Agilent AAEC-2000
208 source "arch/arm/mach-clps711x/Kconfig"
210 source "arch/arm/mach-epxa10db/Kconfig"
212 source "arch/arm/mach-footbridge/Kconfig"
214 source "arch/arm/mach-integrator/Kconfig"
216 source "arch/arm/mach-iop3xx/Kconfig"
218 source "arch/arm/mach-ixp4xx/Kconfig"
220 source "arch/arm/mach-ixp2000/Kconfig"
222 source "arch/arm/mach-pxa/Kconfig"
224 source "arch/arm/mach-sa1100/Kconfig"
226 source "arch/arm/mach-omap/Kconfig"
228 source "arch/arm/mach-s3c2410/Kconfig"
230 source "arch/arm/mach-lh7a40x/Kconfig"
232 source "arch/arm/mach-imx/Kconfig"
234 source "arch/arm/mach-h720x/Kconfig"
236 source "arch/arm/mach-versatile/Kconfig"
238 source "arch/arm/mach-aaec2000/Kconfig"
240 # Definitions to make life easier
244 source arch/arm/mm/Kconfig
246 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
249 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
254 source "arch/arm/common/Kconfig"
256 config FORCE_MAX_ZONEORDER
269 Find out whether you have ISA slots on your motherboard. ISA is the
270 name of a bus system, i.e. the way the CPU talks to the other stuff
271 inside your box. Other bus systems are PCI, EISA, MicroChannel
272 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
273 newer boards don't support it. If you have ISA, say Y, otherwise N.
283 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
285 Find out whether you have a PCI motherboard. PCI is the name of a
286 bus system, i.e. the way the CPU talks to the other stuff inside
287 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
288 VESA. If you have PCI, say Y, otherwise N.
290 The PCI-HOWTO, available from
291 <http://www.tldp.org/docs.html#howto>, contains valuable
292 information about which PCI hardware does work under Linux and which
295 # Select the host bridge type
296 config PCI_HOST_VIA82C505
298 depends on PCI && ARCH_SHARK
301 source "drivers/pci/Kconfig"
303 source "drivers/pcmcia/Kconfig"
307 menu "Kernel Features"
310 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
311 depends on EXPERIMENTAL #&& n
313 This enables support for systems with more than one CPU. If you have
314 a system with only one CPU, like most personal computers, say N. If
315 you have a system with more than one CPU, say Y.
317 If you say N here, the kernel will run on single and multiprocessor
318 machines, but will use only one CPU of a multiprocessor machine. If
319 you say Y here, the kernel will run on many, but not all, single
320 processor machines. On a single processor machine, the kernel will
321 run faster if you say N here.
323 See also the <file:Documentation/smp.tex>,
324 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
325 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
326 <http://www.linuxdoc.org/docs.html#howto>.
328 If you don't know what to do here, say N.
331 int "Maximum number of CPUs (2-32)"
337 bool "Preemptible Kernel (EXPERIMENTAL)"
338 depends on EXPERIMENTAL
340 This option reduces the latency of the kernel when reacting to
341 real-time or interactive events by allowing a low priority process to
342 be preempted even if it is in kernel mode executing a system call.
343 This allows applications to run more reliably even when the system is
346 Say Y here if you are building a kernel for a desktop, embedded
347 or real-time system. Say N if you are unsure.
350 bool "Dynamic tick timer"
352 Select this option if you want to disable continuous timer ticks
353 and have them programmed to occur as required. This option saves
354 power as the system can remain in idle state for longer.
356 By default dynamic tick is disabled during the boot, and can be
357 manually enabled with:
359 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
361 Alternatively, if you want dynamic tick automatically enabled
362 during boot, pass "dyntick=enable" via the kernel command string.
364 config ARCH_DISCONTIGMEM_ENABLE
366 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
368 Say Y to support efficient handling of discontiguous physical memory,
369 for architectures which are either NUMA (Non-Uniform Memory Access)
370 or have huge holes in the physical address space for other reasons.
371 See <file:Documentation/vm/numa> for more.
376 bool "Timer and CPU usage LEDs"
377 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
378 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
379 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
380 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
381 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
383 If you say Y here, the LEDs on your machine will be used
384 to provide useful information about your current system status.
386 If you are compiling a kernel for a NetWinder or EBSA-285, you will
387 be able to select which LEDs are active using the options below. If
388 you are compiling a kernel for the EBSA-110 or the LART however, the
389 red LED will simply flash regularly to indicate that the system is
390 still functional. It is safe to say Y here if you have a CATS
391 system, but the driver will do nothing.
394 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
395 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
397 default y if ARCH_EBSA110
399 If you say Y here, one of the system LEDs (the green one on the
400 NetWinder, the amber one on the EBSA285, or the red one on the LART)
401 will flash regularly to indicate that the system is still
402 operational. This is mainly useful to kernel hackers who are
403 debugging unstable kernels.
405 The LART uses the same LED for both Timer LED and CPU usage LED
406 functions. You may choose to use both, but the Timer LED function
407 will overrule the CPU usage LED.
410 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
411 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
414 If you say Y here, the red LED will be used to give a good real
415 time indication of CPU usage, by lighting whenever the idle task
416 is not currently executing.
418 The LART uses the same LED for both Timer LED and CPU usage LED
419 functions. You may choose to use both, but the Timer LED function
420 will overrule the CPU usage LED.
422 config ALIGNMENT_TRAP
424 default y if !ARCH_EBSA110
426 ARM processors can not fetch/store information which is not
427 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
428 address divisible by 4. On 32-bit ARM processors, these non-aligned
429 fetch/store instructions will be emulated in software if you say
430 here, which has a severe performance impact. This is necessary for
431 correct operation of some network protocols. With an IP-only
432 configuration it is safe to say N, otherwise say Y.
438 # Compressed boot loader in ROM. Yes, we really want to ask about
439 # TEXT and BSS so we preserve their values in the config files.
440 config ZBOOT_ROM_TEXT
441 hex "Compressed ROM boot loader base address"
444 The physical address at which the ROM-able zImage is to be
445 placed in the target. Platforms which normally make use of
446 ROM-able zImage formats normally set this to a suitable
447 value in their defconfig file.
449 If ZBOOT_ROM is not enabled, this has no effect.
452 hex "Compressed ROM boot loader BSS address"
455 The base address of 64KiB of read/write memory in the target
456 for the ROM-able zImage, which must be available while the
457 decompressor is running. Platforms which normally make use of
458 ROM-able zImage formats normally set this to a suitable
459 value in their defconfig file.
461 If ZBOOT_ROM is not enabled, this has no effect.
464 bool "Compressed boot loader in ROM/flash"
465 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
467 Say Y here if you intend to execute your compressed kernel image
468 (zImage) directly from ROM or flash. If unsure, say N.
471 string "Default kernel command string"
474 On some architectures (EBSA110 and CATS), there is currently no way
475 for the boot loader to pass arguments to the kernel. For these
476 architectures, you should supply some command-line options at build
477 time by entering them here. As a minimum, you should specify the
478 memory size and the root device (e.g., mem=64M root=/dev/nfs).
481 bool "Kernel Execute-In-Place from ROM"
482 depends on !ZBOOT_ROM
484 Execute-In-Place allows the kernel to run from non-volatile storage
485 directly addressable by the CPU, such as NOR flash. This saves RAM
486 space since the text section of the kernel is not loaded from flash
487 to RAM. Read-write sections, such as the data section and stack,
488 are still copied to RAM. The XIP kernel is not compressed since
489 it has to run directly from flash, so it will take more space to
490 store it. The flash address used to link the kernel object files,
491 and for storing it, is configuration dependent. Therefore, if you
492 say Y here, you must know the proper physical address where to
493 store the kernel image depending on your own flash memory usage.
495 Also note that the make target becomes "make xipImage" rather than
496 "make zImage" or "make Image". The final kernel binary to put in
497 ROM memory will be arch/arm/boot/xipImage.
502 hex "XIP Kernel Physical Location"
503 depends on XIP_KERNEL
506 This is the physical address in your flash memory the kernel will
507 be linked for and stored to. This address is dependent on your
512 if (ARCH_SA1100 || ARCH_INTEGRATOR)
514 menu "CPU Frequency scaling"
516 source "drivers/cpufreq/Kconfig"
518 config CPU_FREQ_SA1100
520 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
523 config CPU_FREQ_SA1110
525 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
528 config CPU_FREQ_INTEGRATOR
529 tristate "CPUfreq driver for ARM Integrator CPUs"
530 depends on ARCH_INTEGRATOR && CPU_FREQ
533 This enables the CPUfreq driver for ARM Integrator CPUs.
535 For details, take a look at <file:Documentation/cpu-freq>.
543 menu "Floating point emulation"
545 comment "At least one emulation must be selected"
548 bool "NWFPE math emulation"
550 Say Y to include the NWFPE floating point emulator in the kernel.
551 This is necessary to run most binaries. Linux does not currently
552 support floating point hardware so you need to say Y here even if
553 your machine has an FPA or floating point co-processor podule.
555 You may say N here if you are going to load the Acorn FPEmulator
559 bool "Support extended precision"
560 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
562 Say Y to include 80-bit support in the kernel floating-point
563 emulator. Otherwise, only 32 and 64-bit support is compiled in.
564 Note that gcc does not generate 80-bit operations by default,
565 so in most cases this option only enlarges the size of the
566 floating point emulator without any good reason.
568 You almost surely want to say N here.
571 bool "FastFPE math emulation (EXPERIMENTAL)"
572 depends on !CPU_32v3 && EXPERIMENTAL
574 Say Y here to include the FAST floating point emulator in the kernel.
575 This is an experimental much faster emulator which now also has full
576 precision for the mantissa. It does not support any exceptions.
577 It is very simple, and approximately 3-6 times faster than NWFPE.
579 It should be sufficient for most programs. It may be not suitable
580 for scientific calculations, but you have to check this for yourself.
581 If you do not feel you need a faster FP emulation you should better
585 bool "VFP-format floating point maths"
586 depends on CPU_V6 || CPU_ARM926T
588 Say Y to include VFP support code in the kernel. This is needed
589 if your hardware includes a VFP unit.
591 Please see <file:Documentation/arm/VFP/release-notes.txt> for
592 release notes and additional status information.
594 Say N if your target does not have VFP hardware.
598 menu "Userspace binary formats"
600 source "fs/Kconfig.binfmt"
603 tristate "RISC OS personality"
605 Say Y here to include the kernel code necessary if you want to run
606 Acorn RISC OS/Arthur binaries under Linux. This code is still very
607 experimental; if this sounds frightening, say N and sleep in peace.
608 You can also say M here to compile this support as a module (which
609 will be called arthur).
613 menu "Power management options"
616 bool "Power Management support"
618 "Power Management" means that parts of your computer are shut
619 off or put into a power conserving "sleep" mode if they are not
620 being used. There are two competing standards for doing this: APM
621 and ACPI. If you want to use either one, say Y here and then also
622 to the requisite support below.
624 Power Management is most important for battery powered laptop
625 computers; if you have a laptop, check out the Linux Laptop home
626 page on the WWW at <http://www.linux-on-laptops.com/> or
627 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
628 and the Battery Powered Linux mini-HOWTO, available from
629 <http://www.tldp.org/docs.html#howto>.
631 Note that, even if you say N here, Linux on the x86 architecture
632 will issue the hlt instruction if nothing is to be done, thereby
633 sending the processor to sleep and saving power.
636 tristate "Advanced Power Management Emulation"
639 APM is a BIOS specification for saving power using several different
640 techniques. This is mostly useful for battery powered laptops with
641 APM compliant BIOSes. If you say Y here, the system time will be
642 reset after a RESUME operation, the /proc/apm device will provide
643 battery status information, and user-space programs will receive
644 notification of APM "events" (e.g. battery status change).
646 If you select "Y" here, you can disable actual use of the APM
647 BIOS by passing the "apm=off" option to the kernel at boot time.
649 Note that the APM support is almost completely disabled for
650 machines with more than one CPU.
652 In order to use APM, you will need supporting software. For location
653 and more information, read <file:Documentation/pm.txt> and the
654 Battery Powered Linux mini-HOWTO, available from
655 <http://www.tldp.org/docs.html#howto>.
657 This driver does not spin down disk drives (see the hdparm(8)
658 manpage ("man 8 hdparm") for that), and it doesn't turn off
659 VESA-compliant "green" monitors.
661 This driver does not support the TI 4000M TravelMate and the ACER
662 486/DX4/75 because they don't have compliant BIOSes. Many "green"
663 desktop machines also don't have compliant BIOSes, and this driver
664 may cause those machines to panic during the boot phase.
666 Generally, if you don't have a battery in your machine, there isn't
667 much point in using this driver and you should say N. If you get
668 random kernel OOPSes or reboots that don't seem to be related to
669 anything, try disabling/enabling this option (or disabling/enabling
672 Some other things you should try when experiencing seemingly random,
675 1) make sure that you have enough swap space and that it is
677 2) pass the "no-hlt" option to the kernel
678 3) switch on floating point emulation in the kernel and pass
679 the "no387" option to the kernel
680 4) pass the "floppy=nodma" option to the kernel
681 5) pass the "mem=4M" option to the kernel (thereby disabling
682 all but the first 4 MB of RAM)
683 6) make sure that the CPU is not over clocked.
684 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
685 8) disable the cache from your BIOS settings
686 9) install a fan for the video card or exchange video RAM
687 10) install a better fan for the CPU
688 11) exchange RAM chips
689 12) exchange the motherboard.
691 To compile this driver as a module, choose M here: the
692 module will be called apm.
696 menu "Device Drivers"
698 source "drivers/base/Kconfig"
701 source "drivers/mtd/Kconfig"
704 source "drivers/parport/Kconfig"
706 source "drivers/pnp/Kconfig"
708 source "drivers/block/Kconfig"
710 source "drivers/acorn/block/Kconfig"
712 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
713 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
714 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
715 source "drivers/ide/Kconfig"
718 source "drivers/scsi/Kconfig"
720 source "drivers/md/Kconfig"
722 source "drivers/message/fusion/Kconfig"
724 source "drivers/ieee1394/Kconfig"
726 source "drivers/message/i2o/Kconfig"
730 source "drivers/isdn/Kconfig"
732 # input before char - char/joystick depends on it. As does USB.
734 source "drivers/input/Kconfig"
736 source "drivers/char/Kconfig"
738 source "drivers/i2c/Kconfig"
740 #source "drivers/l3/Kconfig"
742 source "drivers/misc/Kconfig"
744 source "drivers/media/Kconfig"
746 source "drivers/video/Kconfig"
748 source "sound/Kconfig"
750 source "drivers/usb/Kconfig"
752 source "drivers/mmc/Kconfig"
758 source "arch/arm/oprofile/Kconfig"
760 source "arch/arm/Kconfig.debug"
762 source "security/Kconfig"
764 source "crypto/Kconfig"