1# 2# For a description of the syntax of this configuration file, 3# see Documentation/kbuild/kconfig-language.txt. 4# 5 6mainmenu "Linux Kernel Configuration" 7 8config ARM 9 bool 10 default y 11 help 12 The ARM series is a line of low-power-consumption RISC chip designs 13 licensed by ARM ltd and targeted at embedded applications and 14 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer 15 manufactured, but legacy ARM-based PC hardware remains popular in 16 Europe. There is an ARM Linux project with a web page at 17 <http://www.arm.linux.org.uk/>. 18 19config MMU 20 bool 21 default y 22 23config EISA 24 bool 25 ---help--- 26 The Extended Industry Standard Architecture (EISA) bus was 27 developed as an open alternative to the IBM MicroChannel bus. 28 29 The EISA bus provided some of the features of the IBM MicroChannel 30 bus while maintaining backward compatibility with cards made for 31 the older ISA bus. The EISA bus saw limited use between 1988 and 32 1995 when it was made obsolete by the PCI bus. 33 34 Say Y here if you are building a kernel for an EISA-based machine. 35 36 Otherwise, say N. 37 38config SBUS 39 bool 40 41config MCA 42 bool 43 help 44 MicroChannel Architecture is found in some IBM PS/2 machines and 45 laptops. It is a bus system similar to PCI or ISA. See 46 <file:Documentation/mca.txt> (and especially the web page given 47 there) before attempting to build an MCA bus kernel. 48 49config UID16 50 bool 51 default y 52 53config RWSEM_GENERIC_SPINLOCK 54 bool 55 default y 56 57config RWSEM_XCHGADD_ALGORITHM 58 bool 59 60config GENERIC_CALIBRATE_DELAY 61 bool 62 default y 63 64config GENERIC_BUST_SPINLOCK 65 bool 66 67config GENERIC_ISA_DMA 68 bool 69 70config FIQ 71 bool 72 73source "init/Kconfig" 74 75menu "System Type" 76 77choice 78 prompt "ARM system type" 79 default ARCH_RPC 80 81config ARCH_CLPS7500 82 bool "Cirrus-CL-PS7500FE" 83 select TIMER_ACORN 84 select ISA 85 86config ARCH_CLPS711X 87 bool "CLPS711x/EP721x-based" 88 89config ARCH_CO285 90 bool "Co-EBSA285" 91 select FOOTBRIDGE 92 select FOOTBRIDGE_ADDIN 93 94config ARCH_EBSA110 95 bool "EBSA-110" 96 select ISA 97 help 98 This is an evaluation board for the StrongARM processor available 99 from Digital. It has limited hardware on-board, including an onboard 100 Ethernet interface, two PCMCIA sockets, two serial ports and a 101 parallel port. 102 103config ARCH_CAMELOT 104 bool "Epxa10db" 105 help 106 This enables support for Altera's Excalibur XA10 development board. 107 If you would like to build your kernel to run on one of these boards 108 then you must say 'Y' here. Otherwise say 'N' 109 110config ARCH_FOOTBRIDGE 111 bool "FootBridge" 112 select FOOTBRIDGE 113 114config ARCH_INTEGRATOR 115 bool "Integrator" 116 select ARM_AMBA 117 select ICST525 118 119config ARCH_IOP3XX 120 bool "IOP3xx-based" 121 select PCI 122 123config ARCH_IXP4XX 124 bool "IXP4xx-based" 125 select DMABOUNCE 126 select PCI 127 128config ARCH_IXP2000 129 bool "IXP2400/2800-based" 130 select PCI 131 132config ARCH_L7200 133 bool "LinkUp-L7200" 134 select FIQ 135 help 136 Say Y here if you intend to run this kernel on a LinkUp Systems 137 L7200 Software Development Board which uses an ARM720T processor. 138 Information on this board can be obtained at: 139 140 <http://www.linkupsys.com/> 141 142 If you have any questions or comments about the Linux kernel port 143 to this board, send e-mail to <sjhill@cotw.com>. 144 145config ARCH_PXA 146 bool "PXA2xx-based" 147 148config ARCH_RPC 149 bool "RiscPC" 150 select ARCH_ACORN 151 select FIQ 152 select TIMER_ACORN 153 help 154 On the Acorn Risc-PC, Linux can support the internal IDE disk and 155 CD-ROM interface, serial and parallel port, and the floppy drive. 156 157config ARCH_SA1100 158 bool "SA1100-based" 159 select ISA 160 select ARCH_DISCONTIGMEM_ENABLE 161 162config ARCH_S3C2410 163 bool "Samsung S3C2410" 164 help 165 Samsung S3C2410X CPU based systems, such as the Simtec Electronics 166 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or 167 the Samsung SMDK2410 development board (and derviatives). 168 169config ARCH_SHARK 170 bool "Shark" 171 select ISA 172 select ISA_DMA 173 select PCI 174 175config ARCH_LH7A40X 176 bool "Sharp LH7A40X" 177 help 178 Say Y here for systems based on one of the Sharp LH7A40X 179 System on a Chip processors. These CPUs include an ARM922T 180 core with a wide array of integrated devices for 181 hand-held and low-power applications. 182 183config ARCH_OMAP 184 bool "TI OMAP" 185 186config ARCH_VERSATILE 187 bool "Versatile" 188 select ARM_AMBA 189 select ICST307 190 help 191 This enables support for ARM Ltd Versatile board. 192 193config ARCH_IMX 194 bool "IMX" 195 196config ARCH_H720X 197 bool "Hynix-HMS720x-based" 198 help 199 This enables support for systems based on the Hynix HMS720x 200 201config ARCH_AAEC2000 202 bool "Agilent AAEC-2000 based" 203 help 204 This enables support for systems based on the Agilent AAEC-2000 205 206endchoice 207 208source "arch/arm/mach-clps711x/Kconfig" 209 210source "arch/arm/mach-epxa10db/Kconfig" 211 212source "arch/arm/mach-footbridge/Kconfig" 213 214source "arch/arm/mach-integrator/Kconfig" 215 216source "arch/arm/mach-iop3xx/Kconfig" 217 218source "arch/arm/mach-ixp4xx/Kconfig" 219 220source "arch/arm/mach-ixp2000/Kconfig" 221 222source "arch/arm/mach-pxa/Kconfig" 223 224source "arch/arm/mach-sa1100/Kconfig" 225 226source "arch/arm/plat-omap/Kconfig" 227 228source "arch/arm/mach-omap1/Kconfig" 229 230source "arch/arm/mach-s3c2410/Kconfig" 231 232source "arch/arm/mach-lh7a40x/Kconfig" 233 234source "arch/arm/mach-imx/Kconfig" 235 236source "arch/arm/mach-h720x/Kconfig" 237 238source "arch/arm/mach-versatile/Kconfig" 239 240source "arch/arm/mach-aaec2000/Kconfig" 241 242# Definitions to make life easier 243config ARCH_ACORN 244 bool 245 246source arch/arm/mm/Kconfig 247 248# bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER 249config XSCALE_PMU 250 bool 251 depends on CPU_XSCALE && !XSCALE_PMU_TIMER 252 default y 253 254endmenu 255 256source "arch/arm/common/Kconfig" 257 258config FORCE_MAX_ZONEORDER 259 int 260 depends on SA1111 261 default "9" 262 263menu "Bus support" 264 265config ARM_AMBA 266 bool 267 268config ISA 269 bool 270 help 271 Find out whether you have ISA slots on your motherboard. ISA is the 272 name of a bus system, i.e. the way the CPU talks to the other stuff 273 inside your box. Other bus systems are PCI, EISA, MicroChannel 274 (MCA) or VESA. ISA is an older system, now being displaced by PCI; 275 newer boards don't support it. If you have ISA, say Y, otherwise N. 276 277config ISA_DMA 278 bool 279 280config ISA_DMA_API 281 bool 282 default y 283 284config PCI 285 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB 286 help 287 Find out whether you have a PCI motherboard. PCI is the name of a 288 bus system, i.e. the way the CPU talks to the other stuff inside 289 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or 290 VESA. If you have PCI, say Y, otherwise N. 291 292 The PCI-HOWTO, available from 293 <http://www.tldp.org/docs.html#howto>, contains valuable 294 information about which PCI hardware does work under Linux and which 295 doesn't. 296 297# Select the host bridge type 298config PCI_HOST_VIA82C505 299 bool 300 depends on PCI && ARCH_SHARK 301 default y 302 303source "drivers/pci/Kconfig" 304 305source "drivers/pcmcia/Kconfig" 306 307endmenu 308 309menu "Kernel Features" 310 311config SMP 312 bool "Symmetric Multi-Processing (EXPERIMENTAL)" 313 depends on EXPERIMENTAL #&& n 314 help 315 This enables support for systems with more than one CPU. If you have 316 a system with only one CPU, like most personal computers, say N. If 317 you have a system with more than one CPU, say Y. 318 319 If you say N here, the kernel will run on single and multiprocessor 320 machines, but will use only one CPU of a multiprocessor machine. If 321 you say Y here, the kernel will run on many, but not all, single 322 processor machines. On a single processor machine, the kernel will 323 run faster if you say N here. 324 325 See also the <file:Documentation/smp.tex>, 326 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>, 327 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at 328 <http://www.linuxdoc.org/docs.html#howto>. 329 330 If you don't know what to do here, say N. 331 332config NR_CPUS 333 int "Maximum number of CPUs (2-32)" 334 range 2 32 335 depends on SMP 336 default "4" 337 338config PREEMPT 339 bool "Preemptible Kernel (EXPERIMENTAL)" 340 depends on EXPERIMENTAL 341 help 342 This option reduces the latency of the kernel when reacting to 343 real-time or interactive events by allowing a low priority process to 344 be preempted even if it is in kernel mode executing a system call. 345 This allows applications to run more reliably even when the system is 346 under load. 347 348 Say Y here if you are building a kernel for a desktop, embedded 349 or real-time system. Say N if you are unsure. 350 351config NO_IDLE_HZ 352 bool "Dynamic tick timer" 353 help 354 Select this option if you want to disable continuous timer ticks 355 and have them programmed to occur as required. This option saves 356 power as the system can remain in idle state for longer. 357 358 By default dynamic tick is disabled during the boot, and can be 359 manually enabled with: 360 361 echo 1 > /sys/devices/system/timer/timer0/dyn_tick 362 363 Alternatively, if you want dynamic tick automatically enabled 364 during boot, pass "dyntick=enable" via the kernel command string. 365 366 Please note that dynamic tick may affect the accuracy of 367 timekeeping on some platforms depending on the implementation. 368 Currently at least OMAP platform is known to have accurate 369 timekeeping with dynamic tick. 370 371config ARCH_DISCONTIGMEM_ENABLE 372 bool 373 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM) 374 help 375 Say Y to support efficient handling of discontiguous physical memory, 376 for architectures which are either NUMA (Non-Uniform Memory Access) 377 or have huge holes in the physical address space for other reasons. 378 See <file:Documentation/vm/numa> for more. 379 380source "mm/Kconfig" 381 382config LEDS 383 bool "Timer and CPU usage LEDs" 384 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \ 385 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \ 386 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \ 387 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \ 388 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE 389 help 390 If you say Y here, the LEDs on your machine will be used 391 to provide useful information about your current system status. 392 393 If you are compiling a kernel for a NetWinder or EBSA-285, you will 394 be able to select which LEDs are active using the options below. If 395 you are compiling a kernel for the EBSA-110 or the LART however, the 396 red LED will simply flash regularly to indicate that the system is 397 still functional. It is safe to say Y here if you have a CATS 398 system, but the driver will do nothing. 399 400config LEDS_TIMER 401 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \ 402 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2 403 depends on LEDS 404 default y if ARCH_EBSA110 405 help 406 If you say Y here, one of the system LEDs (the green one on the 407 NetWinder, the amber one on the EBSA285, or the red one on the LART) 408 will flash regularly to indicate that the system is still 409 operational. This is mainly useful to kernel hackers who are 410 debugging unstable kernels. 411 412 The LART uses the same LED for both Timer LED and CPU usage LED 413 functions. You may choose to use both, but the Timer LED function 414 will overrule the CPU usage LED. 415 416config LEDS_CPU 417 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \ 418 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2 419 depends on LEDS 420 help 421 If you say Y here, the red LED will be used to give a good real 422 time indication of CPU usage, by lighting whenever the idle task 423 is not currently executing. 424 425 The LART uses the same LED for both Timer LED and CPU usage LED 426 functions. You may choose to use both, but the Timer LED function 427 will overrule the CPU usage LED. 428 429config ALIGNMENT_TRAP 430 bool 431 default y if !ARCH_EBSA110 432 help 433 ARM processors can not fetch/store information which is not 434 naturally aligned on the bus, i.e., a 4 byte fetch must start at an 435 address divisible by 4. On 32-bit ARM processors, these non-aligned 436 fetch/store instructions will be emulated in software if you say 437 here, which has a severe performance impact. This is necessary for 438 correct operation of some network protocols. With an IP-only 439 configuration it is safe to say N, otherwise say Y. 440 441endmenu 442 443menu "Boot options" 444 445# Compressed boot loader in ROM. Yes, we really want to ask about 446# TEXT and BSS so we preserve their values in the config files. 447config ZBOOT_ROM_TEXT 448 hex "Compressed ROM boot loader base address" 449 default "0" 450 help 451 The physical address at which the ROM-able zImage is to be 452 placed in the target. Platforms which normally make use of 453 ROM-able zImage formats normally set this to a suitable 454 value in their defconfig file. 455 456 If ZBOOT_ROM is not enabled, this has no effect. 457 458config ZBOOT_ROM_BSS 459 hex "Compressed ROM boot loader BSS address" 460 default "0" 461 help 462 The base address of 64KiB of read/write memory in the target 463 for the ROM-able zImage, which must be available while the 464 decompressor is running. Platforms which normally make use of 465 ROM-able zImage formats normally set this to a suitable 466 value in their defconfig file. 467 468 If ZBOOT_ROM is not enabled, this has no effect. 469 470config ZBOOT_ROM 471 bool "Compressed boot loader in ROM/flash" 472 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS 473 help 474 Say Y here if you intend to execute your compressed kernel image 475 (zImage) directly from ROM or flash. If unsure, say N. 476 477config CMDLINE 478 string "Default kernel command string" 479 default "" 480 help 481 On some architectures (EBSA110 and CATS), there is currently no way 482 for the boot loader to pass arguments to the kernel. For these 483 architectures, you should supply some command-line options at build 484 time by entering them here. As a minimum, you should specify the 485 memory size and the root device (e.g., mem=64M root=/dev/nfs). 486 487config XIP_KERNEL 488 bool "Kernel Execute-In-Place from ROM" 489 depends on !ZBOOT_ROM 490 help 491 Execute-In-Place allows the kernel to run from non-volatile storage 492 directly addressable by the CPU, such as NOR flash. This saves RAM 493 space since the text section of the kernel is not loaded from flash 494 to RAM. Read-write sections, such as the data section and stack, 495 are still copied to RAM. The XIP kernel is not compressed since 496 it has to run directly from flash, so it will take more space to 497 store it. The flash address used to link the kernel object files, 498 and for storing it, is configuration dependent. Therefore, if you 499 say Y here, you must know the proper physical address where to 500 store the kernel image depending on your own flash memory usage. 501 502 Also note that the make target becomes "make xipImage" rather than 503 "make zImage" or "make Image". The final kernel binary to put in 504 ROM memory will be arch/arm/boot/xipImage. 505 506 If unsure, say N. 507 508config XIP_PHYS_ADDR 509 hex "XIP Kernel Physical Location" 510 depends on XIP_KERNEL 511 default "0x00080000" 512 help 513 This is the physical address in your flash memory the kernel will 514 be linked for and stored to. This address is dependent on your 515 own flash usage. 516 517endmenu 518 519if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1) 520 521menu "CPU Frequency scaling" 522 523source "drivers/cpufreq/Kconfig" 524 525config CPU_FREQ_SA1100 526 bool 527 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT) 528 default y 529 530config CPU_FREQ_SA1110 531 bool 532 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3) 533 default y 534 535config CPU_FREQ_INTEGRATOR 536 tristate "CPUfreq driver for ARM Integrator CPUs" 537 depends on ARCH_INTEGRATOR && CPU_FREQ 538 default y 539 help 540 This enables the CPUfreq driver for ARM Integrator CPUs. 541 542 For details, take a look at <file:Documentation/cpu-freq>. 543 544 If in doubt, say Y. 545 546endmenu 547 548endif 549 550menu "Floating point emulation" 551 552comment "At least one emulation must be selected" 553 554config FPE_NWFPE 555 bool "NWFPE math emulation" 556 ---help--- 557 Say Y to include the NWFPE floating point emulator in the kernel. 558 This is necessary to run most binaries. Linux does not currently 559 support floating point hardware so you need to say Y here even if 560 your machine has an FPA or floating point co-processor podule. 561 562 You may say N here if you are going to load the Acorn FPEmulator 563 early in the bootup. 564 565config FPE_NWFPE_XP 566 bool "Support extended precision" 567 depends on FPE_NWFPE && !CPU_BIG_ENDIAN 568 help 569 Say Y to include 80-bit support in the kernel floating-point 570 emulator. Otherwise, only 32 and 64-bit support is compiled in. 571 Note that gcc does not generate 80-bit operations by default, 572 so in most cases this option only enlarges the size of the 573 floating point emulator without any good reason. 574 575 You almost surely want to say N here. 576 577config FPE_FASTFPE 578 bool "FastFPE math emulation (EXPERIMENTAL)" 579 depends on !CPU_32v3 && EXPERIMENTAL 580 ---help--- 581 Say Y here to include the FAST floating point emulator in the kernel. 582 This is an experimental much faster emulator which now also has full 583 precision for the mantissa. It does not support any exceptions. 584 It is very simple, and approximately 3-6 times faster than NWFPE. 585 586 It should be sufficient for most programs. It may be not suitable 587 for scientific calculations, but you have to check this for yourself. 588 If you do not feel you need a faster FP emulation you should better 589 choose NWFPE. 590 591config VFP 592 bool "VFP-format floating point maths" 593 depends on CPU_V6 || CPU_ARM926T 594 help 595 Say Y to include VFP support code in the kernel. This is needed 596 if your hardware includes a VFP unit. 597 598 Please see <file:Documentation/arm/VFP/release-notes.txt> for 599 release notes and additional status information. 600 601 Say N if your target does not have VFP hardware. 602 603endmenu 604 605menu "Userspace binary formats" 606 607source "fs/Kconfig.binfmt" 608 609config ARTHUR 610 tristate "RISC OS personality" 611 help 612 Say Y here to include the kernel code necessary if you want to run 613 Acorn RISC OS/Arthur binaries under Linux. This code is still very 614 experimental; if this sounds frightening, say N and sleep in peace. 615 You can also say M here to compile this support as a module (which 616 will be called arthur). 617 618endmenu 619 620menu "Power management options" 621 622config PM 623 bool "Power Management support" 624 ---help--- 625 "Power Management" means that parts of your computer are shut 626 off or put into a power conserving "sleep" mode if they are not 627 being used. There are two competing standards for doing this: APM 628 and ACPI. If you want to use either one, say Y here and then also 629 to the requisite support below. 630 631 Power Management is most important for battery powered laptop 632 computers; if you have a laptop, check out the Linux Laptop home 633 page on the WWW at <http://www.linux-on-laptops.com/> or 634 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/> 635 and the Battery Powered Linux mini-HOWTO, available from 636 <http://www.tldp.org/docs.html#howto>. 637 638 Note that, even if you say N here, Linux on the x86 architecture 639 will issue the hlt instruction if nothing is to be done, thereby 640 sending the processor to sleep and saving power. 641 642config APM 643 tristate "Advanced Power Management Emulation" 644 depends on PM 645 ---help--- 646 APM is a BIOS specification for saving power using several different 647 techniques. This is mostly useful for battery powered laptops with 648 APM compliant BIOSes. If you say Y here, the system time will be 649 reset after a RESUME operation, the /proc/apm device will provide 650 battery status information, and user-space programs will receive 651 notification of APM "events" (e.g. battery status change). 652 653 If you select "Y" here, you can disable actual use of the APM 654 BIOS by passing the "apm=off" option to the kernel at boot time. 655 656 Note that the APM support is almost completely disabled for 657 machines with more than one CPU. 658 659 In order to use APM, you will need supporting software. For location 660 and more information, read <file:Documentation/pm.txt> and the 661 Battery Powered Linux mini-HOWTO, available from 662 <http://www.tldp.org/docs.html#howto>. 663 664 This driver does not spin down disk drives (see the hdparm(8) 665 manpage ("man 8 hdparm") for that), and it doesn't turn off 666 VESA-compliant "green" monitors. 667 668 This driver does not support the TI 4000M TravelMate and the ACER 669 486/DX4/75 because they don't have compliant BIOSes. Many "green" 670 desktop machines also don't have compliant BIOSes, and this driver 671 may cause those machines to panic during the boot phase. 672 673 Generally, if you don't have a battery in your machine, there isn't 674 much point in using this driver and you should say N. If you get 675 random kernel OOPSes or reboots that don't seem to be related to 676 anything, try disabling/enabling this option (or disabling/enabling 677 APM in your BIOS). 678 679 Some other things you should try when experiencing seemingly random, 680 "weird" problems: 681 682 1) make sure that you have enough swap space and that it is 683 enabled. 684 2) pass the "no-hlt" option to the kernel 685 3) switch on floating point emulation in the kernel and pass 686 the "no387" option to the kernel 687 4) pass the "floppy=nodma" option to the kernel 688 5) pass the "mem=4M" option to the kernel (thereby disabling 689 all but the first 4 MB of RAM) 690 6) make sure that the CPU is not over clocked. 691 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/> 692 8) disable the cache from your BIOS settings 693 9) install a fan for the video card or exchange video RAM 694 10) install a better fan for the CPU 695 11) exchange RAM chips 696 12) exchange the motherboard. 697 698 To compile this driver as a module, choose M here: the 699 module will be called apm. 700 701endmenu 702 703source "net/Kconfig" 704 705menu "Device Drivers" 706 707source "drivers/base/Kconfig" 708 709if ALIGNMENT_TRAP 710source "drivers/mtd/Kconfig" 711endif 712 713source "drivers/parport/Kconfig" 714 715source "drivers/pnp/Kconfig" 716 717source "drivers/block/Kconfig" 718 719source "drivers/acorn/block/Kconfig" 720 721if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \ 722 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \ 723 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE 724source "drivers/ide/Kconfig" 725endif 726 727source "drivers/scsi/Kconfig" 728 729source "drivers/md/Kconfig" 730 731source "drivers/message/fusion/Kconfig" 732 733source "drivers/ieee1394/Kconfig" 734 735source "drivers/message/i2o/Kconfig" 736 737source "drivers/net/Kconfig" 738 739source "drivers/isdn/Kconfig" 740 741# input before char - char/joystick depends on it. As does USB. 742 743source "drivers/input/Kconfig" 744 745source "drivers/char/Kconfig" 746 747source "drivers/i2c/Kconfig" 748 749source "drivers/hwmon/Kconfig" 750 751#source "drivers/l3/Kconfig" 752 753source "drivers/misc/Kconfig" 754 755source "drivers/media/Kconfig" 756 757source "drivers/video/Kconfig" 758 759source "sound/Kconfig" 760 761source "drivers/usb/Kconfig" 762 763source "drivers/mmc/Kconfig" 764 765endmenu 766 767source "fs/Kconfig" 768 769source "arch/arm/oprofile/Kconfig" 770 771source "arch/arm/Kconfig.debug" 772 773source "security/Kconfig" 774 775source "crypto/Kconfig" 776 777source "lib/Kconfig" 778