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_BUST_SPINLOCK
63 config GENERIC_ISA_DMA
75 prompt "ARM system type"
79 bool "Cirrus-CL-PS7500FE"
82 bool "CLPS711x/EP721x-based"
90 This is an evaluation board for the StrongARM processor available
91 from Digital. It has limited hardware on-board, including an onboard
92 Ethernet interface, two PCMCIA sockets, two serial ports and a
98 This enables support for Altera's Excalibur XA10 development board.
99 If you would like to build your kernel to run on one of these boards
100 then you must say 'Y' here. Otherwise say 'N'
102 config ARCH_FOOTBRIDGE
105 config ARCH_INTEGRATOR
115 bool "IXP2400/2800-based"
120 Say Y here if you intend to run this kernel on a LinkUp Systems
121 L7200 Software Development Board which uses an ARM720T processor.
122 Information on this board can be obtained at:
124 <http://www.linkupsys.com/>
126 If you have any questions or comments about the Linux kernel port
127 to this board, send e-mail to sjhill@cotw.com.
135 On the Acorn Risc-PC, Linux can support the internal IDE disk and
136 CD-ROM interface, serial and parallel port, and the floppy drive.
142 bool "Samsung S3C2410"
144 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
145 BAST (http://www.simtec.co.uk/products/EB110ITX/), the IPAQ 1940 or
146 the Samsung SMDK2410 development board (and derviatives).
154 Say Y here for systems based on one of the Sharp LH7A40X
155 System on a Chip processors. These CPUs include an ARM922T
156 core with a wide array of integrated devices for
157 hand-held and low-power applications.
162 config ARCH_VERSATILE_PB
165 This enables support for ARM Ltd Versatile PB board.
171 bool "Hynix-HMS720x-based"
173 This enables support for systems based on the Hynix HMS720x
177 source "arch/arm/mach-clps711x/Kconfig"
179 source "arch/arm/mach-epxa10db/Kconfig"
181 source "arch/arm/mach-footbridge/Kconfig"
183 source "arch/arm/mach-integrator/Kconfig"
185 source "arch/arm/mach-iop3xx/Kconfig"
187 source "arch/arm/mach-ixp4xx/Kconfig"
189 source "arch/arm/mach-ixp2000/Kconfig"
191 source "arch/arm/mach-pxa/Kconfig"
193 source "arch/arm/mach-sa1100/Kconfig"
195 source "arch/arm/mach-omap/Kconfig"
197 source "arch/arm/mach-s3c2410/Kconfig"
199 source "arch/arm/mach-lh7a40x/Kconfig"
201 source "arch/arm/mach-imx/Kconfig"
203 source "arch/arm/mach-h720x/Kconfig"
205 # Definitions to make life easier
213 depends on ARCH_ACORN || ARCH_CLPS7500
216 #####################################################################
220 depends on ARCH_CO285 || ARCH_FOOTBRIDGE
223 config FOOTBRIDGE_HOST
225 depends on ARCH_CATS || ARCH_EBSA285_HOST || ARCH_NETWINDER || ARCH_PERSONAL_SERVER
228 config FOOTBRIDGE_ADDIN
230 depends on ARCH_CO285 || ARCH_EBSA285_ADDIN
235 depends on ARCH_EBSA285_HOST || ARCH_EBSA285_ADDIN
238 #####################################################################
242 depends on ASSABET_NEPONSET || SA1100_ADSBITSY || SA1100_BADGE4 || SA1100_CONSUS || SA1100_GRAPHICSMASTER || SA1100_JORNADA720 || ARCH_LUBBOCK || SA1100_PFS168 || SA1100_PT_SYSTEM3 || SA1100_XP860
247 depends on SA1100_COLLIE
250 config FORCE_MAX_ZONEORDER
257 depends on SA1111 || ARCH_IXP4XX
260 source arch/arm/mm/Kconfig
262 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
265 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
272 # Select various configuration options depending on the machine type
275 depends on ARCH_EDB7211 || ARCH_SA1100 || (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
278 Say Y to support efficient handling of discontiguous physical memory,
279 for architectures which are either NUMA (Non-Uniform Memory Access)
280 or have huge holes in the physical address space for other reasons.
281 See <file:Documentation/vm/numa> for more.
283 # Now handle the bus types
285 bool "PCI support" if ARCH_INTEGRATOR_AP
286 default y if ARCH_SHARK || FOOTBRIDGE_HOST || ARCH_IOP3XX || ARCH_IXP4XX || ARCH_IXP2000
288 Find out whether you have a PCI motherboard. PCI is the name of a
289 bus system, i.e. the way the CPU talks to the other stuff inside
290 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
291 VESA. If you have PCI, say Y, otherwise N.
293 The PCI-HOWTO, available from
294 <http://www.tldp.org/docs.html#howto>, contains valuable
295 information about which PCI hardware does work under Linux and which
298 # Select the host bridge type
299 config PCI_HOST_VIA82C505
301 depends on PCI && ARCH_SHARK
306 depends on ARCH_INTEGRATOR
311 depends on ARCH_INTEGRATOR || ARCH_VERSATILE_PB
316 depends on FOOTBRIDGE_HOST || ARCH_SHARK || ARCH_CLPS7500 || ARCH_EBSA110 || ARCH_CDB89712 || ARCH_EDB7211 || ARCH_SA1100 || ARCH_MX1ADS
319 Find out whether you have ISA slots on your motherboard. ISA is the
320 name of a bus system, i.e. the way the CPU talks to the other stuff
321 inside your box. Other bus systems are PCI, EISA, MicroChannel
322 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
323 newer boards don't support it. If you have ISA, say Y, otherwise N.
327 depends on FOOTBRIDGE_HOST || ARCH_SHARK
332 depends on ARCH_ACORN || ARCH_L7200 || ARCH_LH7A400
335 # Compressed boot loader in ROM. Yes, we really want to ask about
336 # TEXT and BSS so we preserve their values in the config files.
338 bool "Compressed boot loader in ROM/flash"
340 Say Y here if you intend to execute your compressed kernel image (zImage)
341 directly from ROM or flash. If unsure, say N.
343 config ZBOOT_ROM_TEXT
344 hex "Compressed ROM boot loader base address"
347 The base address for zImage. Unless you have special requirements, you
348 should not change this value.
351 hex "Compressed ROM boot loader BSS address"
354 The base address of 64KiB of read/write memory, which must be available
355 while the decompressor is running. Unless you have special requirements,
356 you should not change this value.
359 bool "Support CPU clock change (EXPERIMENTAL)"
360 depends on (ARCH_SA1100 || ARCH_INTEGRATOR) && EXPERIMENTAL
362 CPU clock scaling allows you to change the clock speed of the
363 running CPU on the fly. This is a nice method to save battery power,
364 because the lower the clock speed, the less power the CPU
365 consumes. Note that this driver doesn't automatically change the CPU
366 clock speed, you need some userland tools (which still have to be
367 written) to implement the policy. If you don't understand what this
368 is all about, it's safe to say 'N'.
371 # CPUfreq on SA11x0 is special -- it _needs_ the userspace governor
373 config CPU_FREQ_SA1100
375 depends on CPU_FREQ && SA1100_LART
377 select CPU_FREQ_24_API if SYSCTL
379 config CPU_FREQ_SA1110
381 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
383 select CPU_FREQ_24_API if SYSCTL
385 config CPU_FREQ_INTEGRATOR
386 tristate "CPUfreq driver for ARM Integrator CPUs"
387 depends on ARCH_INTEGRATOR && ICST525 && CPU_FREQ
390 This enables the CPUfreq driver for ARM Integrator CPUs.
392 For details, take a look at <file:Documentation/cpu-freq>.
396 if (CPU_FREQ_INTEGRATOR) || (CPU_FREQ_SA1110) || (CPU_FREQ_SA1100)
398 source "drivers/cpufreq/Kconfig"
402 source "drivers/pci/Kconfig"
404 source "drivers/pcmcia/Kconfig"
406 comment "At least one math emulation must be selected"
409 bool "NWFPE math emulation"
411 Say Y to include the NWFPE floating point emulator in the kernel.
412 This is necessary to run most binaries. Linux does not currently
413 support floating point hardware so you need to say Y here even if
414 your machine has an FPA or floating point co-processor podule.
416 You may say N here if you are going to load the Acorn FPEmulator
420 bool "Support extended precision"
421 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
423 Say Y to include 80-bit support in the kernel floating-point
424 emulator. Otherwise, only 32 and 64-bit support is compiled in.
425 Note that gcc does not generate 80-bit operations by default,
426 so in most cases this option only enlarges the size of the
427 floating point emulator without any good reason.
429 You almost surely want to say N here.
432 bool "FastFPE math emulation (EXPERIMENTAL)"
433 depends on !CPU_32v3 && EXPERIMENTAL
435 Say Y here to include the FAST floating point emulator in the kernel.
436 This is an experimental much faster emulator which now also has full
437 precision for the mantissa. It does not support any exceptions.
438 It is very simple, and approximately 3-6 times faster than NWFPE.
440 It should be sufficient for most programs. It may be not suitable
441 for scientific calculations, but you have to check this for yourself.
442 If you do not feel you need a faster FP emulation you should better
446 bool "VFP-format floating point maths"
447 depends on CPU_V6 || CPU_ARM926T
449 Say Y to include VFP support code in the kernel. This is needed
450 if your hardware includes a VFP unit.
452 Please see <file:Documentation/arm/VFP/release-notes.txt> for
453 release notes and additional status information.
455 Say N if your target does not have VFP hardware.
457 source "fs/Kconfig.binfmt"
459 source "drivers/base/Kconfig"
462 bool "Power Management support"
464 "Power Management" means that parts of your computer are shut
465 off or put into a power conserving "sleep" mode if they are not
466 being used. There are two competing standards for doing this: APM
467 and ACPI. If you want to use either one, say Y here and then also
468 to the requisite support below.
470 Power Management is most important for battery powered laptop
471 computers; if you have a laptop, check out the Linux Laptop home
472 page on the WWW at <http://www.linux-on-laptops.com/> or
473 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
474 and the Battery Powered Linux mini-HOWTO, available from
475 <http://www.tldp.org/docs.html#howto>.
477 Note that, even if you say N here, Linux on the x86 architecture
478 will issue the hlt instruction if nothing is to be done, thereby
479 sending the processor to sleep and saving power.
482 bool "Preemptible Kernel (EXPERIMENTAL)"
483 depends on CPU_32 && EXPERIMENTAL
485 This option reduces the latency of the kernel when reacting to
486 real-time or interactive events by allowing a low priority process to
487 be preempted even if it is in kernel mode executing a system call.
488 This allows applications to run more reliably even when the system is
491 Say Y here if you are building a kernel for a desktop, embedded
492 or real-time system. Say N if you are unsure.
495 tristate "Advanced Power Management Emulation"
498 APM is a BIOS specification for saving power using several different
499 techniques. This is mostly useful for battery powered laptops with
500 APM compliant BIOSes. If you say Y here, the system time will be
501 reset after a RESUME operation, the /proc/apm device will provide
502 battery status information, and user-space programs will receive
503 notification of APM "events" (e.g. battery status change).
505 If you select "Y" here, you can disable actual use of the APM
506 BIOS by passing the "apm=off" option to the kernel at boot time.
508 Note that the APM support is almost completely disabled for
509 machines with more than one CPU.
511 In order to use APM, you will need supporting software. For location
512 and more information, read <file:Documentation/pm.txt> and the
513 Battery Powered Linux mini-HOWTO, available from
514 <http://www.tldp.org/docs.html#howto>.
516 This driver does not spin down disk drives (see the hdparm(8)
517 manpage ("man 8 hdparm") for that), and it doesn't turn off
518 VESA-compliant "green" monitors.
520 This driver does not support the TI 4000M TravelMate and the ACER
521 486/DX4/75 because they don't have compliant BIOSes. Many "green"
522 desktop machines also don't have compliant BIOSes, and this driver
523 may cause those machines to panic during the boot phase.
525 Generally, if you don't have a battery in your machine, there isn't
526 much point in using this driver and you should say N. If you get
527 random kernel OOPSes or reboots that don't seem to be related to
528 anything, try disabling/enabling this option (or disabling/enabling
531 Some other things you should try when experiencing seemingly random,
534 1) make sure that you have enough swap space and that it is
536 2) pass the "no-hlt" option to the kernel
537 3) switch on floating point emulation in the kernel and pass
538 the "no387" option to the kernel
539 4) pass the "floppy=nodma" option to the kernel
540 5) pass the "mem=4M" option to the kernel (thereby disabling
541 all but the first 4 MB of RAM)
542 6) make sure that the CPU is not over clocked.
543 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
544 8) disable the cache from your BIOS settings
545 9) install a fan for the video card or exchange video RAM
546 10) install a better fan for the CPU
547 11) exchange RAM chips
548 12) exchange the motherboard.
550 To compile this driver as a module, choose M here: the
551 module will be called apm.
554 tristate "RISC OS personality"
557 Say Y here to include the kernel code necessary if you want to run
558 Acorn RISC OS/Arthur binaries under Linux. This code is still very
559 experimental; if this sounds frightening, say N and sleep in peace.
560 You can also say M here to compile this support as a module (which
561 will be called arthur).
564 string "Default kernel command string"
567 On some architectures (EBSA110 and CATS), there is currently no way
568 for the boot loader to pass arguments to the kernel. For these
569 architectures, you should supply some command-line options at build
570 time by entering them here. As a minimum, you should specify the
571 memory size and the root device (e.g., mem=64M root=/dev/nfs).
574 bool "Timer and CPU usage LEDs"
575 depends on ARCH_NETWINDER || ARCH_EBSA110 || ARCH_EBSA285 || ARCH_SHARK || ARCH_CO285 || ARCH_SA1100 || ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_PXA_IDP || ARCH_INTEGRATOR || ARCH_CDB89712 || ARCH_P720T || ARCH_OMAP || ARCH_VERSATILE_PB || ARCH_IMX
577 If you say Y here, the LEDs on your machine will be used
578 to provide useful information about your current system status.
580 If you are compiling a kernel for a NetWinder or EBSA-285, you will
581 be able to select which LEDs are active using the options below. If
582 you are compiling a kernel for the EBSA-110 or the LART however, the
583 red LED will simply flash regularly to indicate that the system is
584 still functional. It is safe to say Y here if you have a CATS
585 system, but the driver will do nothing.
588 bool "Timer LED" if LEDS && (ARCH_NETWINDER || ARCH_EBSA285 || ARCH_SHARK || MACH_MAINSTONE || ARCH_CO285 || ARCH_SA1100 || ARCH_LUBBOCK || ARCH_PXA_IDP || ARCH_INTEGRATOR || ARCH_P720T || ARCH_VERSATILE_PB || ARCH_IMX)
589 depends on ARCH_NETWINDER || ARCH_EBSA110 || ARCH_EBSA285 || ARCH_SHARK || ARCH_CO285 || ARCH_SA1100 || ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_PXA_IDP || ARCH_INTEGRATOR || ARCH_CDB89712 || ARCH_P720T || ARCH_OMAP || ARCH_VERSATILE_PB || ARCH_IMX
590 default y if ARCH_EBSA110
592 If you say Y here, one of the system LEDs (the green one on the
593 NetWinder, the amber one on the EBSA285, or the red one on the LART)
594 will flash regularly to indicate that the system is still
595 operational. This is mainly useful to kernel hackers who are
596 debugging unstable kernels.
598 The LART uses the same LED for both Timer LED and CPU usage LED
599 functions. You may choose to use both, but the Timer LED function
600 will overrule the CPU usage LED.
604 depends on LEDS && (ARCH_NETWINDER || ARCH_EBSA285 || ARCH_SHARK || ARCH_CO285 || ARCH_SA1100 || ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_PXA_IDP || ARCH_INTEGRATOR || ARCH_P720T || ARCH_VERSATILE_PB || ARCH_IMX)
606 If you say Y here, the red LED will be used to give a good real
607 time indication of CPU usage, by lighting whenever the idle task
608 is not currently executing.
610 The LART uses the same LED for both Timer LED and CPU usage LED
611 functions. You may choose to use both, but the Timer LED function
612 will overrule the CPU usage LED.
614 config ALIGNMENT_TRAP
617 default y if !ARCH_EBSA110
619 ARM processors can not fetch/store information which is not
620 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
621 address divisible by 4. On 32-bit ARM processors, these non-aligned
622 fetch/store instructions will be emulated in software if you say
623 here, which has a severe performance impact. This is necessary for
624 correct operation of some network protocols. With an IP-only
625 configuration it is safe to say N, otherwise say Y.
629 source "drivers/parport/Kconfig"
632 source "drivers/mtd/Kconfig"
635 source "drivers/pnp/Kconfig"
637 source "drivers/block/Kconfig"
639 source "drivers/md/Kconfig"
641 source "drivers/acorn/block/Kconfig"
645 if ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
646 source "drivers/ide/Kconfig"
649 source "drivers/scsi/Kconfig"
651 source "drivers/message/fusion/Kconfig"
653 source "drivers/ieee1394/Kconfig"
655 source "drivers/message/i2o/Kconfig"
657 source "drivers/isdn/Kconfig"
660 # input before char - char/joystick depends on it. As does USB.
662 source "drivers/input/Kconfig"
664 source "drivers/char/Kconfig"
666 source "drivers/i2c/Kconfig"
668 #source "drivers/l3/Kconfig"
670 source "drivers/media/Kconfig"
674 source "arch/arm/oprofile/Kconfig"
676 source "drivers/video/Kconfig"
678 source "sound/Kconfig"
680 source "drivers/misc/Kconfig"
682 source "drivers/usb/Kconfig"
684 source "drivers/mmc/Kconfig"
686 source "arch/arm/Kconfig.debug"
688 source "kernel/vserver/Kconfig"
690 source "security/Kconfig"
692 source "crypto/Kconfig"