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