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.
240 Support for Intel's IOP13XX (XScale) family of processors.
247 Support for Intel's IXP4XX (XScale) family of processors.
250 bool "IXP2400/2800-based"
254 Support for Intel's IXP2400/2800 (XScale) family of processors.
261 Support for Intel's IXP23xx (XScale) family of processors.
267 Say Y here if you intend to run this kernel on a LinkUp Systems
268 L7200 Software Development Board which uses an ARM720T processor.
269 Information on this board can be obtained at:
271 <http://www.linkupsys.com/>
273 If you have any questions or comments about the Linux kernel port
274 to this board, send e-mail to <sjhill@cotw.com>.
277 bool "NetSilicon NS9xxx"
279 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
282 <http://www.digi.com/products/microprocessors/index.jsp>
285 bool "Philips Nexperia PNX4008 Mobile"
287 This enables support for Philips PNX4008 mobile platform.
295 Support for Intel's PXA2XX processor line.
302 select ARCH_MAY_HAVE_PC_FDC
305 On the Acorn Risc-PC, Linux can support the internal IDE disk and
306 CD-ROM interface, serial and parallel port, and the floppy drive.
311 select ARCH_DISCONTIGMEM_ENABLE
314 Support for StrongARM 11x0 based boards.
317 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
319 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
320 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
321 the Samsung SMDK2410 development board (and derivatives).
329 Support for the StrongARM based Digital DNARD machine, also known
330 as "Shark" (<http://www.shark-linux.de/shark.html>).
335 Say Y here for systems based on one of the Sharp LH7A40X
336 System on a Chip processors. These CPUs include an ARM922T
337 core with a wide array of integrated devices for
338 hand-held and low-power applications.
343 Support for TI's OMAP platform (OMAP1 and OMAP2).
347 source "arch/arm/mach-clps711x/Kconfig"
349 source "arch/arm/mach-ep93xx/Kconfig"
351 source "arch/arm/mach-footbridge/Kconfig"
353 source "arch/arm/mach-integrator/Kconfig"
355 source "arch/arm/mach-iop32x/Kconfig"
357 source "arch/arm/mach-iop33x/Kconfig"
359 source "arch/arm/mach-iop13xx/Kconfig"
361 source "arch/arm/mach-ixp4xx/Kconfig"
363 source "arch/arm/mach-ixp2000/Kconfig"
365 source "arch/arm/mach-ixp23xx/Kconfig"
367 source "arch/arm/mach-pxa/Kconfig"
369 source "arch/arm/mach-sa1100/Kconfig"
371 source "arch/arm/plat-omap/Kconfig"
373 source "arch/arm/mach-omap1/Kconfig"
375 source "arch/arm/mach-omap2/Kconfig"
377 source "arch/arm/plat-s3c24xx/Kconfig"
380 source "arch/arm/mach-s3c2400/Kconfig"
381 source "arch/arm/mach-s3c2410/Kconfig"
382 source "arch/arm/mach-s3c2412/Kconfig"
383 source "arch/arm/mach-s3c2440/Kconfig"
384 source "arch/arm/mach-s3c2442/Kconfig"
385 source "arch/arm/mach-s3c2443/Kconfig"
388 source "arch/arm/mach-lh7a40x/Kconfig"
390 source "arch/arm/mach-imx/Kconfig"
392 source "arch/arm/mach-h720x/Kconfig"
394 source "arch/arm/mach-versatile/Kconfig"
396 source "arch/arm/mach-aaec2000/Kconfig"
398 source "arch/arm/mach-realview/Kconfig"
400 source "arch/arm/mach-at91/Kconfig"
402 source "arch/arm/mach-netx/Kconfig"
404 source "arch/arm/mach-ns9xxx/Kconfig"
406 # Definitions to make life easier
413 source arch/arm/mm/Kconfig
416 bool "Enable iWMMXt support"
417 depends CPU_XSCALE || CPU_XSC3
420 Enable support for iWMMXt context switching at run time if
421 running on a CPU that supports it.
423 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
426 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
430 source "arch/arm/Kconfig-nommu"
435 source "arch/arm/common/Kconfig"
437 config FORCE_MAX_ZONEORDER
450 Find out whether you have ISA slots on your motherboard. ISA is the
451 name of a bus system, i.e. the way the CPU talks to the other stuff
452 inside your box. Other bus systems are PCI, EISA, MicroChannel
453 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
454 newer boards don't support it. If you have ISA, say Y, otherwise N.
456 # Select ISA DMA controller support
461 # Select ISA DMA interface
466 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
468 Find out whether you have a PCI motherboard. PCI is the name of a
469 bus system, i.e. the way the CPU talks to the other stuff inside
470 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
471 VESA. If you have PCI, say Y, otherwise N.
473 The PCI-HOWTO, available from
474 <http://www.tldp.org/docs.html#howto>, contains valuable
475 information about which PCI hardware does work under Linux and which
478 # Select the host bridge type
479 config PCI_HOST_VIA82C505
481 depends on PCI && ARCH_SHARK
484 source "drivers/pci/Kconfig"
486 source "drivers/pcmcia/Kconfig"
490 menu "Kernel Features"
493 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
494 depends on EXPERIMENTAL && REALVIEW_MPCORE
496 This enables support for systems with more than one CPU. If you have
497 a system with only one CPU, like most personal computers, say N. If
498 you have a system with more than one CPU, say Y.
500 If you say N here, the kernel will run on single and multiprocessor
501 machines, but will use only one CPU of a multiprocessor machine. If
502 you say Y here, the kernel will run on many, but not all, single
503 processor machines. On a single processor machine, the kernel will
504 run faster if you say N here.
506 See also the <file:Documentation/smp.txt>,
507 <file:Documentation/i386/IO-APIC.txt>,
508 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
509 <http://www.linuxdoc.org/docs.html#howto>.
511 If you don't know what to do here, say N.
514 int "Maximum number of CPUs (2-32)"
520 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
521 depends on SMP && HOTPLUG && EXPERIMENTAL
523 Say Y here to experiment with turning CPUs off and on. CPUs
524 can be controlled through /sys/devices/system/cpu.
527 bool "Use local timer interrupts"
528 depends on SMP && REALVIEW_MPCORE
531 Enable support for local timers on SMP platforms, rather then the
532 legacy IPI broadcast method. Local timers allows the system
533 accounting to be spread across the timer interval, preventing a
534 "thundering herd" at every timer tick.
537 bool "Preemptible Kernel (EXPERIMENTAL)"
538 depends on EXPERIMENTAL
540 This option reduces the latency of the kernel when reacting to
541 real-time or interactive events by allowing a low priority process to
542 be preempted even if it is in kernel mode executing a system call.
543 This allows applications to run more reliably even when the system is
546 Say Y here if you are building a kernel for a desktop, embedded
547 or real-time system. Say N if you are unsure.
550 bool "Dynamic tick timer"
552 Select this option if you want to disable continuous timer ticks
553 and have them programmed to occur as required. This option saves
554 power as the system can remain in idle state for longer.
556 By default dynamic tick is disabled during the boot, and can be
557 manually enabled with:
559 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
561 Alternatively, if you want dynamic tick automatically enabled
562 during boot, pass "dyntick=enable" via the kernel command string.
564 Please note that dynamic tick may affect the accuracy of
565 timekeeping on some platforms depending on the implementation.
566 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
567 to have accurate timekeeping with dynamic tick.
571 default 128 if ARCH_L7200
572 default 200 if ARCH_EBSA110 || ARCH_S3C2410
573 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
577 bool "Use the ARM EABI to compile the kernel"
579 This option allows for the kernel to be compiled using the latest
580 ARM ABI (aka EABI). This is only useful if you are using a user
581 space environment that is also compiled with EABI.
583 Since there are major incompatibilities between the legacy ABI and
584 EABI, especially with regard to structure member alignment, this
585 option also changes the kernel syscall calling convention to
586 disambiguate both ABIs and allow for backward compatibility support
587 (selected with CONFIG_OABI_COMPAT).
589 To use this you need GCC version 4.0.0 or later.
592 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
593 depends on AEABI && EXPERIMENTAL
596 This option preserves the old syscall interface along with the
597 new (ARM EABI) one. It also provides a compatibility layer to
598 intercept syscalls that have structure arguments which layout
599 in memory differs between the legacy ABI and the new ARM EABI
600 (only for non "thumb" binaries). This option adds a tiny
601 overhead to all syscalls and produces a slightly larger kernel.
602 If you know you'll be using only pure EABI user space then you
603 can say N here. If this option is not selected and you attempt
604 to execute a legacy ABI binary then the result will be
605 UNPREDICTABLE (in fact it can be predicted that it won't work
606 at all). If in doubt say Y.
608 config ARCH_DISCONTIGMEM_ENABLE
610 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
612 Say Y to support efficient handling of discontiguous physical memory,
613 for architectures which are either NUMA (Non-Uniform Memory Access)
614 or have huge holes in the physical address space for other reasons.
615 See <file:Documentation/vm/numa> for more.
619 default "4" if ARCH_LH7A40X
621 depends on NEED_MULTIPLE_NODES
626 bool "Timer and CPU usage LEDs"
627 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
628 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
629 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
630 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
631 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
632 ARCH_AT91 || MACH_TRIZEPS4
634 If you say Y here, the LEDs on your machine will be used
635 to provide useful information about your current system status.
637 If you are compiling a kernel for a NetWinder or EBSA-285, you will
638 be able to select which LEDs are active using the options below. If
639 you are compiling a kernel for the EBSA-110 or the LART however, the
640 red LED will simply flash regularly to indicate that the system is
641 still functional. It is safe to say Y here if you have a CATS
642 system, but the driver will do nothing.
645 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
646 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
648 default y if ARCH_EBSA110
650 If you say Y here, one of the system LEDs (the green one on the
651 NetWinder, the amber one on the EBSA285, or the red one on the LART)
652 will flash regularly to indicate that the system is still
653 operational. This is mainly useful to kernel hackers who are
654 debugging unstable kernels.
656 The LART uses the same LED for both Timer LED and CPU usage LED
657 functions. You may choose to use both, but the Timer LED function
658 will overrule the CPU usage LED.
661 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
662 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
665 If you say Y here, the red LED will be used to give a good real
666 time indication of CPU usage, by lighting whenever the idle task
667 is not currently executing.
669 The LART uses the same LED for both Timer LED and CPU usage LED
670 functions. You may choose to use both, but the Timer LED function
671 will overrule the CPU usage LED.
673 config ALIGNMENT_TRAP
675 depends on CPU_CP15_MMU
676 default y if !ARCH_EBSA110
678 ARM processors cannot fetch/store information which is not
679 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
680 address divisible by 4. On 32-bit ARM processors, these non-aligned
681 fetch/store instructions will be emulated in software if you say
682 here, which has a severe performance impact. This is necessary for
683 correct operation of some network protocols. With an IP-only
684 configuration it is safe to say N, otherwise say Y.
690 # Compressed boot loader in ROM. Yes, we really want to ask about
691 # TEXT and BSS so we preserve their values in the config files.
692 config ZBOOT_ROM_TEXT
693 hex "Compressed ROM boot loader base address"
696 The physical address at which the ROM-able zImage is to be
697 placed in the target. Platforms which normally make use of
698 ROM-able zImage formats normally set this to a suitable
699 value in their defconfig file.
701 If ZBOOT_ROM is not enabled, this has no effect.
704 hex "Compressed ROM boot loader BSS address"
707 The base address of an area of read/write memory in the target
708 for the ROM-able zImage which must be available while the
709 decompressor is running. It must be large enough to hold the
710 entire decompressed kernel plus an additional 128 KiB.
711 Platforms which normally make use of ROM-able zImage formats
712 normally set this to a suitable value in their defconfig file.
714 If ZBOOT_ROM is not enabled, this has no effect.
717 bool "Compressed boot loader in ROM/flash"
718 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
720 Say Y here if you intend to execute your compressed kernel image
721 (zImage) directly from ROM or flash. If unsure, say N.
724 string "Default kernel command string"
727 On some architectures (EBSA110 and CATS), there is currently no way
728 for the boot loader to pass arguments to the kernel. For these
729 architectures, you should supply some command-line options at build
730 time by entering them here. As a minimum, you should specify the
731 memory size and the root device (e.g., mem=64M root=/dev/nfs).
734 bool "Kernel Execute-In-Place from ROM"
735 depends on !ZBOOT_ROM
737 Execute-In-Place allows the kernel to run from non-volatile storage
738 directly addressable by the CPU, such as NOR flash. This saves RAM
739 space since the text section of the kernel is not loaded from flash
740 to RAM. Read-write sections, such as the data section and stack,
741 are still copied to RAM. The XIP kernel is not compressed since
742 it has to run directly from flash, so it will take more space to
743 store it. The flash address used to link the kernel object files,
744 and for storing it, is configuration dependent. Therefore, if you
745 say Y here, you must know the proper physical address where to
746 store the kernel image depending on your own flash memory usage.
748 Also note that the make target becomes "make xipImage" rather than
749 "make zImage" or "make Image". The final kernel binary to put in
750 ROM memory will be arch/arm/boot/xipImage.
755 hex "XIP Kernel Physical Location"
756 depends on XIP_KERNEL
759 This is the physical address in your flash memory the kernel will
760 be linked for and stored to. This address is dependent on your
764 bool "Kexec system call (EXPERIMENTAL)"
765 depends on EXPERIMENTAL
767 kexec is a system call that implements the ability to shutdown your
768 current kernel, and to start another kernel. It is like a reboot
769 but it is indepedent of the system firmware. And like a reboot
770 you can start any kernel with it, not just Linux.
772 It is an ongoing process to be certain the hardware in a machine
773 is properly shutdown, so do not be surprised if this code does not
774 initially work for you. It may help to enable device hotplugging
779 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
781 menu "CPU Frequency scaling"
783 source "drivers/cpufreq/Kconfig"
785 config CPU_FREQ_SA1100
787 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
790 config CPU_FREQ_SA1110
792 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
795 config CPU_FREQ_INTEGRATOR
796 tristate "CPUfreq driver for ARM Integrator CPUs"
797 depends on ARCH_INTEGRATOR && CPU_FREQ
800 This enables the CPUfreq driver for ARM Integrator CPUs.
802 For details, take a look at <file:Documentation/cpu-freq>.
807 tristate "CPUfreq driver for i.MX CPUs"
808 depends on ARCH_IMX && CPU_FREQ
811 This enables the CPUfreq driver for i.MX CPUs.
819 menu "Floating point emulation"
821 comment "At least one emulation must be selected"
824 bool "NWFPE math emulation"
825 depends on !AEABI || OABI_COMPAT
827 Say Y to include the NWFPE floating point emulator in the kernel.
828 This is necessary to run most binaries. Linux does not currently
829 support floating point hardware so you need to say Y here even if
830 your machine has an FPA or floating point co-processor podule.
832 You may say N here if you are going to load the Acorn FPEmulator
836 bool "Support extended precision"
839 Say Y to include 80-bit support in the kernel floating-point
840 emulator. Otherwise, only 32 and 64-bit support is compiled in.
841 Note that gcc does not generate 80-bit operations by default,
842 so in most cases this option only enlarges the size of the
843 floating point emulator without any good reason.
845 You almost surely want to say N here.
848 bool "FastFPE math emulation (EXPERIMENTAL)"
849 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
851 Say Y here to include the FAST floating point emulator in the kernel.
852 This is an experimental much faster emulator which now also has full
853 precision for the mantissa. It does not support any exceptions.
854 It is very simple, and approximately 3-6 times faster than NWFPE.
856 It should be sufficient for most programs. It may be not suitable
857 for scientific calculations, but you have to check this for yourself.
858 If you do not feel you need a faster FP emulation you should better
862 bool "VFP-format floating point maths"
863 depends on CPU_V6 || CPU_ARM926T
865 Say Y to include VFP support code in the kernel. This is needed
866 if your hardware includes a VFP unit.
868 Please see <file:Documentation/arm/VFP/release-notes.txt> for
869 release notes and additional status information.
871 Say N if your target does not have VFP hardware.
875 menu "Userspace binary formats"
877 source "fs/Kconfig.binfmt"
880 tristate "RISC OS personality"
883 Say Y here to include the kernel code necessary if you want to run
884 Acorn RISC OS/Arthur binaries under Linux. This code is still very
885 experimental; if this sounds frightening, say N and sleep in peace.
886 You can also say M here to compile this support as a module (which
887 will be called arthur).
891 menu "Power management options"
893 source "kernel/power/Kconfig"
896 tristate "Advanced Power Management Emulation"
898 APM is a BIOS specification for saving power using several different
899 techniques. This is mostly useful for battery powered laptops with
900 APM compliant BIOSes. If you say Y here, the system time will be
901 reset after a RESUME operation, the /proc/apm device will provide
902 battery status information, and user-space programs will receive
903 notification of APM "events" (e.g. battery status change).
905 In order to use APM, you will need supporting software. For location
906 and more information, read <file:Documentation/pm.txt> and the
907 Battery Powered Linux mini-HOWTO, available from
908 <http://www.tldp.org/docs.html#howto>.
910 This driver does not spin down disk drives (see the hdparm(8)
911 manpage ("man 8 hdparm") for that), and it doesn't turn off
912 VESA-compliant "green" monitors.
914 Generally, if you don't have a battery in your machine, there isn't
915 much point in using this driver and you should say N. If you get
916 random kernel OOPSes or reboots that don't seem to be related to
917 anything, try disabling/enabling this option (or disabling/enabling
924 menu "Device Drivers"
926 source "drivers/base/Kconfig"
928 source "drivers/connector/Kconfig"
930 if ALIGNMENT_TRAP || !CPU_CP15_MMU
931 source "drivers/mtd/Kconfig"
934 source "drivers/parport/Kconfig"
936 source "drivers/pnp/Kconfig"
938 source "drivers/block/Kconfig"
940 source "drivers/acorn/block/Kconfig"
942 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
943 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
944 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
946 source "drivers/ide/Kconfig"
949 source "drivers/scsi/Kconfig"
951 source "drivers/ata/Kconfig"
953 source "drivers/md/Kconfig"
955 source "drivers/message/fusion/Kconfig"
957 source "drivers/ieee1394/Kconfig"
959 source "drivers/message/i2o/Kconfig"
961 source "drivers/net/Kconfig"
963 source "drivers/isdn/Kconfig"
965 # input before char - char/joystick depends on it. As does USB.
967 source "drivers/input/Kconfig"
969 source "drivers/char/Kconfig"
971 source "drivers/i2c/Kconfig"
973 source "drivers/spi/Kconfig"
975 source "drivers/w1/Kconfig"
977 source "drivers/hwmon/Kconfig"
979 #source "drivers/l3/Kconfig"
981 source "drivers/misc/Kconfig"
983 source "drivers/mfd/Kconfig"
985 source "drivers/leds/Kconfig"
987 source "drivers/media/Kconfig"
989 source "drivers/video/Kconfig"
991 source "sound/Kconfig"
993 source "drivers/hid/Kconfig"
995 source "drivers/usb/Kconfig"
997 source "drivers/mmc/Kconfig"
999 source "drivers/rtc/Kconfig"
1005 source "arch/arm/oprofile/Kconfig"
1007 source "arch/arm/Kconfig.debug"
1009 source "security/Kconfig"
1011 source "crypto/Kconfig"
1013 source "lib/Kconfig"