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
342 select GENERIC_CLOCKEVENTS
344 Support for Marvell Orion System on Chip family.
347 bool "Philips Nexperia PNX4008 Mobile"
349 This enables support for Philips PNX4008 mobile platform.
352 bool "PXA2xx/PXA3xx-based"
357 select GENERIC_CLOCKEVENTS
359 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
366 select ARCH_MAY_HAVE_PC_FDC
370 On the Acorn Risc-PC, Linux can support the internal IDE disk and
371 CD-ROM interface, serial and parallel port, and the floppy drive.
376 select ARCH_DISCONTIGMEM_ENABLE
380 Support for StrongARM 11x0 based boards.
383 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
386 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
387 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
388 the Samsung SMDK2410 development board (and derivatives).
396 Support for the StrongARM based Digital DNARD machine, also known
397 as "Shark" (<http://www.shark-linux.de/shark.html>).
402 Say Y here for systems based on one of the Sharp LH7A40X
403 System on a Chip processors. These CPUs include an ARM922T
404 core with a wide array of integrated devices for
405 hand-held and low-power applications.
410 select GENERIC_CLOCKEVENTS
413 Support for TI's DaVinci platform.
420 Support for TI's OMAP platform (OMAP1 and OMAP2).
424 source "arch/arm/mach-clps711x/Kconfig"
426 source "arch/arm/mach-ep93xx/Kconfig"
428 source "arch/arm/mach-footbridge/Kconfig"
430 source "arch/arm/mach-integrator/Kconfig"
432 source "arch/arm/mach-iop32x/Kconfig"
434 source "arch/arm/mach-iop33x/Kconfig"
436 source "arch/arm/mach-iop13xx/Kconfig"
438 source "arch/arm/mach-ixp4xx/Kconfig"
440 source "arch/arm/mach-ixp2000/Kconfig"
442 source "arch/arm/mach-ixp23xx/Kconfig"
444 source "arch/arm/mach-pxa/Kconfig"
446 source "arch/arm/mach-sa1100/Kconfig"
448 source "arch/arm/plat-omap/Kconfig"
450 source "arch/arm/mach-omap1/Kconfig"
452 source "arch/arm/mach-omap2/Kconfig"
454 source "arch/arm/mach-orion/Kconfig"
456 source "arch/arm/plat-s3c24xx/Kconfig"
457 source "arch/arm/plat-s3c/Kconfig"
460 source "arch/arm/mach-s3c2400/Kconfig"
461 source "arch/arm/mach-s3c2410/Kconfig"
462 source "arch/arm/mach-s3c2412/Kconfig"
463 source "arch/arm/mach-s3c2440/Kconfig"
464 source "arch/arm/mach-s3c2442/Kconfig"
465 source "arch/arm/mach-s3c2443/Kconfig"
468 source "arch/arm/mach-lh7a40x/Kconfig"
470 source "arch/arm/mach-imx/Kconfig"
472 source "arch/arm/mach-h720x/Kconfig"
474 source "arch/arm/mach-versatile/Kconfig"
476 source "arch/arm/mach-aaec2000/Kconfig"
478 source "arch/arm/mach-realview/Kconfig"
480 source "arch/arm/mach-at91/Kconfig"
482 source "arch/arm/plat-mxc/Kconfig"
484 source "arch/arm/mach-netx/Kconfig"
486 source "arch/arm/mach-ns9xxx/Kconfig"
488 source "arch/arm/mach-davinci/Kconfig"
490 source "arch/arm/mach-ks8695/Kconfig"
492 # Definitions to make life easier
499 source arch/arm/mm/Kconfig
502 bool "Enable iWMMXt support"
503 depends on CPU_XSCALE || CPU_XSC3
504 default y if PXA27x || PXA3xx
506 Enable support for iWMMXt context switching at run time if
507 running on a CPU that supports it.
509 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
512 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
516 source "arch/arm/Kconfig-nommu"
521 source "arch/arm/common/Kconfig"
523 config FORCE_MAX_ZONEORDER
536 Find out whether you have ISA slots on your motherboard. ISA is the
537 name of a bus system, i.e. the way the CPU talks to the other stuff
538 inside your box. Other bus systems are PCI, EISA, MicroChannel
539 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
540 newer boards don't support it. If you have ISA, say Y, otherwise N.
542 # Select ISA DMA controller support
547 # Select ISA DMA interface
552 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX || ARCH_KS8695 || MACH_ARMCORE
554 Find out whether you have a PCI motherboard. PCI is the name of a
555 bus system, i.e. the way the CPU talks to the other stuff inside
556 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
557 VESA. If you have PCI, say Y, otherwise N.
559 The PCI-HOWTO, available from
560 <http://www.tldp.org/docs.html#howto>, contains valuable
561 information about which PCI hardware does work under Linux and which
567 # Select the host bridge type
568 config PCI_HOST_VIA82C505
570 depends on PCI && ARCH_SHARK
573 config PCI_HOST_ITE8152
575 depends on PCI && MACH_ARMCORE
579 source "drivers/pci/Kconfig"
581 source "drivers/pcmcia/Kconfig"
585 menu "Kernel Features"
587 source "kernel/time/Kconfig"
590 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
591 depends on EXPERIMENTAL && REALVIEW_MPCORE
593 This enables support for systems with more than one CPU. If you have
594 a system with only one CPU, like most personal computers, say N. If
595 you have a system with more than one CPU, say Y.
597 If you say N here, the kernel will run on single and multiprocessor
598 machines, but will use only one CPU of a multiprocessor machine. If
599 you say Y here, the kernel will run on many, but not all, single
600 processor machines. On a single processor machine, the kernel will
601 run faster if you say N here.
603 See also the <file:Documentation/smp.txt>,
604 <file:Documentation/i386/IO-APIC.txt>,
605 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
606 <http://www.linuxdoc.org/docs.html#howto>.
608 If you don't know what to do here, say N.
611 int "Maximum number of CPUs (2-32)"
617 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
618 depends on SMP && HOTPLUG && EXPERIMENTAL
620 Say Y here to experiment with turning CPUs off and on. CPUs
621 can be controlled through /sys/devices/system/cpu.
624 bool "Use local timer interrupts"
625 depends on SMP && REALVIEW_MPCORE
628 Enable support for local timers on SMP platforms, rather then the
629 legacy IPI broadcast method. Local timers allows the system
630 accounting to be spread across the timer interval, preventing a
631 "thundering herd" at every timer tick.
634 bool "Preemptible Kernel (EXPERIMENTAL)"
635 depends on EXPERIMENTAL
637 This option reduces the latency of the kernel when reacting to
638 real-time or interactive events by allowing a low priority process to
639 be preempted even if it is in kernel mode executing a system call.
640 This allows applications to run more reliably even when the system is
643 Say Y here if you are building a kernel for a desktop, embedded
644 or real-time system. Say N if you are unsure.
647 bool "Dynamic tick timer"
648 depends on !GENERIC_CLOCKEVENTS
650 Select this option if you want to disable continuous timer ticks
651 and have them programmed to occur as required. This option saves
652 power as the system can remain in idle state for longer.
654 By default dynamic tick is disabled during the boot, and can be
655 manually enabled with:
657 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
659 Alternatively, if you want dynamic tick automatically enabled
660 during boot, pass "dyntick=enable" via the kernel command string.
662 Please note that dynamic tick may affect the accuracy of
663 timekeeping on some platforms depending on the implementation.
664 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
665 to have accurate timekeeping with dynamic tick.
669 default 128 if ARCH_L7200
670 default 200 if ARCH_EBSA110 || ARCH_S3C2410
671 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
675 bool "Use the ARM EABI to compile the kernel"
677 This option allows for the kernel to be compiled using the latest
678 ARM ABI (aka EABI). This is only useful if you are using a user
679 space environment that is also compiled with EABI.
681 Since there are major incompatibilities between the legacy ABI and
682 EABI, especially with regard to structure member alignment, this
683 option also changes the kernel syscall calling convention to
684 disambiguate both ABIs and allow for backward compatibility support
685 (selected with CONFIG_OABI_COMPAT).
687 To use this you need GCC version 4.0.0 or later.
690 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
691 depends on AEABI && EXPERIMENTAL
694 This option preserves the old syscall interface along with the
695 new (ARM EABI) one. It also provides a compatibility layer to
696 intercept syscalls that have structure arguments which layout
697 in memory differs between the legacy ABI and the new ARM EABI
698 (only for non "thumb" binaries). This option adds a tiny
699 overhead to all syscalls and produces a slightly larger kernel.
700 If you know you'll be using only pure EABI user space then you
701 can say N here. If this option is not selected and you attempt
702 to execute a legacy ABI binary then the result will be
703 UNPREDICTABLE (in fact it can be predicted that it won't work
704 at all). If in doubt say Y.
706 config ARCH_DISCONTIGMEM_ENABLE
708 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
710 Say Y to support efficient handling of discontiguous physical memory,
711 for architectures which are either NUMA (Non-Uniform Memory Access)
712 or have huge holes in the physical address space for other reasons.
713 See <file:Documentation/vm/numa> for more.
717 default "4" if ARCH_LH7A40X
719 depends on NEED_MULTIPLE_NODES
724 bool "Timer and CPU usage LEDs"
725 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
726 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
727 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
728 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
729 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
730 ARCH_AT91 || MACH_TRIZEPS4 || ARCH_DAVINCI || \
733 If you say Y here, the LEDs on your machine will be used
734 to provide useful information about your current system status.
736 If you are compiling a kernel for a NetWinder or EBSA-285, you will
737 be able to select which LEDs are active using the options below. If
738 you are compiling a kernel for the EBSA-110 or the LART however, the
739 red LED will simply flash regularly to indicate that the system is
740 still functional. It is safe to say Y here if you have a CATS
741 system, but the driver will do nothing.
744 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
745 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
746 || MACH_OMAP_PERSEUS2
748 depends on !GENERIC_CLOCKEVENTS
749 default y if ARCH_EBSA110
751 If you say Y here, one of the system LEDs (the green one on the
752 NetWinder, the amber one on the EBSA285, or the red one on the LART)
753 will flash regularly to indicate that the system is still
754 operational. This is mainly useful to kernel hackers who are
755 debugging unstable kernels.
757 The LART uses the same LED for both Timer LED and CPU usage LED
758 functions. You may choose to use both, but the Timer LED function
759 will overrule the CPU usage LED.
762 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
764 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
765 || MACH_OMAP_PERSEUS2
768 If you say Y here, the red LED will be used to give a good real
769 time indication of CPU usage, by lighting whenever the idle task
770 is not currently executing.
772 The LART uses the same LED for both Timer LED and CPU usage LED
773 functions. You may choose to use both, but the Timer LED function
774 will overrule the CPU usage LED.
776 config ALIGNMENT_TRAP
778 depends on CPU_CP15_MMU
779 default y if !ARCH_EBSA110
781 ARM processors cannot fetch/store information which is not
782 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
783 address divisible by 4. On 32-bit ARM processors, these non-aligned
784 fetch/store instructions will be emulated in software if you say
785 here, which has a severe performance impact. This is necessary for
786 correct operation of some network protocols. With an IP-only
787 configuration it is safe to say N, otherwise say Y.
793 # Compressed boot loader in ROM. Yes, we really want to ask about
794 # TEXT and BSS so we preserve their values in the config files.
795 config ZBOOT_ROM_TEXT
796 hex "Compressed ROM boot loader base address"
799 The physical address at which the ROM-able zImage is to be
800 placed in the target. Platforms which normally make use of
801 ROM-able zImage formats normally set this to a suitable
802 value in their defconfig file.
804 If ZBOOT_ROM is not enabled, this has no effect.
807 hex "Compressed ROM boot loader BSS address"
810 The base address of an area of read/write memory in the target
811 for the ROM-able zImage which must be available while the
812 decompressor is running. It must be large enough to hold the
813 entire decompressed kernel plus an additional 128 KiB.
814 Platforms which normally make use of ROM-able zImage formats
815 normally set this to a suitable value in their defconfig file.
817 If ZBOOT_ROM is not enabled, this has no effect.
820 bool "Compressed boot loader in ROM/flash"
821 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
823 Say Y here if you intend to execute your compressed kernel image
824 (zImage) directly from ROM or flash. If unsure, say N.
827 string "Default kernel command string"
830 On some architectures (EBSA110 and CATS), there is currently no way
831 for the boot loader to pass arguments to the kernel. For these
832 architectures, you should supply some command-line options at build
833 time by entering them here. As a minimum, you should specify the
834 memory size and the root device (e.g., mem=64M root=/dev/nfs).
837 bool "Kernel Execute-In-Place from ROM"
838 depends on !ZBOOT_ROM
840 Execute-In-Place allows the kernel to run from non-volatile storage
841 directly addressable by the CPU, such as NOR flash. This saves RAM
842 space since the text section of the kernel is not loaded from flash
843 to RAM. Read-write sections, such as the data section and stack,
844 are still copied to RAM. The XIP kernel is not compressed since
845 it has to run directly from flash, so it will take more space to
846 store it. The flash address used to link the kernel object files,
847 and for storing it, is configuration dependent. Therefore, if you
848 say Y here, you must know the proper physical address where to
849 store the kernel image depending on your own flash memory usage.
851 Also note that the make target becomes "make xipImage" rather than
852 "make zImage" or "make Image". The final kernel binary to put in
853 ROM memory will be arch/arm/boot/xipImage.
858 hex "XIP Kernel Physical Location"
859 depends on XIP_KERNEL
862 This is the physical address in your flash memory the kernel will
863 be linked for and stored to. This address is dependent on your
867 bool "Kexec system call (EXPERIMENTAL)"
868 depends on EXPERIMENTAL
870 kexec is a system call that implements the ability to shutdown your
871 current kernel, and to start another kernel. It is like a reboot
872 but it is independent of the system firmware. And like a reboot
873 you can start any kernel with it, not just Linux.
875 It is an ongoing process to be certain the hardware in a machine
876 is properly shutdown, so do not be surprised if this code does not
877 initially work for you. It may help to enable device hotplugging
882 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
884 menu "CPU Frequency scaling"
886 source "drivers/cpufreq/Kconfig"
888 config CPU_FREQ_SA1100
890 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
893 config CPU_FREQ_SA1110
895 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
898 config CPU_FREQ_INTEGRATOR
899 tristate "CPUfreq driver for ARM Integrator CPUs"
900 depends on ARCH_INTEGRATOR && CPU_FREQ
903 This enables the CPUfreq driver for ARM Integrator CPUs.
905 For details, take a look at <file:Documentation/cpu-freq>.
910 tristate "CPUfreq driver for i.MX CPUs"
911 depends on ARCH_IMX && CPU_FREQ
914 This enables the CPUfreq driver for i.MX CPUs.
922 menu "Floating point emulation"
924 comment "At least one emulation must be selected"
927 bool "NWFPE math emulation"
928 depends on !AEABI || OABI_COMPAT
930 Say Y to include the NWFPE floating point emulator in the kernel.
931 This is necessary to run most binaries. Linux does not currently
932 support floating point hardware so you need to say Y here even if
933 your machine has an FPA or floating point co-processor podule.
935 You may say N here if you are going to load the Acorn FPEmulator
939 bool "Support extended precision"
942 Say Y to include 80-bit support in the kernel floating-point
943 emulator. Otherwise, only 32 and 64-bit support is compiled in.
944 Note that gcc does not generate 80-bit operations by default,
945 so in most cases this option only enlarges the size of the
946 floating point emulator without any good reason.
948 You almost surely want to say N here.
951 bool "FastFPE math emulation (EXPERIMENTAL)"
952 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
954 Say Y here to include the FAST floating point emulator in the kernel.
955 This is an experimental much faster emulator which now also has full
956 precision for the mantissa. It does not support any exceptions.
957 It is very simple, and approximately 3-6 times faster than NWFPE.
959 It should be sufficient for most programs. It may be not suitable
960 for scientific calculations, but you have to check this for yourself.
961 If you do not feel you need a faster FP emulation you should better
965 bool "VFP-format floating point maths"
966 depends on CPU_V6 || CPU_ARM926T || CPU_FEROCEON
968 Say Y to include VFP support code in the kernel. This is needed
969 if your hardware includes a VFP unit.
971 Please see <file:Documentation/arm/VFP/release-notes.txt> for
972 release notes and additional status information.
974 Say N if your target does not have VFP hardware.
978 menu "Userspace binary formats"
980 source "fs/Kconfig.binfmt"
983 tristate "RISC OS personality"
986 Say Y here to include the kernel code necessary if you want to run
987 Acorn RISC OS/Arthur binaries under Linux. This code is still very
988 experimental; if this sounds frightening, say N and sleep in peace.
989 You can also say M here to compile this support as a module (which
990 will be called arthur).
994 menu "Power management options"
996 source "kernel/power/Kconfig"
1000 source "net/Kconfig"
1002 menu "Device Drivers"
1004 source "drivers/base/Kconfig"
1006 source "drivers/connector/Kconfig"
1008 if ALIGNMENT_TRAP || !CPU_CP15_MMU
1009 source "drivers/mtd/Kconfig"
1012 source "drivers/parport/Kconfig"
1014 source "drivers/pnp/Kconfig"
1016 source "drivers/block/Kconfig"
1018 # misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
1020 source "drivers/misc/Kconfig"
1022 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
1023 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
1024 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
1026 source "drivers/ide/Kconfig"
1029 source "drivers/scsi/Kconfig"
1031 source "drivers/ata/Kconfig"
1033 source "drivers/md/Kconfig"
1035 source "drivers/message/fusion/Kconfig"
1037 source "drivers/ieee1394/Kconfig"
1039 source "drivers/message/i2o/Kconfig"
1041 source "drivers/net/Kconfig"
1043 source "drivers/isdn/Kconfig"
1045 # input before char - char/joystick depends on it. As does USB.
1047 source "drivers/input/Kconfig"
1049 source "drivers/char/Kconfig"
1051 source "drivers/i2c/Kconfig"
1053 source "drivers/spi/Kconfig"
1055 source "drivers/w1/Kconfig"
1057 source "drivers/power/Kconfig"
1059 source "drivers/hwmon/Kconfig"
1061 source "drivers/watchdog/Kconfig"
1063 source "drivers/ssb/Kconfig"
1065 #source "drivers/l3/Kconfig"
1067 source "drivers/mfd/Kconfig"
1069 source "drivers/media/Kconfig"
1071 source "drivers/video/Kconfig"
1073 source "sound/Kconfig"
1075 source "drivers/hid/Kconfig"
1077 source "drivers/usb/Kconfig"
1079 source "drivers/mmc/Kconfig"
1081 source "drivers/leds/Kconfig"
1083 source "drivers/rtc/Kconfig"
1085 source "drivers/dma/Kconfig"
1087 source "drivers/dca/Kconfig"
1093 source "arch/arm/Kconfig.instrumentation"
1095 source "arch/arm/Kconfig.debug"
1097 source "security/Kconfig"
1099 source "crypto/Kconfig"
1101 source "lib/Kconfig"