2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 select SYS_SUPPORTS_APM_EMULATION
14 The ARM series is a line of low-power-consumption RISC chip designs
15 licensed by ARM Ltd and targeted at embedded applications and
16 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
17 manufactured, but legacy ARM-based PC hardware remains popular in
18 Europe. There is an ARM Linux project with a web page at
19 <http://www.arm.linux.org.uk/>.
21 config SYS_SUPPORTS_APM_EMULATION
32 config GENERIC_CLOCKEVENTS
47 The Extended Industry Standard Architecture (EISA) bus was
48 developed as an open alternative to the IBM MicroChannel bus.
50 The EISA bus provided some of the features of the IBM MicroChannel
51 bus while maintaining backward compatibility with cards made for
52 the older ISA bus. The EISA bus saw limited use between 1988 and
53 1995 when it was made obsolete by the PCI bus.
55 Say Y here if you are building a kernel for an EISA-based machine.
65 MicroChannel Architecture is found in some IBM PS/2 machines and
66 laptops. It is a bus system similar to PCI or ISA. See
67 <file:Documentation/mca.txt> (and especially the web page given
68 there) before attempting to build an MCA bus kernel.
70 config GENERIC_HARDIRQS
74 config STACKTRACE_SUPPORT
78 config LOCKDEP_SUPPORT
82 config TRACE_IRQFLAGS_SUPPORT
86 config HARDIRQS_SW_RESEND
90 config GENERIC_IRQ_PROBE
94 config RWSEM_GENERIC_SPINLOCK
98 config RWSEM_XCHGADD_ALGORITHM
101 config ARCH_HAS_ILOG2_U32
105 config ARCH_HAS_ILOG2_U64
109 config GENERIC_HWEIGHT
113 config GENERIC_CALIBRATE_DELAY
117 config ARCH_MAY_HAVE_PC_FDC
124 config GENERIC_ISA_DMA
135 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
136 default DRAM_BASE if REMAP_VECTORS_TO_RAM
139 The base address of exception vectors.
141 source "init/Kconfig"
146 prompt "ARM system type"
147 default ARCH_VERSATILE
150 bool "Agilent AAEC-2000 based"
153 This enables support for systems based on the Agilent AAEC-2000
155 config ARCH_INTEGRATOR
156 bool "ARM Ltd. Integrator family"
160 Support for ARM's Integrator platform.
163 bool "ARM Ltd. RealView family"
167 This enables support for ARM Ltd RealView boards.
169 config ARCH_VERSATILE
170 bool "ARM Ltd. Versatile family"
175 select GENERIC_CLOCKEVENTS
177 This enables support for ARM Ltd Versatile board.
183 This enables support for systems based on the Atmel AT91RM9200
184 and AT91SAM9xxx processors.
187 bool "Cirrus CL-PS7500FE"
192 Support for the Cirrus Logic PS7500FE system-on-a-chip.
195 bool "Cirrus Logic CLPS711x/EP721x-based"
197 Support for Cirrus Logic 711x/721x based boards.
202 select FOOTBRIDGE_ADDIN
204 Support for Intel's EBSA285 companion chip.
211 This is an evaluation board for the StrongARM processor available
212 from Digital. It has limited hardware on-board, including an
213 Ethernet interface, two PCMCIA sockets, two serial ports and a
221 This enables support for the Cirrus EP93xx series of CPUs.
223 config ARCH_FOOTBRIDGE
227 Support for systems based on the DC21285 companion chip
228 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
231 bool "Hilscher NetX based"
234 This enables support for systems based on the Hilscher NetX Soc
237 bool "Hynix HMS720x-based"
240 This enables support for systems based on the Hynix HMS720x
246 select GENERIC_CLOCKEVENTS
248 Support for Motorola's i.MX family of processors (MX1, MXL).
255 select ARCH_SUPPORTS_MSI
257 Support for Intel's IOP13XX (XScale) family of processors.
265 Support for Intel's 80219 and IOP32X (XScale) family of
274 Support for Intel's IOP33X (XScale) family of processors.
281 Support for Intel's IXP23xx (XScale) family of processors.
284 bool "IXP2400/2800-based"
288 Support for Intel's IXP2400/2800 (XScale) family of processors.
295 select GENERIC_CLOCKEVENTS
297 Support for Intel's IXP4XX (XScale) family of processors.
303 Say Y here if you intend to run this kernel on a LinkUp Systems
304 L7200 Software Development Board which uses an ARM720T processor.
305 Information on this board can be obtained at:
307 <http://www.linkupsys.com/>
309 If you have any questions or comments about the Linux kernel port
310 to this board, send e-mail to <sjhill@cotw.com>.
313 bool "Micrel/Kendin KS8695"
316 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
317 System-on-Chip devices.
320 bool "NetSilicon NS9xxx"
323 select GENERIC_CLOCKEVENTS
325 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
328 <http://www.digi.com/products/microprocessors/index.jsp>
331 bool "Freescale MXC/iMX-based"
334 Support for Freescale MXC/iMX-based family of processors
337 bool "Philips Nexperia PNX4008 Mobile"
339 This enables support for Philips PNX4008 mobile platform.
342 bool "PXA2xx/PXA3xx-based"
347 select GENERIC_CLOCKEVENTS
349 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
356 select ARCH_MAY_HAVE_PC_FDC
360 On the Acorn Risc-PC, Linux can support the internal IDE disk and
361 CD-ROM interface, serial and parallel port, and the floppy drive.
366 select ARCH_DISCONTIGMEM_ENABLE
370 Support for StrongARM 11x0 based boards.
373 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
376 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
377 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
378 the Samsung SMDK2410 development board (and derivatives).
386 Support for the StrongARM based Digital DNARD machine, also known
387 as "Shark" (<http://www.shark-linux.de/shark.html>).
392 Say Y here for systems based on one of the Sharp LH7A40X
393 System on a Chip processors. These CPUs include an ARM922T
394 core with a wide array of integrated devices for
395 hand-held and low-power applications.
400 select GENERIC_CLOCKEVENTS
403 Support for TI's DaVinci platform.
410 Support for TI's OMAP platform (OMAP1 and OMAP2).
414 source "arch/arm/mach-clps711x/Kconfig"
416 source "arch/arm/mach-ep93xx/Kconfig"
418 source "arch/arm/mach-footbridge/Kconfig"
420 source "arch/arm/mach-integrator/Kconfig"
422 source "arch/arm/mach-iop32x/Kconfig"
424 source "arch/arm/mach-iop33x/Kconfig"
426 source "arch/arm/mach-iop13xx/Kconfig"
428 source "arch/arm/mach-ixp4xx/Kconfig"
430 source "arch/arm/mach-ixp2000/Kconfig"
432 source "arch/arm/mach-ixp23xx/Kconfig"
434 source "arch/arm/mach-pxa/Kconfig"
436 source "arch/arm/mach-sa1100/Kconfig"
438 source "arch/arm/plat-omap/Kconfig"
440 source "arch/arm/mach-omap1/Kconfig"
442 source "arch/arm/mach-omap2/Kconfig"
444 source "arch/arm/plat-s3c24xx/Kconfig"
445 source "arch/arm/plat-s3c/Kconfig"
448 source "arch/arm/mach-s3c2400/Kconfig"
449 source "arch/arm/mach-s3c2410/Kconfig"
450 source "arch/arm/mach-s3c2412/Kconfig"
451 source "arch/arm/mach-s3c2440/Kconfig"
452 source "arch/arm/mach-s3c2442/Kconfig"
453 source "arch/arm/mach-s3c2443/Kconfig"
456 source "arch/arm/mach-lh7a40x/Kconfig"
458 source "arch/arm/mach-imx/Kconfig"
460 source "arch/arm/mach-h720x/Kconfig"
462 source "arch/arm/mach-versatile/Kconfig"
464 source "arch/arm/mach-aaec2000/Kconfig"
466 source "arch/arm/mach-realview/Kconfig"
468 source "arch/arm/mach-at91/Kconfig"
470 source "arch/arm/plat-mxc/Kconfig"
472 source "arch/arm/mach-netx/Kconfig"
474 source "arch/arm/mach-ns9xxx/Kconfig"
476 source "arch/arm/mach-davinci/Kconfig"
478 source "arch/arm/mach-ks8695/Kconfig"
480 # Definitions to make life easier
487 source arch/arm/mm/Kconfig
490 bool "Enable iWMMXt support"
491 depends on CPU_XSCALE || CPU_XSC3
492 default y if PXA27x || PXA3xx
494 Enable support for iWMMXt context switching at run time if
495 running on a CPU that supports it.
497 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
500 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
504 source "arch/arm/Kconfig-nommu"
509 source "arch/arm/common/Kconfig"
511 config FORCE_MAX_ZONEORDER
524 Find out whether you have ISA slots on your motherboard. ISA is the
525 name of a bus system, i.e. the way the CPU talks to the other stuff
526 inside your box. Other bus systems are PCI, EISA, MicroChannel
527 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
528 newer boards don't support it. If you have ISA, say Y, otherwise N.
530 # Select ISA DMA controller support
535 # Select ISA DMA interface
540 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX || ARCH_KS8695 || MACH_ARMCORE
542 Find out whether you have a PCI motherboard. PCI is the name of a
543 bus system, i.e. the way the CPU talks to the other stuff inside
544 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
545 VESA. If you have PCI, say Y, otherwise N.
547 The PCI-HOWTO, available from
548 <http://www.tldp.org/docs.html#howto>, contains valuable
549 information about which PCI hardware does work under Linux and which
555 # Select the host bridge type
556 config PCI_HOST_VIA82C505
558 depends on PCI && ARCH_SHARK
561 config PCI_HOST_ITE8152
563 depends on PCI && MACH_ARMCORE
567 source "drivers/pci/Kconfig"
569 source "drivers/pcmcia/Kconfig"
573 menu "Kernel Features"
575 source "kernel/time/Kconfig"
578 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
579 depends on EXPERIMENTAL && REALVIEW_MPCORE
581 This enables support for systems with more than one CPU. If you have
582 a system with only one CPU, like most personal computers, say N. If
583 you have a system with more than one CPU, say Y.
585 If you say N here, the kernel will run on single and multiprocessor
586 machines, but will use only one CPU of a multiprocessor machine. If
587 you say Y here, the kernel will run on many, but not all, single
588 processor machines. On a single processor machine, the kernel will
589 run faster if you say N here.
591 See also the <file:Documentation/smp.txt>,
592 <file:Documentation/i386/IO-APIC.txt>,
593 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
594 <http://www.linuxdoc.org/docs.html#howto>.
596 If you don't know what to do here, say N.
599 int "Maximum number of CPUs (2-32)"
605 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
606 depends on SMP && HOTPLUG && EXPERIMENTAL
608 Say Y here to experiment with turning CPUs off and on. CPUs
609 can be controlled through /sys/devices/system/cpu.
612 bool "Use local timer interrupts"
613 depends on SMP && REALVIEW_MPCORE
616 Enable support for local timers on SMP platforms, rather then the
617 legacy IPI broadcast method. Local timers allows the system
618 accounting to be spread across the timer interval, preventing a
619 "thundering herd" at every timer tick.
622 bool "Preemptible Kernel (EXPERIMENTAL)"
623 depends on EXPERIMENTAL
625 This option reduces the latency of the kernel when reacting to
626 real-time or interactive events by allowing a low priority process to
627 be preempted even if it is in kernel mode executing a system call.
628 This allows applications to run more reliably even when the system is
631 Say Y here if you are building a kernel for a desktop, embedded
632 or real-time system. Say N if you are unsure.
635 bool "Dynamic tick timer"
636 depends on !GENERIC_CLOCKEVENTS
638 Select this option if you want to disable continuous timer ticks
639 and have them programmed to occur as required. This option saves
640 power as the system can remain in idle state for longer.
642 By default dynamic tick is disabled during the boot, and can be
643 manually enabled with:
645 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
647 Alternatively, if you want dynamic tick automatically enabled
648 during boot, pass "dyntick=enable" via the kernel command string.
650 Please note that dynamic tick may affect the accuracy of
651 timekeeping on some platforms depending on the implementation.
652 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
653 to have accurate timekeeping with dynamic tick.
657 default 128 if ARCH_L7200
658 default 200 if ARCH_EBSA110 || ARCH_S3C2410
659 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
660 default AT91_TIMER_HZ if ARCH_AT91
664 bool "Use the ARM EABI to compile the kernel"
666 This option allows for the kernel to be compiled using the latest
667 ARM ABI (aka EABI). This is only useful if you are using a user
668 space environment that is also compiled with EABI.
670 Since there are major incompatibilities between the legacy ABI and
671 EABI, especially with regard to structure member alignment, this
672 option also changes the kernel syscall calling convention to
673 disambiguate both ABIs and allow for backward compatibility support
674 (selected with CONFIG_OABI_COMPAT).
676 To use this you need GCC version 4.0.0 or later.
679 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
680 depends on AEABI && EXPERIMENTAL
683 This option preserves the old syscall interface along with the
684 new (ARM EABI) one. It also provides a compatibility layer to
685 intercept syscalls that have structure arguments which layout
686 in memory differs between the legacy ABI and the new ARM EABI
687 (only for non "thumb" binaries). This option adds a tiny
688 overhead to all syscalls and produces a slightly larger kernel.
689 If you know you'll be using only pure EABI user space then you
690 can say N here. If this option is not selected and you attempt
691 to execute a legacy ABI binary then the result will be
692 UNPREDICTABLE (in fact it can be predicted that it won't work
693 at all). If in doubt say Y.
695 config ARCH_DISCONTIGMEM_ENABLE
697 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
699 Say Y to support efficient handling of discontiguous physical memory,
700 for architectures which are either NUMA (Non-Uniform Memory Access)
701 or have huge holes in the physical address space for other reasons.
702 See <file:Documentation/vm/numa> for more.
706 default "4" if ARCH_LH7A40X
708 depends on NEED_MULTIPLE_NODES
713 bool "Timer and CPU usage LEDs"
714 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
715 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
716 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
717 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
718 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
719 ARCH_AT91 || MACH_TRIZEPS4 || ARCH_DAVINCI || \
722 If you say Y here, the LEDs on your machine will be used
723 to provide useful information about your current system status.
725 If you are compiling a kernel for a NetWinder or EBSA-285, you will
726 be able to select which LEDs are active using the options below. If
727 you are compiling a kernel for the EBSA-110 or the LART however, the
728 red LED will simply flash regularly to indicate that the system is
729 still functional. It is safe to say Y here if you have a CATS
730 system, but the driver will do nothing.
733 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
734 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
735 || MACH_OMAP_PERSEUS2
737 depends on !GENERIC_CLOCKEVENTS
738 default y if ARCH_EBSA110
740 If you say Y here, one of the system LEDs (the green one on the
741 NetWinder, the amber one on the EBSA285, or the red one on the LART)
742 will flash regularly to indicate that the system is still
743 operational. This is mainly useful to kernel hackers who are
744 debugging unstable kernels.
746 The LART uses the same LED for both Timer LED and CPU usage LED
747 functions. You may choose to use both, but the Timer LED function
748 will overrule the CPU usage LED.
751 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
753 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
754 || MACH_OMAP_PERSEUS2
757 If you say Y here, the red LED will be used to give a good real
758 time indication of CPU usage, by lighting whenever the idle task
759 is not currently executing.
761 The LART uses the same LED for both Timer LED and CPU usage LED
762 functions. You may choose to use both, but the Timer LED function
763 will overrule the CPU usage LED.
765 config ALIGNMENT_TRAP
767 depends on CPU_CP15_MMU
768 default y if !ARCH_EBSA110
770 ARM processors cannot fetch/store information which is not
771 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
772 address divisible by 4. On 32-bit ARM processors, these non-aligned
773 fetch/store instructions will be emulated in software if you say
774 here, which has a severe performance impact. This is necessary for
775 correct operation of some network protocols. With an IP-only
776 configuration it is safe to say N, otherwise say Y.
782 # Compressed boot loader in ROM. Yes, we really want to ask about
783 # TEXT and BSS so we preserve their values in the config files.
784 config ZBOOT_ROM_TEXT
785 hex "Compressed ROM boot loader base address"
788 The physical address at which the ROM-able zImage is to be
789 placed in the target. Platforms which normally make use of
790 ROM-able zImage formats normally set this to a suitable
791 value in their defconfig file.
793 If ZBOOT_ROM is not enabled, this has no effect.
796 hex "Compressed ROM boot loader BSS address"
799 The base address of an area of read/write memory in the target
800 for the ROM-able zImage which must be available while the
801 decompressor is running. It must be large enough to hold the
802 entire decompressed kernel plus an additional 128 KiB.
803 Platforms which normally make use of ROM-able zImage formats
804 normally set this to a suitable value in their defconfig file.
806 If ZBOOT_ROM is not enabled, this has no effect.
809 bool "Compressed boot loader in ROM/flash"
810 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
812 Say Y here if you intend to execute your compressed kernel image
813 (zImage) directly from ROM or flash. If unsure, say N.
816 string "Default kernel command string"
819 On some architectures (EBSA110 and CATS), there is currently no way
820 for the boot loader to pass arguments to the kernel. For these
821 architectures, you should supply some command-line options at build
822 time by entering them here. As a minimum, you should specify the
823 memory size and the root device (e.g., mem=64M root=/dev/nfs).
826 bool "Kernel Execute-In-Place from ROM"
827 depends on !ZBOOT_ROM
829 Execute-In-Place allows the kernel to run from non-volatile storage
830 directly addressable by the CPU, such as NOR flash. This saves RAM
831 space since the text section of the kernel is not loaded from flash
832 to RAM. Read-write sections, such as the data section and stack,
833 are still copied to RAM. The XIP kernel is not compressed since
834 it has to run directly from flash, so it will take more space to
835 store it. The flash address used to link the kernel object files,
836 and for storing it, is configuration dependent. Therefore, if you
837 say Y here, you must know the proper physical address where to
838 store the kernel image depending on your own flash memory usage.
840 Also note that the make target becomes "make xipImage" rather than
841 "make zImage" or "make Image". The final kernel binary to put in
842 ROM memory will be arch/arm/boot/xipImage.
847 hex "XIP Kernel Physical Location"
848 depends on XIP_KERNEL
851 This is the physical address in your flash memory the kernel will
852 be linked for and stored to. This address is dependent on your
856 bool "Kexec system call (EXPERIMENTAL)"
857 depends on EXPERIMENTAL
859 kexec is a system call that implements the ability to shutdown your
860 current kernel, and to start another kernel. It is like a reboot
861 but it is independent of the system firmware. And like a reboot
862 you can start any kernel with it, not just Linux.
864 It is an ongoing process to be certain the hardware in a machine
865 is properly shutdown, so do not be surprised if this code does not
866 initially work for you. It may help to enable device hotplugging
871 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
873 menu "CPU Frequency scaling"
875 source "drivers/cpufreq/Kconfig"
877 config CPU_FREQ_SA1100
879 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
882 config CPU_FREQ_SA1110
884 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
887 config CPU_FREQ_INTEGRATOR
888 tristate "CPUfreq driver for ARM Integrator CPUs"
889 depends on ARCH_INTEGRATOR && CPU_FREQ
892 This enables the CPUfreq driver for ARM Integrator CPUs.
894 For details, take a look at <file:Documentation/cpu-freq>.
899 tristate "CPUfreq driver for i.MX CPUs"
900 depends on ARCH_IMX && CPU_FREQ
903 This enables the CPUfreq driver for i.MX CPUs.
911 menu "Floating point emulation"
913 comment "At least one emulation must be selected"
916 bool "NWFPE math emulation"
917 depends on !AEABI || OABI_COMPAT
919 Say Y to include the NWFPE floating point emulator in the kernel.
920 This is necessary to run most binaries. Linux does not currently
921 support floating point hardware so you need to say Y here even if
922 your machine has an FPA or floating point co-processor podule.
924 You may say N here if you are going to load the Acorn FPEmulator
928 bool "Support extended precision"
931 Say Y to include 80-bit support in the kernel floating-point
932 emulator. Otherwise, only 32 and 64-bit support is compiled in.
933 Note that gcc does not generate 80-bit operations by default,
934 so in most cases this option only enlarges the size of the
935 floating point emulator without any good reason.
937 You almost surely want to say N here.
940 bool "FastFPE math emulation (EXPERIMENTAL)"
941 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
943 Say Y here to include the FAST floating point emulator in the kernel.
944 This is an experimental much faster emulator which now also has full
945 precision for the mantissa. It does not support any exceptions.
946 It is very simple, and approximately 3-6 times faster than NWFPE.
948 It should be sufficient for most programs. It may be not suitable
949 for scientific calculations, but you have to check this for yourself.
950 If you do not feel you need a faster FP emulation you should better
954 bool "VFP-format floating point maths"
955 depends on CPU_V6 || CPU_ARM926T
957 Say Y to include VFP support code in the kernel. This is needed
958 if your hardware includes a VFP unit.
960 Please see <file:Documentation/arm/VFP/release-notes.txt> for
961 release notes and additional status information.
963 Say N if your target does not have VFP hardware.
967 menu "Userspace binary formats"
969 source "fs/Kconfig.binfmt"
972 tristate "RISC OS personality"
975 Say Y here to include the kernel code necessary if you want to run
976 Acorn RISC OS/Arthur binaries under Linux. This code is still very
977 experimental; if this sounds frightening, say N and sleep in peace.
978 You can also say M here to compile this support as a module (which
979 will be called arthur).
983 menu "Power management options"
985 source "kernel/power/Kconfig"
991 menu "Device Drivers"
993 source "drivers/base/Kconfig"
995 source "drivers/connector/Kconfig"
997 if ALIGNMENT_TRAP || !CPU_CP15_MMU
998 source "drivers/mtd/Kconfig"
1001 source "drivers/parport/Kconfig"
1003 source "drivers/pnp/Kconfig"
1005 source "drivers/block/Kconfig"
1007 # misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
1009 source "drivers/misc/Kconfig"
1011 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
1012 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
1013 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
1015 source "drivers/ide/Kconfig"
1018 source "drivers/scsi/Kconfig"
1020 source "drivers/ata/Kconfig"
1022 source "drivers/md/Kconfig"
1024 source "drivers/message/fusion/Kconfig"
1026 source "drivers/ieee1394/Kconfig"
1028 source "drivers/message/i2o/Kconfig"
1030 source "drivers/net/Kconfig"
1032 source "drivers/isdn/Kconfig"
1034 # input before char - char/joystick depends on it. As does USB.
1036 source "drivers/input/Kconfig"
1038 source "drivers/char/Kconfig"
1040 source "drivers/i2c/Kconfig"
1042 source "drivers/spi/Kconfig"
1044 source "drivers/w1/Kconfig"
1046 source "drivers/power/Kconfig"
1048 source "drivers/hwmon/Kconfig"
1050 source "drivers/watchdog/Kconfig"
1052 source "drivers/ssb/Kconfig"
1054 #source "drivers/l3/Kconfig"
1056 source "drivers/mfd/Kconfig"
1058 source "drivers/media/Kconfig"
1060 source "drivers/video/Kconfig"
1062 source "sound/Kconfig"
1064 source "drivers/hid/Kconfig"
1066 source "drivers/usb/Kconfig"
1068 source "drivers/mmc/Kconfig"
1070 source "drivers/leds/Kconfig"
1072 source "drivers/rtc/Kconfig"
1074 source "drivers/dma/Kconfig"
1076 source "drivers/dca/Kconfig"
1082 source "arch/arm/Kconfig.instrumentation"
1084 source "arch/arm/Kconfig.debug"
1086 source "security/Kconfig"
1088 source "crypto/Kconfig"
1090 source "lib/Kconfig"