2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 This is Linux's home port. Linux was originally native to the Intel
13 386, and runs on all the later x86 processors including the Intel
14 486, 586, Pentiums, and various instruction-set-compatible chips by
15 AMD, Cyrix, and others.
21 config LOCKDEP_SUPPORT
25 config STACKTRACE_SUPPORT
29 config SEMAPHORE_SLEEPERS
44 config GENERIC_ISA_DMA
52 config GENERIC_HWEIGHT
56 config ARCH_MAY_HAVE_PC_FDC
66 menu "Processor type and features"
69 bool "Symmetric multi-processing support"
71 This enables support for systems with more than one CPU. If you have
72 a system with only one CPU, like most personal computers, say N. If
73 you have a system with more than one CPU, say Y.
75 If you say N here, the kernel will run on single and multiprocessor
76 machines, but will use only one CPU of a multiprocessor machine. If
77 you say Y here, the kernel will run on many, but not all,
78 singleprocessor machines. On a singleprocessor machine, the kernel
79 will run faster if you say N here.
81 Note that if you say Y here and choose architecture "586" or
82 "Pentium" under "Processor family", the kernel will not work on 486
83 architectures. Similarly, multiprocessor kernels for the "PPro"
84 architecture may not work on all Pentium based boards.
86 People using multiprocessor machines who say Y here should also say
87 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
88 Management" code will be disabled if you say Y here.
90 See also the <file:Documentation/smp.txt>,
91 <file:Documentation/i386/IO-APIC.txt>,
92 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
93 <http://www.tldp.org/docs.html#howto>.
95 If you don't know what to do here, say N.
98 prompt "Subarchitecture Type"
104 Choose this option if your computer is a standard PC or compatible.
109 Select this for an AMD Elan processor.
111 Do not use this option for K6/Athlon/Opteron processors!
113 If unsure, choose "PC-compatible" instead.
118 Voyager is an MCA-based 32-way capable SMP architecture proprietary
119 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
123 If you do not specifically know you have a Voyager based machine,
124 say N here, otherwise the kernel you build will not be bootable.
127 bool "NUMAQ (IBM/Sequent)"
131 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
132 multiquad box. This changes the way that processors are bootstrapped,
133 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
134 You will need a new lynxer.elf file to flash your firmware with - send
135 email to <Martin.Bligh@us.ibm.com>.
138 bool "Summit/EXA (IBM x440)"
141 This option is needed for IBM systems that use the Summit/EXA chipset.
142 In particular, it is needed for the x440.
144 If you don't have one of these computers, you should say N here.
145 If you want to build a NUMA kernel, you must select ACPI.
148 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
151 This option is needed for the systems that have more than 8 CPUs
152 and if the system is not of any sub-arch type above.
154 If you don't have such a system, you should say N here.
157 bool "SGI 320/540 (Visual Workstation)"
159 The SGI Visual Workstation series is an IA32-based workstation
160 based on SGI systems chips with some legacy PC hardware attached.
162 Say Y here to create a kernel to run on the SGI 320 or 540.
164 A kernel compiled for the Visual Workstation will not run on PCs
165 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
167 config X86_GENERICARCH
168 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
171 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
172 It is intended for a generic binary kernel.
173 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
176 bool "Support for Unisys ES7000 IA32 series"
179 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
180 supposed to run on an IA32-based Unisys ES7000 system.
181 Only choose this option if you have such a system, otherwise you
189 depends on ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
192 config HAVE_ARCH_PARSE_SRAT
197 config X86_SUMMIT_NUMA
200 depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
202 config X86_CYCLONE_TIMER
205 depends on X86_SUMMIT || X86_GENERICARCH
207 config ES7000_CLUSTERED_APIC
210 depends on SMP && X86_ES7000 && MPENTIUMIII
212 source "arch/i386/Kconfig.cpu"
215 bool "HPET Timer Support"
217 This enables the use of the HPET for the kernel's internal timer.
218 HPET is the next generation timer replacing legacy 8254s.
219 You can safely choose Y here. However, HPET will only be
220 activated if the platform and the BIOS support this feature.
221 Otherwise the 8254 will be used for timing services.
223 Choose N to continue using the legacy 8254 timer.
225 config HPET_EMULATE_RTC
227 depends on HPET_TIMER && RTC=y
231 int "Maximum number of CPUs (2-255)"
234 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
237 This allows you to specify the maximum number of CPUs which this
238 kernel will support. The maximum supported value is 255 and the
239 minimum value which makes sense is 2.
241 This is purely to save memory - each supported CPU adds
242 approximately eight kilobytes to the kernel image.
245 bool "SMT (Hyperthreading) scheduler support"
248 SMT scheduler support improves the CPU scheduler's decision making
249 when dealing with Intel Pentium 4 chips with HyperThreading at a
250 cost of slightly increased overhead in some places. If unsure say
254 bool "Multi-core scheduler support"
258 Multi-core scheduler support improves the CPU scheduler's decision
259 making when dealing with multi-core CPU chips at a cost of slightly
260 increased overhead in some places. If unsure say N here.
262 source "kernel/Kconfig.preempt"
265 bool "Local APIC support on uniprocessors"
266 depends on !SMP && !(X86_VISWS || X86_VOYAGER)
268 A local APIC (Advanced Programmable Interrupt Controller) is an
269 integrated interrupt controller in the CPU. If you have a single-CPU
270 system which has a processor with a local APIC, you can say Y here to
271 enable and use it. If you say Y here even though your machine doesn't
272 have a local APIC, then the kernel will still run with no slowdown at
273 all. The local APIC supports CPU-generated self-interrupts (timer,
274 performance counters), and the NMI watchdog which detects hard
278 bool "IO-APIC support on uniprocessors"
279 depends on X86_UP_APIC
281 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
282 SMP-capable replacement for PC-style interrupt controllers. Most
283 SMP systems and many recent uniprocessor systems have one.
285 If you have a single-CPU system with an IO-APIC, you can say Y here
286 to use it. If you say Y here even though your machine doesn't have
287 an IO-APIC, then the kernel will still run with no slowdown at all.
289 config X86_LOCAL_APIC
291 depends on X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER)
296 depends on X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER))
299 config X86_VISWS_APIC
305 bool "Machine Check Exception"
306 depends on !X86_VOYAGER
308 Machine Check Exception support allows the processor to notify the
309 kernel if it detects a problem (e.g. overheating, component failure).
310 The action the kernel takes depends on the severity of the problem,
311 ranging from a warning message on the console, to halting the machine.
312 Your processor must be a Pentium or newer to support this - check the
313 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
314 have a design flaw which leads to false MCE events - hence MCE is
315 disabled on all P5 processors, unless explicitly enabled with "mce"
316 as a boot argument. Similarly, if MCE is built in and creates a
317 problem on some new non-standard machine, you can boot with "nomce"
318 to disable it. MCE support simply ignores non-MCE processors like
319 the 386 and 486, so nearly everyone can say Y here.
321 config X86_MCE_NONFATAL
322 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
325 Enabling this feature starts a timer that triggers every 5 seconds which
326 will look at the machine check registers to see if anything happened.
327 Non-fatal problems automatically get corrected (but still logged).
328 Disable this if you don't want to see these messages.
329 Seeing the messages this option prints out may be indicative of dying hardware,
330 or out-of-spec (ie, overclocked) hardware.
331 This option only does something on certain CPUs.
332 (AMD Athlon/Duron and Intel Pentium 4)
334 config X86_MCE_P4THERMAL
335 bool "check for P4 thermal throttling interrupt."
336 depends on X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
338 Enabling this feature will cause a message to be printed when the P4
339 enters thermal throttling.
343 bool "Enable VM86 support" if EMBEDDED
345 This option is required by programs like DOSEMU to run 16-bit legacy
346 code on X86 processors. It also may be needed by software like
347 XFree86 to initialize some video cards via BIOS. Disabling this
348 option saves about 6k.
351 tristate "Toshiba Laptop support"
353 This adds a driver to safely access the System Management Mode of
354 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
355 not work on models with a Phoenix BIOS. The System Management Mode
356 is used to set the BIOS and power saving options on Toshiba portables.
358 For information on utilities to make use of this driver see the
359 Toshiba Linux utilities web site at:
360 <http://www.buzzard.org.uk/toshiba/>.
362 Say Y if you intend to run this kernel on a Toshiba portable.
366 tristate "Dell laptop support"
368 This adds a driver to safely access the System Management Mode
369 of the CPU on the Dell Inspiron 8000. The System Management Mode
370 is used to read cpu temperature and cooling fan status and to
371 control the fans on the I8K portables.
373 This driver has been tested only on the Inspiron 8000 but it may
374 also work with other Dell laptops. You can force loading on other
375 models by passing the parameter `force=1' to the module. Use at
378 For information on utilities to make use of this driver see the
379 I8K Linux utilities web site at:
380 <http://people.debian.org/~dz/i8k/>
382 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
385 config X86_REBOOTFIXUPS
386 bool "Enable X86 board specific fixups for reboot"
390 This enables chipset and/or board specific fixups to be done
391 in order to get reboot to work correctly. This is only needed on
392 some combinations of hardware and BIOS. The symptom, for which
393 this config is intended, is when reboot ends with a stalled/hung
396 Currently, the only fixup is for the Geode GX1/CS5530A/TROM2.1.
399 Say Y if you want to enable the fixup. Currently, it's safe to
400 enable this option even if you don't need it.
404 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
406 If you say Y here and also to "/dev file system support" in the
407 'File systems' section, you will be able to update the microcode on
408 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
409 Pentium III, Pentium 4, Xeon etc. You will obviously need the
410 actual microcode binary data itself which is not shipped with the
413 For latest news and information on obtaining all the required
414 ingredients for this driver, check:
415 <http://www.urbanmyth.org/microcode/>.
417 To compile this driver as a module, choose M here: the
418 module will be called microcode.
421 tristate "/dev/cpu/*/msr - Model-specific register support"
423 This device gives privileged processes access to the x86
424 Model-Specific Registers (MSRs). It is a character device with
425 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
426 MSR accesses are directed to a specific CPU on multi-processor
430 tristate "/dev/cpu/*/cpuid - CPU information support"
432 This device gives processes access to the x86 CPUID instruction to
433 be executed on a specific processor. It is a character device
434 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
437 source "drivers/firmware/Kconfig"
440 prompt "High Memory Support"
445 depends on !X86_NUMAQ
447 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
448 However, the address space of 32-bit x86 processors is only 4
449 Gigabytes large. That means that, if you have a large amount of
450 physical memory, not all of it can be "permanently mapped" by the
451 kernel. The physical memory that's not permanently mapped is called
454 If you are compiling a kernel which will never run on a machine with
455 more than 1 Gigabyte total physical RAM, answer "off" here (default
456 choice and suitable for most users). This will result in a "3GB/1GB"
457 split: 3GB are mapped so that each process sees a 3GB virtual memory
458 space and the remaining part of the 4GB virtual memory space is used
459 by the kernel to permanently map as much physical memory as
462 If the machine has between 1 and 4 Gigabytes physical RAM, then
465 If more than 4 Gigabytes is used then answer "64GB" here. This
466 selection turns Intel PAE (Physical Address Extension) mode on.
467 PAE implements 3-level paging on IA32 processors. PAE is fully
468 supported by Linux, PAE mode is implemented on all recent Intel
469 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
470 then the kernel will not boot on CPUs that don't support PAE!
472 The actual amount of total physical memory will either be
473 auto detected or can be forced by using a kernel command line option
474 such as "mem=256M". (Try "man bootparam" or see the documentation of
475 your boot loader (lilo or loadlin) about how to pass options to the
476 kernel at boot time.)
478 If unsure, say "off".
482 depends on !X86_NUMAQ
484 Select this if you have a 32-bit processor and between 1 and 4
485 gigabytes of physical RAM.
489 depends on X86_CMPXCHG64
491 Select this if you have a 32-bit processor and more than 4
492 gigabytes of physical RAM.
497 depends on EXPERIMENTAL
498 prompt "Memory split" if EMBEDDED
501 Select the desired split between kernel and user memory.
503 If the address range available to the kernel is less than the
504 physical memory installed, the remaining memory will be available
505 as "high memory". Accessing high memory is a little more costly
506 than low memory, as it needs to be mapped into the kernel first.
507 Note that increasing the kernel address space limits the range
508 available to user programs, making the address space there
509 tighter. Selecting anything other than the default 3G/1G split
510 will also likely make your kernel incompatible with binary-only
513 If you are not absolutely sure what you are doing, leave this
517 bool "3G/1G user/kernel split"
518 config VMSPLIT_3G_OPT
520 bool "3G/1G user/kernel split (for full 1G low memory)"
522 bool "2G/2G user/kernel split"
524 bool "1G/3G user/kernel split"
529 default 0xB0000000 if VMSPLIT_3G_OPT
530 default 0x78000000 if VMSPLIT_2G
531 default 0x40000000 if VMSPLIT_1G
536 depends on HIGHMEM64G || HIGHMEM4G
541 depends on HIGHMEM64G
543 select RESOURCES_64BIT
545 # Common NUMA Features
547 bool "Numa Memory Allocation and Scheduler Support"
548 depends on SMP && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI)
550 default y if (X86_NUMAQ || X86_SUMMIT)
552 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
553 depends on X86_SUMMIT && (!HIGHMEM64G || !ACPI)
557 default "4" if X86_NUMAQ
559 depends on NEED_MULTIPLE_NODES
561 config HAVE_ARCH_BOOTMEM_NODE
566 config ARCH_HAVE_MEMORY_PRESENT
568 depends on DISCONTIGMEM
571 config NEED_NODE_MEMMAP_SIZE
573 depends on DISCONTIGMEM || SPARSEMEM
576 config HAVE_ARCH_ALLOC_REMAP
581 config ARCH_FLATMEM_ENABLE
583 depends on (ARCH_SELECT_MEMORY_MODEL && X86_PC)
585 config ARCH_DISCONTIGMEM_ENABLE
589 config ARCH_DISCONTIGMEM_DEFAULT
593 config ARCH_SPARSEMEM_ENABLE
595 depends on (NUMA || (X86_PC && EXPERIMENTAL))
596 select SPARSEMEM_STATIC
598 config ARCH_SELECT_MEMORY_MODEL
600 depends on ARCH_SPARSEMEM_ENABLE
604 config HAVE_ARCH_EARLY_PFN_TO_NID
610 bool "Allocate 3rd-level pagetables from highmem"
611 depends on HIGHMEM4G || HIGHMEM64G
613 The VM uses one page table entry for each page of physical memory.
614 For systems with a lot of RAM, this can be wasteful of precious
615 low memory. Setting this option will put user-space page table
616 entries in high memory.
618 config MATH_EMULATION
619 bool "Math emulation"
621 Linux can emulate a math coprocessor (used for floating point
622 operations) if you don't have one. 486DX and Pentium processors have
623 a math coprocessor built in, 486SX and 386 do not, unless you added
624 a 487DX or 387, respectively. (The messages during boot time can
625 give you some hints here ["man dmesg"].) Everyone needs either a
626 coprocessor or this emulation.
628 If you don't have a math coprocessor, you need to say Y here; if you
629 say Y here even though you have a coprocessor, the coprocessor will
630 be used nevertheless. (This behavior can be changed with the kernel
631 command line option "no387", which comes handy if your coprocessor
632 is broken. Try "man bootparam" or see the documentation of your boot
633 loader (lilo or loadlin) about how to pass options to the kernel at
634 boot time.) This means that it is a good idea to say Y here if you
635 intend to use this kernel on different machines.
637 More information about the internals of the Linux math coprocessor
638 emulation can be found in <file:arch/i386/math-emu/README>.
640 If you are not sure, say Y; apart from resulting in a 66 KB bigger
641 kernel, it won't hurt.
644 bool "MTRR (Memory Type Range Register) support"
646 On Intel P6 family processors (Pentium Pro, Pentium II and later)
647 the Memory Type Range Registers (MTRRs) may be used to control
648 processor access to memory ranges. This is most useful if you have
649 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
650 allows bus write transfers to be combined into a larger transfer
651 before bursting over the PCI/AGP bus. This can increase performance
652 of image write operations 2.5 times or more. Saying Y here creates a
653 /proc/mtrr file which may be used to manipulate your processor's
654 MTRRs. Typically the X server should use this.
656 This code has a reasonably generic interface so that similar
657 control registers on other processors can be easily supported
660 The Cyrix 6x86, 6x86MX and M II processors have Address Range
661 Registers (ARRs) which provide a similar functionality to MTRRs. For
662 these, the ARRs are used to emulate the MTRRs.
663 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
664 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
665 write-combining. All of these processors are supported by this code
666 and it makes sense to say Y here if you have one of them.
668 Saying Y here also fixes a problem with buggy SMP BIOSes which only
669 set the MTRRs for the boot CPU and not for the secondary CPUs. This
670 can lead to all sorts of problems, so it's good to say Y here.
672 You can safely say Y even if your machine doesn't have MTRRs, you'll
673 just add about 9 KB to your kernel.
675 See <file:Documentation/mtrr.txt> for more information.
678 bool "Boot from EFI support"
682 This enables the the kernel to boot on EFI platforms using
683 system configuration information passed to it from the firmware.
684 This also enables the kernel to use any EFI runtime services that are
685 available (such as the EFI variable services).
687 This option is only useful on systems that have EFI firmware
688 and will result in a kernel image that is ~8k larger. In addition,
689 you must use the latest ELILO loader available at
690 <http://elilo.sourceforge.net> in order to take advantage of
691 kernel initialization using EFI information (neither GRUB nor LILO know
692 anything about EFI). However, even with this option, the resultant
693 kernel should continue to boot on existing non-EFI platforms.
696 bool "Enable kernel irq balancing"
697 depends on SMP && X86_IO_APIC
700 The default yes will allow the kernel to do irq load balancing.
701 Saying no will keep the kernel from doing irq load balancing.
703 # turning this on wastes a bunch of space.
704 # Summit needs it only when NUMA is on
707 depends on (((X86_SUMMIT || X86_GENERICARCH) && NUMA) || (X86 && EFI))
711 bool "Use register arguments"
714 Compile the kernel with -mregparm=3. This instructs gcc to use
715 a more efficient function call ABI which passes the first three
716 arguments of a function call via registers, which results in denser
719 If this option is disabled, then the default ABI of passing
720 arguments via the stack is used.
725 bool "Enable seccomp to safely compute untrusted bytecode"
729 This kernel feature is useful for number crunching applications
730 that may need to compute untrusted bytecode during their
731 execution. By using pipes or other transports made available to
732 the process as file descriptors supporting the read/write
733 syscalls, it's possible to isolate those applications in
734 their own address space using seccomp. Once seccomp is
735 enabled via /proc/<pid>/seccomp, it cannot be disabled
736 and the task is only allowed to execute a few safe syscalls
737 defined by each seccomp mode.
739 If unsure, say Y. Only embedded should say N here.
741 source kernel/Kconfig.hz
744 bool "kexec system call (EXPERIMENTAL)"
745 depends on EXPERIMENTAL
747 kexec is a system call that implements the ability to shutdown your
748 current kernel, and to start another kernel. It is like a reboot
749 but it is independent of the system firmware. And like a reboot
750 you can start any kernel with it, not just Linux.
752 The name comes from the similarity to the exec system call.
754 It is an ongoing process to be certain the hardware in a machine
755 is properly shutdown, so do not be surprised if this code does not
756 initially work for you. It may help to enable device hotplugging
757 support. As of this writing the exact hardware interface is
758 strongly in flux, so no good recommendation can be made.
761 bool "kernel crash dumps (EXPERIMENTAL)"
762 depends on EXPERIMENTAL
765 Generate crash dump after being started by kexec.
767 config PHYSICAL_START
768 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
770 default "0x1000000" if CRASH_DUMP
773 This gives the physical address where the kernel is loaded. Normally
774 for regular kernels this value is 0x100000 (1MB). But in the case
775 of kexec on panic the fail safe kernel needs to run at a different
776 address than the panic-ed kernel. This option is used to set the load
777 address for kernels used to capture crash dump on being kexec'ed
778 after panic. The default value for crash dump kernels is
779 0x1000000 (16MB). This can also be set based on the "X" value as
780 specified in the "crashkernel=YM@XM" command line boot parameter
781 passed to the panic-ed kernel. Typically this parameter is set as
782 crashkernel=64M@16M. Please take a look at
783 Documentation/kdump/kdump.txt for more details about crash dumps.
785 Don't change this unless you know what you are doing.
788 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
789 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
791 Say Y here to experiment with turning CPUs off and on, and to
792 enable suspend on SMP systems. CPUs can be controlled through
793 /sys/devices/system/cpu.
796 bool "Compat VDSO support"
800 Map the VDSO to the predictable old-style address too.
802 Say N here if you are running a sufficiently recent glibc
803 version (2.3.3 or later), to remove the high-mapped
804 VDSO mapping and to exclusively use the randomized VDSO.
810 config ARCH_ENABLE_MEMORY_HOTPLUG
814 menu "Power management options (ACPI, APM)"
815 depends on !X86_VOYAGER
817 source kernel/power/Kconfig
819 source "drivers/acpi/Kconfig"
821 menu "APM (Advanced Power Management) BIOS Support"
822 depends on PM && !X86_VISWS
825 tristate "APM (Advanced Power Management) BIOS support"
828 APM is a BIOS specification for saving power using several different
829 techniques. This is mostly useful for battery powered laptops with
830 APM compliant BIOSes. If you say Y here, the system time will be
831 reset after a RESUME operation, the /proc/apm device will provide
832 battery status information, and user-space programs will receive
833 notification of APM "events" (e.g. battery status change).
835 If you select "Y" here, you can disable actual use of the APM
836 BIOS by passing the "apm=off" option to the kernel at boot time.
838 Note that the APM support is almost completely disabled for
839 machines with more than one CPU.
841 In order to use APM, you will need supporting software. For location
842 and more information, read <file:Documentation/pm.txt> and the
843 Battery Powered Linux mini-HOWTO, available from
844 <http://www.tldp.org/docs.html#howto>.
846 This driver does not spin down disk drives (see the hdparm(8)
847 manpage ("man 8 hdparm") for that), and it doesn't turn off
848 VESA-compliant "green" monitors.
850 This driver does not support the TI 4000M TravelMate and the ACER
851 486/DX4/75 because they don't have compliant BIOSes. Many "green"
852 desktop machines also don't have compliant BIOSes, and this driver
853 may cause those machines to panic during the boot phase.
855 Generally, if you don't have a battery in your machine, there isn't
856 much point in using this driver and you should say N. If you get
857 random kernel OOPSes or reboots that don't seem to be related to
858 anything, try disabling/enabling this option (or disabling/enabling
861 Some other things you should try when experiencing seemingly random,
864 1) make sure that you have enough swap space and that it is
866 2) pass the "no-hlt" option to the kernel
867 3) switch on floating point emulation in the kernel and pass
868 the "no387" option to the kernel
869 4) pass the "floppy=nodma" option to the kernel
870 5) pass the "mem=4M" option to the kernel (thereby disabling
871 all but the first 4 MB of RAM)
872 6) make sure that the CPU is not over clocked.
873 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
874 8) disable the cache from your BIOS settings
875 9) install a fan for the video card or exchange video RAM
876 10) install a better fan for the CPU
877 11) exchange RAM chips
878 12) exchange the motherboard.
880 To compile this driver as a module, choose M here: the
881 module will be called apm.
883 config APM_IGNORE_USER_SUSPEND
884 bool "Ignore USER SUSPEND"
887 This option will ignore USER SUSPEND requests. On machines with a
888 compliant APM BIOS, you want to say N. However, on the NEC Versa M
889 series notebooks, it is necessary to say Y because of a BIOS bug.
892 bool "Enable PM at boot time"
895 Enable APM features at boot time. From page 36 of the APM BIOS
896 specification: "When disabled, the APM BIOS does not automatically
897 power manage devices, enter the Standby State, enter the Suspend
898 State, or take power saving steps in response to CPU Idle calls."
899 This driver will make CPU Idle calls when Linux is idle (unless this
900 feature is turned off -- see "Do CPU IDLE calls", below). This
901 should always save battery power, but more complicated APM features
902 will be dependent on your BIOS implementation. You may need to turn
903 this option off if your computer hangs at boot time when using APM
904 support, or if it beeps continuously instead of suspending. Turn
905 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
906 T400CDT. This is off by default since most machines do fine without
910 bool "Make CPU Idle calls when idle"
913 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
914 On some machines, this can activate improved power savings, such as
915 a slowed CPU clock rate, when the machine is idle. These idle calls
916 are made after the idle loop has run for some length of time (e.g.,
917 333 mS). On some machines, this will cause a hang at boot time or
918 whenever the CPU becomes idle. (On machines with more than one CPU,
919 this option does nothing.)
921 config APM_DISPLAY_BLANK
922 bool "Enable console blanking using APM"
925 Enable console blanking using the APM. Some laptops can use this to
926 turn off the LCD backlight when the screen blanker of the Linux
927 virtual console blanks the screen. Note that this is only used by
928 the virtual console screen blanker, and won't turn off the backlight
929 when using the X Window system. This also doesn't have anything to
930 do with your VESA-compliant power-saving monitor. Further, this
931 option doesn't work for all laptops -- it might not turn off your
932 backlight at all, or it might print a lot of errors to the console,
933 especially if you are using gpm.
935 config APM_RTC_IS_GMT
936 bool "RTC stores time in GMT"
939 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
940 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
943 It is in fact recommended to store GMT in your RTC, because then you
944 don't have to worry about daylight savings time changes. The only
945 reason not to use GMT in your RTC is if you also run a broken OS
946 that doesn't understand GMT.
948 config APM_ALLOW_INTS
949 bool "Allow interrupts during APM BIOS calls"
952 Normally we disable external interrupts while we are making calls to
953 the APM BIOS as a measure to lessen the effects of a badly behaving
954 BIOS implementation. The BIOS should reenable interrupts if it
955 needs to. Unfortunately, some BIOSes do not -- especially those in
956 many of the newer IBM Thinkpads. If you experience hangs when you
957 suspend, try setting this to Y. Otherwise, say N.
959 config APM_REAL_MODE_POWER_OFF
960 bool "Use real mode APM BIOS call to power off"
963 Use real mode APM BIOS calls to switch off the computer. This is
964 a work-around for a number of buggy BIOSes. Switch this option on if
965 your computer crashes instead of powering off properly.
969 source "arch/i386/kernel/cpu/cpufreq/Kconfig"
973 menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
976 bool "PCI support" if !X86_VISWS
977 depends on !X86_VOYAGER
978 default y if X86_VISWS
980 Find out whether you have a PCI motherboard. PCI is the name of a
981 bus system, i.e. the way the CPU talks to the other stuff inside
982 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
983 VESA. If you have PCI, say Y, otherwise N.
985 The PCI-HOWTO, available from
986 <http://www.tldp.org/docs.html#howto>, contains valuable
987 information about which PCI hardware does work under Linux and which
991 prompt "PCI access mode"
992 depends on PCI && !X86_VISWS
995 On PCI systems, the BIOS can be used to detect the PCI devices and
996 determine their configuration. However, some old PCI motherboards
997 have BIOS bugs and may crash if this is done. Also, some embedded
998 PCI-based systems don't have any BIOS at all. Linux can also try to
999 detect the PCI hardware directly without using the BIOS.
1001 With this option, you can specify how Linux should detect the
1002 PCI devices. If you choose "BIOS", the BIOS will be used,
1003 if you choose "Direct", the BIOS won't be used, and if you
1004 choose "MMConfig", then PCI Express MMCONFIG will be used.
1005 If you choose "Any", the kernel will try MMCONFIG, then the
1006 direct access method and falls back to the BIOS if that doesn't
1007 work. If unsure, go with the default, which is "Any".
1012 config PCI_GOMMCONFIG
1025 depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1030 depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1035 depends on PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1038 source "drivers/pci/pcie/Kconfig"
1040 source "drivers/pci/Kconfig"
1048 depends on !(X86_VOYAGER || X86_VISWS)
1050 Find out whether you have ISA slots on your motherboard. ISA is the
1051 name of a bus system, i.e. the way the CPU talks to the other stuff
1052 inside your box. Other bus systems are PCI, EISA, MicroChannel
1053 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1054 newer boards don't support it. If you have ISA, say Y, otherwise N.
1060 The Extended Industry Standard Architecture (EISA) bus was
1061 developed as an open alternative to the IBM MicroChannel bus.
1063 The EISA bus provided some of the features of the IBM MicroChannel
1064 bus while maintaining backward compatibility with cards made for
1065 the older ISA bus. The EISA bus saw limited use between 1988 and
1066 1995 when it was made obsolete by the PCI bus.
1068 Say Y here if you are building a kernel for an EISA-based machine.
1072 source "drivers/eisa/Kconfig"
1075 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1076 default y if X86_VOYAGER
1078 MicroChannel Architecture is found in some IBM PS/2 machines and
1079 laptops. It is a bus system similar to PCI or ISA. See
1080 <file:Documentation/mca.txt> (and especially the web page given
1081 there) before attempting to build an MCA bus kernel.
1083 source "drivers/mca/Kconfig"
1086 tristate "NatSemi SCx200 support"
1087 depends on !X86_VOYAGER
1089 This provides basic support for National Semiconductor's
1090 (now AMD's) Geode processors. The driver probes for the
1091 PCI-IDs of several on-chip devices, so its a good dependency
1092 for other scx200_* drivers.
1094 If compiled as a module, the driver is named scx200.
1096 config SCx200HR_TIMER
1097 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1098 depends on SCx200 && GENERIC_TIME
1101 This driver provides a clocksource built upon the on-chip
1102 27MHz high-resolution timer. Its also a workaround for
1103 NSC Geode SC-1100's buggy TSC, which loses time when the
1104 processor goes idle (as is done by the scheduler). The
1105 other workaround is idle=poll boot option.
1109 depends on AGP_AMD64
1111 source "drivers/pcmcia/Kconfig"
1113 source "drivers/pci/hotplug/Kconfig"
1117 menu "Executable file formats"
1119 source "fs/Kconfig.binfmt"
1123 source "net/Kconfig"
1125 source "drivers/Kconfig"
1129 menu "Instrumentation Support"
1130 depends on EXPERIMENTAL
1132 source "arch/i386/oprofile/Kconfig"
1135 bool "Kprobes (EXPERIMENTAL)"
1136 depends on EXPERIMENTAL && MODULES
1138 Kprobes allows you to trap at almost any kernel address and
1139 execute a callback function. register_kprobe() establishes
1140 a probepoint and specifies the callback. Kprobes is useful
1141 for kernel debugging, non-intrusive instrumentation and testing.
1142 If in doubt, say "N".
1145 source "arch/i386/Kconfig.debug"
1147 source "security/Kconfig"
1149 source "crypto/Kconfig"
1151 source "lib/Kconfig"
1154 # Use the generic interrupt handling code in kernel/irq/:
1156 config GENERIC_HARDIRQS
1160 config GENERIC_IRQ_PROBE
1164 config GENERIC_PENDING_IRQ
1166 depends on GENERIC_HARDIRQS && SMP
1171 depends on SMP && !X86_VOYAGER
1176 depends on SMP && !(X86_VISWS || X86_VOYAGER)
1179 config X86_BIOS_REBOOT
1181 depends on !(X86_VISWS || X86_VOYAGER)
1184 config X86_TRAMPOLINE
1186 depends on X86_SMP || (X86_VOYAGER && SMP)
projects / linux-2.6 / blob