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.
17 config SEMAPHORE_SLEEPERS
32 config GENERIC_ISA_DMA
40 config ARCH_MAY_HAVE_PC_FDC
50 menu "Processor type and features"
53 prompt "Subarchitecture Type"
59 Choose this option if your computer is a standard PC or compatible.
64 Select this for an AMD Elan processor.
66 Do not use this option for K6/Athlon/Opteron processors!
68 If unsure, choose "PC-compatible" instead.
73 Voyager is an MCA-based 32-way capable SMP architecture proprietary
74 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
78 If you do not specifically know you have a Voyager based machine,
79 say N here, otherwise the kernel you build will not be bootable.
82 bool "NUMAQ (IBM/Sequent)"
86 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
87 multiquad box. This changes the way that processors are bootstrapped,
88 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
89 You will need a new lynxer.elf file to flash your firmware with - send
90 email to <Martin.Bligh@us.ibm.com>.
93 bool "Summit/EXA (IBM x440)"
96 This option is needed for IBM systems that use the Summit/EXA chipset.
97 In particular, it is needed for the x440.
99 If you don't have one of these computers, you should say N here.
102 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
105 This option is needed for the systems that have more than 8 CPUs
106 and if the system is not of any sub-arch type above.
108 If you don't have such a system, you should say N here.
111 bool "SGI 320/540 (Visual Workstation)"
113 The SGI Visual Workstation series is an IA32-based workstation
114 based on SGI systems chips with some legacy PC hardware attached.
116 Say Y here to create a kernel to run on the SGI 320 or 540.
118 A kernel compiled for the Visual Workstation will not run on PCs
119 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
121 config X86_GENERICARCH
122 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
125 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
126 It is intended for a generic binary kernel.
129 bool "Support for Unisys ES7000 IA32 series"
132 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
133 supposed to run on an IA32-based Unisys ES7000 system.
134 Only choose this option if you have such a system, otherwise you
142 depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
144 config X86_SUMMIT_NUMA
147 depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
149 config X86_CYCLONE_TIMER
152 depends on X86_SUMMIT || X86_GENERICARCH
154 config ES7000_CLUSTERED_APIC
157 depends on SMP && X86_ES7000 && MPENTIUMIII
159 source "arch/i386/Kconfig.cpu"
162 bool "HPET Timer Support"
164 This enables the use of the HPET for the kernel's internal timer.
165 HPET is the next generation timer replacing legacy 8254s.
166 You can safely choose Y here. However, HPET will only be
167 activated if the platform and the BIOS support this feature.
168 Otherwise the 8254 will be used for timing services.
170 Choose N to continue using the legacy 8254 timer.
172 config HPET_EMULATE_RTC
174 depends on HPET_TIMER && RTC=y
178 bool "Symmetric multi-processing support"
180 This enables support for systems with more than one CPU. If you have
181 a system with only one CPU, like most personal computers, say N. If
182 you have a system with more than one CPU, say Y.
184 If you say N here, the kernel will run on single and multiprocessor
185 machines, but will use only one CPU of a multiprocessor machine. If
186 you say Y here, the kernel will run on many, but not all,
187 singleprocessor machines. On a singleprocessor machine, the kernel
188 will run faster if you say N here.
190 Note that if you say Y here and choose architecture "586" or
191 "Pentium" under "Processor family", the kernel will not work on 486
192 architectures. Similarly, multiprocessor kernels for the "PPro"
193 architecture may not work on all Pentium based boards.
195 People using multiprocessor machines who say Y here should also say
196 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
197 Management" code will be disabled if you say Y here.
199 See also the <file:Documentation/smp.txt>,
200 <file:Documentation/i386/IO-APIC.txt>,
201 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
202 <http://www.tldp.org/docs.html#howto>.
204 If you don't know what to do here, say N.
207 int "Maximum number of CPUs (2-255)"
210 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
213 This allows you to specify the maximum number of CPUs which this
214 kernel will support. The maximum supported value is 255 and the
215 minimum value which makes sense is 2.
217 This is purely to save memory - each supported CPU adds
218 approximately eight kilobytes to the kernel image.
221 bool "SMT (Hyperthreading) scheduler support"
225 SMT scheduler support improves the CPU scheduler's decision making
226 when dealing with Intel Pentium 4 chips with HyperThreading at a
227 cost of slightly increased overhead in some places. If unsure say
230 source "kernel/Kconfig.preempt"
233 bool "Local APIC support on uniprocessors"
234 depends on !SMP && !(X86_VISWS || X86_VOYAGER)
236 A local APIC (Advanced Programmable Interrupt Controller) is an
237 integrated interrupt controller in the CPU. If you have a single-CPU
238 system which has a processor with a local APIC, you can say Y here to
239 enable and use it. If you say Y here even though your machine doesn't
240 have a local APIC, then the kernel will still run with no slowdown at
241 all. The local APIC supports CPU-generated self-interrupts (timer,
242 performance counters), and the NMI watchdog which detects hard
246 bool "IO-APIC support on uniprocessors"
247 depends on X86_UP_APIC
249 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
250 SMP-capable replacement for PC-style interrupt controllers. Most
251 SMP systems and many recent uniprocessor systems have one.
253 If you have a single-CPU system with an IO-APIC, you can say Y here
254 to use it. If you say Y here even though your machine doesn't have
255 an IO-APIC, then the kernel will still run with no slowdown at all.
257 config X86_LOCAL_APIC
259 depends on X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER)
264 depends on X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER))
267 config X86_VISWS_APIC
273 bool "Machine Check Exception"
274 depends on !X86_VOYAGER
276 Machine Check Exception support allows the processor to notify the
277 kernel if it detects a problem (e.g. overheating, component failure).
278 The action the kernel takes depends on the severity of the problem,
279 ranging from a warning message on the console, to halting the machine.
280 Your processor must be a Pentium or newer to support this - check the
281 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
282 have a design flaw which leads to false MCE events - hence MCE is
283 disabled on all P5 processors, unless explicitly enabled with "mce"
284 as a boot argument. Similarly, if MCE is built in and creates a
285 problem on some new non-standard machine, you can boot with "nomce"
286 to disable it. MCE support simply ignores non-MCE processors like
287 the 386 and 486, so nearly everyone can say Y here.
289 config X86_MCE_NONFATAL
290 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
293 Enabling this feature starts a timer that triggers every 5 seconds which
294 will look at the machine check registers to see if anything happened.
295 Non-fatal problems automatically get corrected (but still logged).
296 Disable this if you don't want to see these messages.
297 Seeing the messages this option prints out may be indicative of dying hardware,
298 or out-of-spec (ie, overclocked) hardware.
299 This option only does something on certain CPUs.
300 (AMD Athlon/Duron and Intel Pentium 4)
302 config X86_MCE_P4THERMAL
303 bool "check for P4 thermal throttling interrupt."
304 depends on X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
306 Enabling this feature will cause a message to be printed when the P4
307 enters thermal throttling.
310 tristate "Toshiba Laptop support"
312 This adds a driver to safely access the System Management Mode of
313 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
314 not work on models with a Phoenix BIOS. The System Management Mode
315 is used to set the BIOS and power saving options on Toshiba portables.
317 For information on utilities to make use of this driver see the
318 Toshiba Linux utilities web site at:
319 <http://www.buzzard.org.uk/toshiba/>.
321 Say Y if you intend to run this kernel on a Toshiba portable.
325 tristate "Dell laptop support"
327 This adds a driver to safely access the System Management Mode
328 of the CPU on the Dell Inspiron 8000. The System Management Mode
329 is used to read cpu temperature and cooling fan status and to
330 control the fans on the I8K portables.
332 This driver has been tested only on the Inspiron 8000 but it may
333 also work with other Dell laptops. You can force loading on other
334 models by passing the parameter `force=1' to the module. Use at
337 For information on utilities to make use of this driver see the
338 I8K Linux utilities web site at:
339 <http://people.debian.org/~dz/i8k/>
341 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
344 config X86_REBOOTFIXUPS
345 bool "Enable X86 board specific fixups for reboot"
349 This enables chipset and/or board specific fixups to be done
350 in order to get reboot to work correctly. This is only needed on
351 some combinations of hardware and BIOS. The symptom, for which
352 this config is intended, is when reboot ends with a stalled/hung
355 Currently, the only fixup is for the Geode GX1/CS5530A/TROM2.1.
358 Say Y if you want to enable the fixup. Currently, it's safe to
359 enable this option even if you don't need it.
363 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
365 If you say Y here and also to "/dev file system support" in the
366 'File systems' section, you will be able to update the microcode on
367 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
368 Pentium III, Pentium 4, Xeon etc. You will obviously need the
369 actual microcode binary data itself which is not shipped with the
372 For latest news and information on obtaining all the required
373 ingredients for this driver, check:
374 <http://www.urbanmyth.org/microcode/>.
376 To compile this driver as a module, choose M here: the
377 module will be called microcode.
380 tristate "/dev/cpu/*/msr - Model-specific register support"
382 This device gives privileged processes access to the x86
383 Model-Specific Registers (MSRs). It is a character device with
384 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
385 MSR accesses are directed to a specific CPU on multi-processor
389 tristate "/dev/cpu/*/cpuid - CPU information support"
391 This device gives processes access to the x86 CPUID instruction to
392 be executed on a specific processor. It is a character device
393 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
396 source "drivers/firmware/Kconfig"
399 prompt "High Memory Support"
404 depends on !X86_NUMAQ
406 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
407 However, the address space of 32-bit x86 processors is only 4
408 Gigabytes large. That means that, if you have a large amount of
409 physical memory, not all of it can be "permanently mapped" by the
410 kernel. The physical memory that's not permanently mapped is called
413 If you are compiling a kernel which will never run on a machine with
414 more than 1 Gigabyte total physical RAM, answer "off" here (default
415 choice and suitable for most users). This will result in a "3GB/1GB"
416 split: 3GB are mapped so that each process sees a 3GB virtual memory
417 space and the remaining part of the 4GB virtual memory space is used
418 by the kernel to permanently map as much physical memory as
421 If the machine has between 1 and 4 Gigabytes physical RAM, then
424 If more than 4 Gigabytes is used then answer "64GB" here. This
425 selection turns Intel PAE (Physical Address Extension) mode on.
426 PAE implements 3-level paging on IA32 processors. PAE is fully
427 supported by Linux, PAE mode is implemented on all recent Intel
428 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
429 then the kernel will not boot on CPUs that don't support PAE!
431 The actual amount of total physical memory will either be
432 auto detected or can be forced by using a kernel command line option
433 such as "mem=256M". (Try "man bootparam" or see the documentation of
434 your boot loader (lilo or loadlin) about how to pass options to the
435 kernel at boot time.)
437 If unsure, say "off".
441 depends on !X86_NUMAQ
443 Select this if you have a 32-bit processor and between 1 and 4
444 gigabytes of physical RAM.
448 depends on X86_CMPXCHG64
450 Select this if you have a 32-bit processor and more than 4
451 gigabytes of physical RAM.
456 depends on EXPERIMENTAL && !X86_PAE
457 prompt "Memory split"
460 Select the desired split between kernel and user memory.
462 If the address range available to the kernel is less than the
463 physical memory installed, the remaining memory will be available
464 as "high memory". Accessing high memory is a little more costly
465 than low memory, as it needs to be mapped into the kernel first.
466 Note that increasing the kernel address space limits the range
467 available to user programs, making the address space there
468 tighter. Selecting anything other than the default 3G/1G split
469 will also likely make your kernel incompatible with binary-only
472 If you are not absolutely sure what you are doing, leave this
476 bool "3G/1G user/kernel split"
477 config VMSPLIT_3G_OPT
478 bool "3G/1G user/kernel split (for full 1G low memory)"
480 bool "2G/2G user/kernel split"
482 bool "1G/3G user/kernel split"
487 default 0xB0000000 if VMSPLIT_3G_OPT
488 default 0x78000000 if VMSPLIT_2G
489 default 0x40000000 if VMSPLIT_1G
494 depends on HIGHMEM64G || HIGHMEM4G
499 depends on HIGHMEM64G
502 # Common NUMA Features
504 bool "Numa Memory Allocation and Scheduler Support"
505 depends on SMP && HIGHMEM64G && (X86_NUMAQ || X86_GENERICARCH || (X86_SUMMIT && ACPI))
507 default y if (X86_NUMAQ || X86_SUMMIT)
509 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
510 depends on X86_SUMMIT && (!HIGHMEM64G || !ACPI)
512 config HAVE_ARCH_BOOTMEM_NODE
517 config ARCH_HAVE_MEMORY_PRESENT
519 depends on DISCONTIGMEM
522 config NEED_NODE_MEMMAP_SIZE
524 depends on DISCONTIGMEM || SPARSEMEM
527 config HAVE_ARCH_ALLOC_REMAP
532 config ARCH_FLATMEM_ENABLE
534 depends on (ARCH_SELECT_MEMORY_MODEL && X86_PC)
536 config ARCH_DISCONTIGMEM_ENABLE
540 config ARCH_DISCONTIGMEM_DEFAULT
544 config ARCH_SPARSEMEM_ENABLE
546 depends on (NUMA || (X86_PC && EXPERIMENTAL))
547 select SPARSEMEM_STATIC
549 config ARCH_SELECT_MEMORY_MODEL
551 depends on ARCH_SPARSEMEM_ENABLE
555 config HAVE_ARCH_EARLY_PFN_TO_NID
561 bool "Allocate 3rd-level pagetables from highmem"
562 depends on HIGHMEM4G || HIGHMEM64G
564 The VM uses one page table entry for each page of physical memory.
565 For systems with a lot of RAM, this can be wasteful of precious
566 low memory. Setting this option will put user-space page table
567 entries in high memory.
569 config MATH_EMULATION
570 bool "Math emulation"
572 Linux can emulate a math coprocessor (used for floating point
573 operations) if you don't have one. 486DX and Pentium processors have
574 a math coprocessor built in, 486SX and 386 do not, unless you added
575 a 487DX or 387, respectively. (The messages during boot time can
576 give you some hints here ["man dmesg"].) Everyone needs either a
577 coprocessor or this emulation.
579 If you don't have a math coprocessor, you need to say Y here; if you
580 say Y here even though you have a coprocessor, the coprocessor will
581 be used nevertheless. (This behavior can be changed with the kernel
582 command line option "no387", which comes handy if your coprocessor
583 is broken. Try "man bootparam" or see the documentation of your boot
584 loader (lilo or loadlin) about how to pass options to the kernel at
585 boot time.) This means that it is a good idea to say Y here if you
586 intend to use this kernel on different machines.
588 More information about the internals of the Linux math coprocessor
589 emulation can be found in <file:arch/i386/math-emu/README>.
591 If you are not sure, say Y; apart from resulting in a 66 KB bigger
592 kernel, it won't hurt.
595 bool "MTRR (Memory Type Range Register) support"
597 On Intel P6 family processors (Pentium Pro, Pentium II and later)
598 the Memory Type Range Registers (MTRRs) may be used to control
599 processor access to memory ranges. This is most useful if you have
600 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
601 allows bus write transfers to be combined into a larger transfer
602 before bursting over the PCI/AGP bus. This can increase performance
603 of image write operations 2.5 times or more. Saying Y here creates a
604 /proc/mtrr file which may be used to manipulate your processor's
605 MTRRs. Typically the X server should use this.
607 This code has a reasonably generic interface so that similar
608 control registers on other processors can be easily supported
611 The Cyrix 6x86, 6x86MX and M II processors have Address Range
612 Registers (ARRs) which provide a similar functionality to MTRRs. For
613 these, the ARRs are used to emulate the MTRRs.
614 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
615 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
616 write-combining. All of these processors are supported by this code
617 and it makes sense to say Y here if you have one of them.
619 Saying Y here also fixes a problem with buggy SMP BIOSes which only
620 set the MTRRs for the boot CPU and not for the secondary CPUs. This
621 can lead to all sorts of problems, so it's good to say Y here.
623 You can safely say Y even if your machine doesn't have MTRRs, you'll
624 just add about 9 KB to your kernel.
626 See <file:Documentation/mtrr.txt> for more information.
629 bool "Boot from EFI support (EXPERIMENTAL)"
633 This enables the the kernel to boot on EFI platforms using
634 system configuration information passed to it from the firmware.
635 This also enables the kernel to use any EFI runtime services that are
636 available (such as the EFI variable services).
638 This option is only useful on systems that have EFI firmware
639 and will result in a kernel image that is ~8k larger. In addition,
640 you must use the latest ELILO loader available at
641 <http://elilo.sourceforge.net> in order to take advantage of
642 kernel initialization using EFI information (neither GRUB nor LILO know
643 anything about EFI). However, even with this option, the resultant
644 kernel should continue to boot on existing non-EFI platforms.
647 bool "Enable kernel irq balancing"
648 depends on SMP && X86_IO_APIC
651 The default yes will allow the kernel to do irq load balancing.
652 Saying no will keep the kernel from doing irq load balancing.
654 # turning this on wastes a bunch of space.
655 # Summit needs it only when NUMA is on
658 depends on (((X86_SUMMIT || X86_GENERICARCH) && NUMA) || (X86 && EFI))
662 bool "Use register arguments"
665 Compile the kernel with -mregparm=3. This instructs gcc to use
666 a more efficient function call ABI which passes the first three
667 arguments of a function call via registers, which results in denser
670 If this option is disabled, then the default ABI of passing
671 arguments via the stack is used.
676 bool "Enable seccomp to safely compute untrusted bytecode"
680 This kernel feature is useful for number crunching applications
681 that may need to compute untrusted bytecode during their
682 execution. By using pipes or other transports made available to
683 the process as file descriptors supporting the read/write
684 syscalls, it's possible to isolate those applications in
685 their own address space using seccomp. Once seccomp is
686 enabled via /proc/<pid>/seccomp, it cannot be disabled
687 and the task is only allowed to execute a few safe syscalls
688 defined by each seccomp mode.
690 If unsure, say Y. Only embedded should say N here.
692 source kernel/Kconfig.hz
695 bool "kexec system call (EXPERIMENTAL)"
696 depends on EXPERIMENTAL
698 kexec is a system call that implements the ability to shutdown your
699 current kernel, and to start another kernel. It is like a reboot
700 but it is indepedent of the system firmware. And like a reboot
701 you can start any kernel with it, not just Linux.
703 The name comes from the similiarity to the exec system call.
705 It is an ongoing process to be certain the hardware in a machine
706 is properly shutdown, so do not be surprised if this code does not
707 initially work for you. It may help to enable device hotplugging
708 support. As of this writing the exact hardware interface is
709 strongly in flux, so no good recommendation can be made.
712 bool "kernel crash dumps (EXPERIMENTAL)"
713 depends on EXPERIMENTAL
716 Generate crash dump after being started by kexec.
718 config PHYSICAL_START
719 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
721 default "0x1000000" if CRASH_DUMP
724 This gives the physical address where the kernel is loaded. Normally
725 for regular kernels this value is 0x100000 (1MB). But in the case
726 of kexec on panic the fail safe kernel needs to run at a different
727 address than the panic-ed kernel. This option is used to set the load
728 address for kernels used to capture crash dump on being kexec'ed
729 after panic. The default value for crash dump kernels is
730 0x1000000 (16MB). This can also be set based on the "X" value as
731 specified in the "crashkernel=YM@XM" command line boot parameter
732 passed to the panic-ed kernel. Typically this parameter is set as
733 crashkernel=64M@16M. Please take a look at
734 Documentation/kdump/kdump.txt for more details about crash dumps.
736 Don't change this unless you know what you are doing.
739 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
740 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER && !X86_PC
742 Say Y here to experiment with turning CPUs off and on. CPUs
743 can be controlled through /sys/devices/system/cpu.
749 bool "Enable doublefault exception handler" if EMBEDDED
751 This option allows trapping of rare doublefault exceptions that
752 would otherwise cause a system to silently reboot. Disabling this
753 option saves about 4k and might cause you much additional grey
759 menu "Power management options (ACPI, APM)"
760 depends on !X86_VOYAGER
762 source kernel/power/Kconfig
764 source "drivers/acpi/Kconfig"
766 menu "APM (Advanced Power Management) BIOS Support"
767 depends on PM && !X86_VISWS
770 tristate "APM (Advanced Power Management) BIOS support"
773 APM is a BIOS specification for saving power using several different
774 techniques. This is mostly useful for battery powered laptops with
775 APM compliant BIOSes. If you say Y here, the system time will be
776 reset after a RESUME operation, the /proc/apm device will provide
777 battery status information, and user-space programs will receive
778 notification of APM "events" (e.g. battery status change).
780 If you select "Y" here, you can disable actual use of the APM
781 BIOS by passing the "apm=off" option to the kernel at boot time.
783 Note that the APM support is almost completely disabled for
784 machines with more than one CPU.
786 In order to use APM, you will need supporting software. For location
787 and more information, read <file:Documentation/pm.txt> and the
788 Battery Powered Linux mini-HOWTO, available from
789 <http://www.tldp.org/docs.html#howto>.
791 This driver does not spin down disk drives (see the hdparm(8)
792 manpage ("man 8 hdparm") for that), and it doesn't turn off
793 VESA-compliant "green" monitors.
795 This driver does not support the TI 4000M TravelMate and the ACER
796 486/DX4/75 because they don't have compliant BIOSes. Many "green"
797 desktop machines also don't have compliant BIOSes, and this driver
798 may cause those machines to panic during the boot phase.
800 Generally, if you don't have a battery in your machine, there isn't
801 much point in using this driver and you should say N. If you get
802 random kernel OOPSes or reboots that don't seem to be related to
803 anything, try disabling/enabling this option (or disabling/enabling
806 Some other things you should try when experiencing seemingly random,
809 1) make sure that you have enough swap space and that it is
811 2) pass the "no-hlt" option to the kernel
812 3) switch on floating point emulation in the kernel and pass
813 the "no387" option to the kernel
814 4) pass the "floppy=nodma" option to the kernel
815 5) pass the "mem=4M" option to the kernel (thereby disabling
816 all but the first 4 MB of RAM)
817 6) make sure that the CPU is not over clocked.
818 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
819 8) disable the cache from your BIOS settings
820 9) install a fan for the video card or exchange video RAM
821 10) install a better fan for the CPU
822 11) exchange RAM chips
823 12) exchange the motherboard.
825 To compile this driver as a module, choose M here: the
826 module will be called apm.
828 config APM_IGNORE_USER_SUSPEND
829 bool "Ignore USER SUSPEND"
832 This option will ignore USER SUSPEND requests. On machines with a
833 compliant APM BIOS, you want to say N. However, on the NEC Versa M
834 series notebooks, it is necessary to say Y because of a BIOS bug.
837 bool "Enable PM at boot time"
840 Enable APM features at boot time. From page 36 of the APM BIOS
841 specification: "When disabled, the APM BIOS does not automatically
842 power manage devices, enter the Standby State, enter the Suspend
843 State, or take power saving steps in response to CPU Idle calls."
844 This driver will make CPU Idle calls when Linux is idle (unless this
845 feature is turned off -- see "Do CPU IDLE calls", below). This
846 should always save battery power, but more complicated APM features
847 will be dependent on your BIOS implementation. You may need to turn
848 this option off if your computer hangs at boot time when using APM
849 support, or if it beeps continuously instead of suspending. Turn
850 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
851 T400CDT. This is off by default since most machines do fine without
855 bool "Make CPU Idle calls when idle"
858 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
859 On some machines, this can activate improved power savings, such as
860 a slowed CPU clock rate, when the machine is idle. These idle calls
861 are made after the idle loop has run for some length of time (e.g.,
862 333 mS). On some machines, this will cause a hang at boot time or
863 whenever the CPU becomes idle. (On machines with more than one CPU,
864 this option does nothing.)
866 config APM_DISPLAY_BLANK
867 bool "Enable console blanking using APM"
870 Enable console blanking using the APM. Some laptops can use this to
871 turn off the LCD backlight when the screen blanker of the Linux
872 virtual console blanks the screen. Note that this is only used by
873 the virtual console screen blanker, and won't turn off the backlight
874 when using the X Window system. This also doesn't have anything to
875 do with your VESA-compliant power-saving monitor. Further, this
876 option doesn't work for all laptops -- it might not turn off your
877 backlight at all, or it might print a lot of errors to the console,
878 especially if you are using gpm.
880 config APM_RTC_IS_GMT
881 bool "RTC stores time in GMT"
884 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
885 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
888 It is in fact recommended to store GMT in your RTC, because then you
889 don't have to worry about daylight savings time changes. The only
890 reason not to use GMT in your RTC is if you also run a broken OS
891 that doesn't understand GMT.
893 config APM_ALLOW_INTS
894 bool "Allow interrupts during APM BIOS calls"
897 Normally we disable external interrupts while we are making calls to
898 the APM BIOS as a measure to lessen the effects of a badly behaving
899 BIOS implementation. The BIOS should reenable interrupts if it
900 needs to. Unfortunately, some BIOSes do not -- especially those in
901 many of the newer IBM Thinkpads. If you experience hangs when you
902 suspend, try setting this to Y. Otherwise, say N.
904 config APM_REAL_MODE_POWER_OFF
905 bool "Use real mode APM BIOS call to power off"
908 Use real mode APM BIOS calls to switch off the computer. This is
909 a work-around for a number of buggy BIOSes. Switch this option on if
910 your computer crashes instead of powering off properly.
914 source "arch/i386/kernel/cpu/cpufreq/Kconfig"
918 menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
921 bool "PCI support" if !X86_VISWS
922 depends on !X86_VOYAGER
923 default y if X86_VISWS
925 Find out whether you have a PCI motherboard. PCI is the name of a
926 bus system, i.e. the way the CPU talks to the other stuff inside
927 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
928 VESA. If you have PCI, say Y, otherwise N.
930 The PCI-HOWTO, available from
931 <http://www.tldp.org/docs.html#howto>, contains valuable
932 information about which PCI hardware does work under Linux and which
936 prompt "PCI access mode"
937 depends on PCI && !X86_VISWS
940 On PCI systems, the BIOS can be used to detect the PCI devices and
941 determine their configuration. However, some old PCI motherboards
942 have BIOS bugs and may crash if this is done. Also, some embedded
943 PCI-based systems don't have any BIOS at all. Linux can also try to
944 detect the PCI hardware directly without using the BIOS.
946 With this option, you can specify how Linux should detect the
947 PCI devices. If you choose "BIOS", the BIOS will be used,
948 if you choose "Direct", the BIOS won't be used, and if you
949 choose "MMConfig", then PCI Express MMCONFIG will be used.
950 If you choose "Any", the kernel will try MMCONFIG, then the
951 direct access method and falls back to the BIOS if that doesn't
952 work. If unsure, go with the default, which is "Any".
957 config PCI_GOMMCONFIG
970 depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
975 depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
980 depends on PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
983 source "drivers/pci/pcie/Kconfig"
985 source "drivers/pci/Kconfig"
993 depends on !(X86_VOYAGER || X86_VISWS)
995 Find out whether you have ISA slots on your motherboard. ISA is the
996 name of a bus system, i.e. the way the CPU talks to the other stuff
997 inside your box. Other bus systems are PCI, EISA, MicroChannel
998 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
999 newer boards don't support it. If you have ISA, say Y, otherwise N.
1005 The Extended Industry Standard Architecture (EISA) bus was
1006 developed as an open alternative to the IBM MicroChannel bus.
1008 The EISA bus provided some of the features of the IBM MicroChannel
1009 bus while maintaining backward compatibility with cards made for
1010 the older ISA bus. The EISA bus saw limited use between 1988 and
1011 1995 when it was made obsolete by the PCI bus.
1013 Say Y here if you are building a kernel for an EISA-based machine.
1017 source "drivers/eisa/Kconfig"
1020 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1021 default y if X86_VOYAGER
1023 MicroChannel Architecture is found in some IBM PS/2 machines and
1024 laptops. It is a bus system similar to PCI or ISA. See
1025 <file:Documentation/mca.txt> (and especially the web page given
1026 there) before attempting to build an MCA bus kernel.
1028 source "drivers/mca/Kconfig"
1031 tristate "NatSemi SCx200 support"
1032 depends on !X86_VOYAGER
1034 This provides basic support for the National Semiconductor SCx200
1035 processor. Right now this is just a driver for the GPIO pins.
1037 If you don't know what to do here, say N.
1039 This support is also available as a module. If compiled as a
1040 module, it will be called scx200.
1042 source "drivers/pcmcia/Kconfig"
1044 source "drivers/pci/hotplug/Kconfig"
1048 menu "Executable file formats"
1050 source "fs/Kconfig.binfmt"
1054 source "net/Kconfig"
1056 source "drivers/Kconfig"
1060 menu "Instrumentation Support"
1061 depends on EXPERIMENTAL
1063 source "arch/i386/oprofile/Kconfig"
1066 bool "Kprobes (EXPERIMENTAL)"
1067 depends on EXPERIMENTAL && MODULES
1069 Kprobes allows you to trap at almost any kernel address and
1070 execute a callback function. register_kprobe() establishes
1071 a probepoint and specifies the callback. Kprobes is useful
1072 for kernel debugging, non-intrusive instrumentation and testing.
1073 If in doubt, say "N".
1076 source "arch/i386/Kconfig.debug"
1078 source "security/Kconfig"
1080 source "crypto/Kconfig"
1082 source "lib/Kconfig"
1085 # Use the generic interrupt handling code in kernel/irq/:
1087 config GENERIC_HARDIRQS
1091 config GENERIC_IRQ_PROBE
1095 config GENERIC_PENDING_IRQ
1097 depends on GENERIC_HARDIRQS && SMP
1102 depends on SMP && !X86_VOYAGER
1107 depends on SMP && !(X86_VISWS || X86_VOYAGER)
1110 config X86_BIOS_REBOOT
1112 depends on !(X86_VISWS || X86_VOYAGER)
1115 config X86_TRAMPOLINE
1117 depends on X86_SMP || (X86_VOYAGER && SMP)