2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
13 The ARM series is a line of low-power-consumption RISC chip designs
14 licensed by ARM Ltd and targeted at embedded applications and
15 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
16 manufactured, but legacy ARM-based PC hardware remains popular in
17 Europe. There is an ARM Linux project with a web page at
18 <http://www.arm.linux.org.uk/>.
31 The Extended Industry Standard Architecture (EISA) bus was
32 developed as an open alternative to the IBM MicroChannel bus.
34 The EISA bus provided some of the features of the IBM MicroChannel
35 bus while maintaining backward compatibility with cards made for
36 the older ISA bus. The EISA bus saw limited use between 1988 and
37 1995 when it was made obsolete by the PCI bus.
39 Say Y here if you are building a kernel for an EISA-based machine.
49 MicroChannel Architecture is found in some IBM PS/2 machines and
50 laptops. It is a bus system similar to PCI or ISA. See
51 <file:Documentation/mca.txt> (and especially the web page given
52 there) before attempting to build an MCA bus kernel.
54 config GENERIC_HARDIRQS
58 config TRACE_IRQFLAGS_SUPPORT
62 config HARDIRQS_SW_RESEND
66 config GENERIC_IRQ_PROBE
70 config RWSEM_GENERIC_SPINLOCK
74 config RWSEM_XCHGADD_ALGORITHM
77 config ARCH_HAS_ILOG2_U32
81 config ARCH_HAS_ILOG2_U64
85 config GENERIC_HWEIGHT
89 config GENERIC_CALIBRATE_DELAY
93 config GENERIC_BUST_SPINLOCK
96 config ARCH_MAY_HAVE_PC_FDC
99 config GENERIC_ISA_DMA
110 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
111 default DRAM_BASE if REMAP_VECTORS_TO_RAM
114 The base address of exception vectors.
116 source "init/Kconfig"
121 prompt "ARM system type"
122 default ARCH_VERSATILE
125 bool "Agilent AAEC-2000 based"
128 This enables support for systems based on the Agilent AAEC-2000
130 config ARCH_INTEGRATOR
131 bool "ARM Ltd. Integrator family"
135 Support for ARM's Integrator platform.
138 bool "ARM Ltd. RealView family"
142 This enables support for ARM Ltd RealView boards.
144 config ARCH_VERSATILE
145 bool "ARM Ltd. Versatile family"
150 This enables support for ARM Ltd Versatile board.
155 This enables support for systems based on the Atmel AT91RM9200
156 and AT91SAM9xxx processors.
159 bool "Cirrus CL-PS7500FE"
163 Support for the Cirrus Logic PS7500FE system-on-a-chip.
166 bool "Cirrus Logic CLPS711x/EP721x-based"
168 Support for Cirrus Logic 711x/721x based boards.
173 select FOOTBRIDGE_ADDIN
175 Support for Intel's EBSA285 companion chip.
181 This is an evaluation board for the StrongARM processor available
182 from Digital. It has limited hardware on-board, including an
183 Ethernet interface, two PCMCIA sockets, two serial ports and a
191 This enables support for the Cirrus EP93xx series of CPUs.
193 config ARCH_FOOTBRIDGE
197 Support for systems based on the DC21285 companion chip
198 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
201 bool "Hilscher NetX based"
204 This enables support for systems based on the Hilscher NetX Soc
207 bool "Hynix HMS720x-based"
210 This enables support for systems based on the Hynix HMS720x
215 Support for Motorola's i.MX family of processors (MX1, MXL).
223 Support for Intel's 80219 and IOP32X (XScale) family of
232 Support for Intel's IOP33X (XScale) family of processors.
238 Support for Intel's IOP13XX (XScale) family of processors.
245 Support for Intel's IXP4XX (XScale) family of processors.
248 bool "IXP2400/2800-based"
252 Support for Intel's IXP2400/2800 (XScale) family of processors.
259 Support for Intel's IXP23xx (XScale) family of processors.
265 Say Y here if you intend to run this kernel on a LinkUp Systems
266 L7200 Software Development Board which uses an ARM720T processor.
267 Information on this board can be obtained at:
269 <http://www.linkupsys.com/>
271 If you have any questions or comments about the Linux kernel port
272 to this board, send e-mail to <sjhill@cotw.com>.
275 bool "NetSilicon NS9xxx"
277 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
280 <http://www.digi.com/products/microprocessors/index.jsp>
283 bool "Philips Nexperia PNX4008 Mobile"
285 This enables support for Philips PNX4008 mobile platform.
293 Support for Intel's PXA2XX processor line.
300 select ARCH_MAY_HAVE_PC_FDC
303 On the Acorn Risc-PC, Linux can support the internal IDE disk and
304 CD-ROM interface, serial and parallel port, and the floppy drive.
309 select ARCH_DISCONTIGMEM_ENABLE
312 Support for StrongARM 11x0 based boards.
315 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
317 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
318 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
319 the Samsung SMDK2410 development board (and derivatives).
327 Support for the StrongARM based Digital DNARD machine, also known
328 as "Shark" (<http://www.shark-linux.de/shark.html>).
333 Say Y here for systems based on one of the Sharp LH7A40X
334 System on a Chip processors. These CPUs include an ARM922T
335 core with a wide array of integrated devices for
336 hand-held and low-power applications.
341 Support for TI's OMAP platform (OMAP1 and OMAP2).
345 source "arch/arm/mach-clps711x/Kconfig"
347 source "arch/arm/mach-ep93xx/Kconfig"
349 source "arch/arm/mach-footbridge/Kconfig"
351 source "arch/arm/mach-integrator/Kconfig"
353 source "arch/arm/mach-iop32x/Kconfig"
355 source "arch/arm/mach-iop33x/Kconfig"
357 source "arch/arm/mach-iop13xx/Kconfig"
359 source "arch/arm/mach-ixp4xx/Kconfig"
361 source "arch/arm/mach-ixp2000/Kconfig"
363 source "arch/arm/mach-ixp23xx/Kconfig"
365 source "arch/arm/mach-pxa/Kconfig"
367 source "arch/arm/mach-sa1100/Kconfig"
369 source "arch/arm/plat-omap/Kconfig"
371 source "arch/arm/mach-omap1/Kconfig"
373 source "arch/arm/mach-omap2/Kconfig"
375 source "arch/arm/plat-s3c24xx/Kconfig"
378 source "arch/arm/mach-s3c2400/Kconfig"
379 source "arch/arm/mach-s3c2410/Kconfig"
380 source "arch/arm/mach-s3c2412/Kconfig"
381 source "arch/arm/mach-s3c2440/Kconfig"
382 source "arch/arm/mach-s3c2442/Kconfig"
383 source "arch/arm/mach-s3c2443/Kconfig"
386 source "arch/arm/mach-lh7a40x/Kconfig"
388 source "arch/arm/mach-imx/Kconfig"
390 source "arch/arm/mach-h720x/Kconfig"
392 source "arch/arm/mach-versatile/Kconfig"
394 source "arch/arm/mach-aaec2000/Kconfig"
396 source "arch/arm/mach-realview/Kconfig"
398 source "arch/arm/mach-at91/Kconfig"
400 source "arch/arm/mach-netx/Kconfig"
402 source "arch/arm/mach-ns9xxx/Kconfig"
404 # Definitions to make life easier
411 source arch/arm/mm/Kconfig
414 bool "Enable iWMMXt support"
415 depends CPU_XSCALE || CPU_XSC3
418 Enable support for iWMMXt context switching at run time if
419 running on a CPU that supports it.
421 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
424 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
428 source "arch/arm/Kconfig-nommu"
433 source "arch/arm/common/Kconfig"
435 config FORCE_MAX_ZONEORDER
448 Find out whether you have ISA slots on your motherboard. ISA is the
449 name of a bus system, i.e. the way the CPU talks to the other stuff
450 inside your box. Other bus systems are PCI, EISA, MicroChannel
451 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
452 newer boards don't support it. If you have ISA, say Y, otherwise N.
454 # Select ISA DMA controller support
459 # Select ISA DMA interface
464 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
466 Find out whether you have a PCI motherboard. PCI is the name of a
467 bus system, i.e. the way the CPU talks to the other stuff inside
468 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
469 VESA. If you have PCI, say Y, otherwise N.
471 The PCI-HOWTO, available from
472 <http://www.tldp.org/docs.html#howto>, contains valuable
473 information about which PCI hardware does work under Linux and which
476 # Select the host bridge type
477 config PCI_HOST_VIA82C505
479 depends on PCI && ARCH_SHARK
482 source "drivers/pci/Kconfig"
484 source "drivers/pcmcia/Kconfig"
488 menu "Kernel Features"
491 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
492 depends on EXPERIMENTAL && REALVIEW_MPCORE
494 This enables support for systems with more than one CPU. If you have
495 a system with only one CPU, like most personal computers, say N. If
496 you have a system with more than one CPU, say Y.
498 If you say N here, the kernel will run on single and multiprocessor
499 machines, but will use only one CPU of a multiprocessor machine. If
500 you say Y here, the kernel will run on many, but not all, single
501 processor machines. On a single processor machine, the kernel will
502 run faster if you say N here.
504 See also the <file:Documentation/smp.txt>,
505 <file:Documentation/i386/IO-APIC.txt>,
506 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
507 <http://www.linuxdoc.org/docs.html#howto>.
509 If you don't know what to do here, say N.
512 int "Maximum number of CPUs (2-32)"
518 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
519 depends on SMP && HOTPLUG && EXPERIMENTAL
521 Say Y here to experiment with turning CPUs off and on. CPUs
522 can be controlled through /sys/devices/system/cpu.
525 bool "Use local timer interrupts"
526 depends on SMP && REALVIEW_MPCORE
529 Enable support for local timers on SMP platforms, rather then the
530 legacy IPI broadcast method. Local timers allows the system
531 accounting to be spread across the timer interval, preventing a
532 "thundering herd" at every timer tick.
535 bool "Preemptible Kernel (EXPERIMENTAL)"
536 depends on EXPERIMENTAL
538 This option reduces the latency of the kernel when reacting to
539 real-time or interactive events by allowing a low priority process to
540 be preempted even if it is in kernel mode executing a system call.
541 This allows applications to run more reliably even when the system is
544 Say Y here if you are building a kernel for a desktop, embedded
545 or real-time system. Say N if you are unsure.
548 bool "Dynamic tick timer"
550 Select this option if you want to disable continuous timer ticks
551 and have them programmed to occur as required. This option saves
552 power as the system can remain in idle state for longer.
554 By default dynamic tick is disabled during the boot, and can be
555 manually enabled with:
557 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
559 Alternatively, if you want dynamic tick automatically enabled
560 during boot, pass "dyntick=enable" via the kernel command string.
562 Please note that dynamic tick may affect the accuracy of
563 timekeeping on some platforms depending on the implementation.
564 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
565 to have accurate timekeeping with dynamic tick.
569 default 128 if ARCH_L7200
570 default 200 if ARCH_EBSA110 || ARCH_S3C2410
571 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
575 bool "Use the ARM EABI to compile the kernel"
577 This option allows for the kernel to be compiled using the latest
578 ARM ABI (aka EABI). This is only useful if you are using a user
579 space environment that is also compiled with EABI.
581 Since there are major incompatibilities between the legacy ABI and
582 EABI, especially with regard to structure member alignment, this
583 option also changes the kernel syscall calling convention to
584 disambiguate both ABIs and allow for backward compatibility support
585 (selected with CONFIG_OABI_COMPAT).
587 To use this you need GCC version 4.0.0 or later.
590 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
591 depends on AEABI && EXPERIMENTAL
594 This option preserves the old syscall interface along with the
595 new (ARM EABI) one. It also provides a compatibility layer to
596 intercept syscalls that have structure arguments which layout
597 in memory differs between the legacy ABI and the new ARM EABI
598 (only for non "thumb" binaries). This option adds a tiny
599 overhead to all syscalls and produces a slightly larger kernel.
600 If you know you'll be using only pure EABI user space then you
601 can say N here. If this option is not selected and you attempt
602 to execute a legacy ABI binary then the result will be
603 UNPREDICTABLE (in fact it can be predicted that it won't work
604 at all). If in doubt say Y.
606 config ARCH_DISCONTIGMEM_ENABLE
608 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
610 Say Y to support efficient handling of discontiguous physical memory,
611 for architectures which are either NUMA (Non-Uniform Memory Access)
612 or have huge holes in the physical address space for other reasons.
613 See <file:Documentation/vm/numa> for more.
617 default "4" if ARCH_LH7A40X
619 depends on NEED_MULTIPLE_NODES
624 bool "Timer and CPU usage LEDs"
625 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
626 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
627 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
628 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
629 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
630 ARCH_AT91 || MACH_TRIZEPS4
632 If you say Y here, the LEDs on your machine will be used
633 to provide useful information about your current system status.
635 If you are compiling a kernel for a NetWinder or EBSA-285, you will
636 be able to select which LEDs are active using the options below. If
637 you are compiling a kernel for the EBSA-110 or the LART however, the
638 red LED will simply flash regularly to indicate that the system is
639 still functional. It is safe to say Y here if you have a CATS
640 system, but the driver will do nothing.
643 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
644 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
646 default y if ARCH_EBSA110
648 If you say Y here, one of the system LEDs (the green one on the
649 NetWinder, the amber one on the EBSA285, or the red one on the LART)
650 will flash regularly to indicate that the system is still
651 operational. This is mainly useful to kernel hackers who are
652 debugging unstable kernels.
654 The LART uses the same LED for both Timer LED and CPU usage LED
655 functions. You may choose to use both, but the Timer LED function
656 will overrule the CPU usage LED.
659 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
660 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
663 If you say Y here, the red LED will be used to give a good real
664 time indication of CPU usage, by lighting whenever the idle task
665 is not currently executing.
667 The LART uses the same LED for both Timer LED and CPU usage LED
668 functions. You may choose to use both, but the Timer LED function
669 will overrule the CPU usage LED.
671 config ALIGNMENT_TRAP
673 depends on CPU_CP15_MMU
674 default y if !ARCH_EBSA110
676 ARM processors cannot fetch/store information which is not
677 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
678 address divisible by 4. On 32-bit ARM processors, these non-aligned
679 fetch/store instructions will be emulated in software if you say
680 here, which has a severe performance impact. This is necessary for
681 correct operation of some network protocols. With an IP-only
682 configuration it is safe to say N, otherwise say Y.
688 # Compressed boot loader in ROM. Yes, we really want to ask about
689 # TEXT and BSS so we preserve their values in the config files.
690 config ZBOOT_ROM_TEXT
691 hex "Compressed ROM boot loader base address"
694 The physical address at which the ROM-able zImage is to be
695 placed in the target. Platforms which normally make use of
696 ROM-able zImage formats normally set this to a suitable
697 value in their defconfig file.
699 If ZBOOT_ROM is not enabled, this has no effect.
702 hex "Compressed ROM boot loader BSS address"
705 The base address of an area of read/write memory in the target
706 for the ROM-able zImage which must be available while the
707 decompressor is running. It must be large enough to hold the
708 entire decompressed kernel plus an additional 128 KiB.
709 Platforms which normally make use of ROM-able zImage formats
710 normally set this to a suitable value in their defconfig file.
712 If ZBOOT_ROM is not enabled, this has no effect.
715 bool "Compressed boot loader in ROM/flash"
716 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
718 Say Y here if you intend to execute your compressed kernel image
719 (zImage) directly from ROM or flash. If unsure, say N.
722 string "Default kernel command string"
725 On some architectures (EBSA110 and CATS), there is currently no way
726 for the boot loader to pass arguments to the kernel. For these
727 architectures, you should supply some command-line options at build
728 time by entering them here. As a minimum, you should specify the
729 memory size and the root device (e.g., mem=64M root=/dev/nfs).
732 bool "Kernel Execute-In-Place from ROM"
733 depends on !ZBOOT_ROM
735 Execute-In-Place allows the kernel to run from non-volatile storage
736 directly addressable by the CPU, such as NOR flash. This saves RAM
737 space since the text section of the kernel is not loaded from flash
738 to RAM. Read-write sections, such as the data section and stack,
739 are still copied to RAM. The XIP kernel is not compressed since
740 it has to run directly from flash, so it will take more space to
741 store it. The flash address used to link the kernel object files,
742 and for storing it, is configuration dependent. Therefore, if you
743 say Y here, you must know the proper physical address where to
744 store the kernel image depending on your own flash memory usage.
746 Also note that the make target becomes "make xipImage" rather than
747 "make zImage" or "make Image". The final kernel binary to put in
748 ROM memory will be arch/arm/boot/xipImage.
753 hex "XIP Kernel Physical Location"
754 depends on XIP_KERNEL
757 This is the physical address in your flash memory the kernel will
758 be linked for and stored to. This address is dependent on your
762 bool "Kexec system call (EXPERIMENTAL)"
763 depends on EXPERIMENTAL
765 kexec is a system call that implements the ability to shutdown your
766 current kernel, and to start another kernel. It is like a reboot
767 but it is indepedent of the system firmware. And like a reboot
768 you can start any kernel with it, not just Linux.
770 It is an ongoing process to be certain the hardware in a machine
771 is properly shutdown, so do not be surprised if this code does not
772 initially work for you. It may help to enable device hotplugging
777 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
779 menu "CPU Frequency scaling"
781 source "drivers/cpufreq/Kconfig"
783 config CPU_FREQ_SA1100
785 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
788 config CPU_FREQ_SA1110
790 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
793 config CPU_FREQ_INTEGRATOR
794 tristate "CPUfreq driver for ARM Integrator CPUs"
795 depends on ARCH_INTEGRATOR && CPU_FREQ
798 This enables the CPUfreq driver for ARM Integrator CPUs.
800 For details, take a look at <file:Documentation/cpu-freq>.
805 tristate "CPUfreq driver for i.MX CPUs"
806 depends on ARCH_IMX && CPU_FREQ
809 This enables the CPUfreq driver for i.MX CPUs.
817 menu "Floating point emulation"
819 comment "At least one emulation must be selected"
822 bool "NWFPE math emulation"
823 depends on !AEABI || OABI_COMPAT
825 Say Y to include the NWFPE floating point emulator in the kernel.
826 This is necessary to run most binaries. Linux does not currently
827 support floating point hardware so you need to say Y here even if
828 your machine has an FPA or floating point co-processor podule.
830 You may say N here if you are going to load the Acorn FPEmulator
834 bool "Support extended precision"
837 Say Y to include 80-bit support in the kernel floating-point
838 emulator. Otherwise, only 32 and 64-bit support is compiled in.
839 Note that gcc does not generate 80-bit operations by default,
840 so in most cases this option only enlarges the size of the
841 floating point emulator without any good reason.
843 You almost surely want to say N here.
846 bool "FastFPE math emulation (EXPERIMENTAL)"
847 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
849 Say Y here to include the FAST floating point emulator in the kernel.
850 This is an experimental much faster emulator which now also has full
851 precision for the mantissa. It does not support any exceptions.
852 It is very simple, and approximately 3-6 times faster than NWFPE.
854 It should be sufficient for most programs. It may be not suitable
855 for scientific calculations, but you have to check this for yourself.
856 If you do not feel you need a faster FP emulation you should better
860 bool "VFP-format floating point maths"
861 depends on CPU_V6 || CPU_ARM926T
863 Say Y to include VFP support code in the kernel. This is needed
864 if your hardware includes a VFP unit.
866 Please see <file:Documentation/arm/VFP/release-notes.txt> for
867 release notes and additional status information.
869 Say N if your target does not have VFP hardware.
873 menu "Userspace binary formats"
875 source "fs/Kconfig.binfmt"
878 tristate "RISC OS personality"
881 Say Y here to include the kernel code necessary if you want to run
882 Acorn RISC OS/Arthur binaries under Linux. This code is still very
883 experimental; if this sounds frightening, say N and sleep in peace.
884 You can also say M here to compile this support as a module (which
885 will be called arthur).
889 menu "Power management options"
891 source "kernel/power/Kconfig"
894 tristate "Advanced Power Management Emulation"
896 APM is a BIOS specification for saving power using several different
897 techniques. This is mostly useful for battery powered laptops with
898 APM compliant BIOSes. If you say Y here, the system time will be
899 reset after a RESUME operation, the /proc/apm device will provide
900 battery status information, and user-space programs will receive
901 notification of APM "events" (e.g. battery status change).
903 In order to use APM, you will need supporting software. For location
904 and more information, read <file:Documentation/pm.txt> and the
905 Battery Powered Linux mini-HOWTO, available from
906 <http://www.tldp.org/docs.html#howto>.
908 This driver does not spin down disk drives (see the hdparm(8)
909 manpage ("man 8 hdparm") for that), and it doesn't turn off
910 VESA-compliant "green" monitors.
912 Generally, if you don't have a battery in your machine, there isn't
913 much point in using this driver and you should say N. If you get
914 random kernel OOPSes or reboots that don't seem to be related to
915 anything, try disabling/enabling this option (or disabling/enabling
922 menu "Device Drivers"
924 source "drivers/base/Kconfig"
926 source "drivers/connector/Kconfig"
928 if ALIGNMENT_TRAP || !CPU_CP15_MMU
929 source "drivers/mtd/Kconfig"
932 source "drivers/parport/Kconfig"
934 source "drivers/pnp/Kconfig"
936 source "drivers/block/Kconfig"
938 source "drivers/acorn/block/Kconfig"
940 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
941 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
942 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
944 source "drivers/ide/Kconfig"
947 source "drivers/scsi/Kconfig"
949 source "drivers/ata/Kconfig"
951 source "drivers/md/Kconfig"
953 source "drivers/message/fusion/Kconfig"
955 source "drivers/ieee1394/Kconfig"
957 source "drivers/message/i2o/Kconfig"
959 source "drivers/net/Kconfig"
961 source "drivers/isdn/Kconfig"
963 # input before char - char/joystick depends on it. As does USB.
965 source "drivers/input/Kconfig"
967 source "drivers/char/Kconfig"
969 source "drivers/i2c/Kconfig"
971 source "drivers/spi/Kconfig"
973 source "drivers/w1/Kconfig"
975 source "drivers/hwmon/Kconfig"
977 #source "drivers/l3/Kconfig"
979 source "drivers/misc/Kconfig"
981 source "drivers/mfd/Kconfig"
983 source "drivers/leds/Kconfig"
985 source "drivers/media/Kconfig"
987 source "drivers/video/Kconfig"
989 source "sound/Kconfig"
991 source "drivers/hid/Kconfig"
993 source "drivers/usb/Kconfig"
995 source "drivers/mmc/Kconfig"
997 source "drivers/rtc/Kconfig"
1003 source "arch/arm/oprofile/Kconfig"
1005 source "arch/arm/Kconfig.debug"
1007 source "security/Kconfig"
1009 source "crypto/Kconfig"
1011 source "lib/Kconfig"