2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
22 config GENERIC_LOCKBREAK
28 config GENERIC_CMOS_UPDATE
31 config CLOCKSOURCE_WATCHDOG
34 config GENERIC_CLOCKEVENTS
37 config GENERIC_CLOCKEVENTS_BROADCAST
39 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
41 config LOCKDEP_SUPPORT
44 config STACKTRACE_SUPPORT
47 config SEMAPHORE_SLEEPERS
62 config GENERIC_ISA_DMA
72 config GENERIC_HWEIGHT
78 config ARCH_MAY_HAVE_PC_FDC
84 config RWSEM_GENERIC_SPINLOCK
87 config RWSEM_XCHGADD_ALGORITHM
90 config ARCH_HAS_ILOG2_U32
93 config ARCH_HAS_ILOG2_U64
96 config GENERIC_CALIBRATE_DELAY
99 config GENERIC_TIME_VSYSCALL
103 config HAVE_SETUP_PER_CPU_AREA
106 config ARCH_SUPPORTS_OPROFILE
115 config ARCH_POPULATES_NODE_MAP
122 # Use the generic interrupt handling code in kernel/irq/:
123 config GENERIC_HARDIRQS
127 config GENERIC_IRQ_PROBE
131 config GENERIC_PENDING_IRQ
133 depends on GENERIC_HARDIRQS && SMP
138 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
143 depends on X86_32 && SMP
147 depends on X86_64 && SMP
152 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
155 config X86_BIOS_REBOOT
157 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
160 config X86_TRAMPOLINE
162 depends on X86_SMP || (X86_VOYAGER && SMP)
167 source "init/Kconfig"
169 menu "Processor type and features"
171 source "kernel/time/Kconfig"
174 bool "Symmetric multi-processing support"
176 This enables support for systems with more than one CPU. If you have
177 a system with only one CPU, like most personal computers, say N. If
178 you have a system with more than one CPU, say Y.
180 If you say N here, the kernel will run on single and multiprocessor
181 machines, but will use only one CPU of a multiprocessor machine. If
182 you say Y here, the kernel will run on many, but not all,
183 singleprocessor machines. On a singleprocessor machine, the kernel
184 will run faster if you say N here.
186 Note that if you say Y here and choose architecture "586" or
187 "Pentium" under "Processor family", the kernel will not work on 486
188 architectures. Similarly, multiprocessor kernels for the "PPro"
189 architecture may not work on all Pentium based boards.
191 People using multiprocessor machines who say Y here should also say
192 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
193 Management" code will be disabled if you say Y here.
195 See also the <file:Documentation/smp.txt>,
196 <file:Documentation/i386/IO-APIC.txt>,
197 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
198 <http://www.tldp.org/docs.html#howto>.
200 If you don't know what to do here, say N.
203 prompt "Subarchitecture Type"
209 Choose this option if your computer is a standard PC or compatible.
215 Select this for an AMD Elan processor.
217 Do not use this option for K6/Athlon/Opteron processors!
219 If unsure, choose "PC-compatible" instead.
224 select SMP if !BROKEN
226 Voyager is an MCA-based 32-way capable SMP architecture proprietary
227 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
231 If you do not specifically know you have a Voyager based machine,
232 say N here, otherwise the kernel you build will not be bootable.
235 bool "NUMAQ (IBM/Sequent)"
240 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
241 multiquad box. This changes the way that processors are bootstrapped,
242 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
243 You will need a new lynxer.elf file to flash your firmware with - send
244 email to <Martin.Bligh@us.ibm.com>.
247 bool "Summit/EXA (IBM x440)"
248 depends on X86_32 && SMP
250 This option is needed for IBM systems that use the Summit/EXA chipset.
251 In particular, it is needed for the x440.
253 If you don't have one of these computers, you should say N here.
254 If you want to build a NUMA kernel, you must select ACPI.
257 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
258 depends on X86_32 && SMP
260 This option is needed for the systems that have more than 8 CPUs
261 and if the system is not of any sub-arch type above.
263 If you don't have such a system, you should say N here.
266 bool "SGI 320/540 (Visual Workstation)"
269 The SGI Visual Workstation series is an IA32-based workstation
270 based on SGI systems chips with some legacy PC hardware attached.
272 Say Y here to create a kernel to run on the SGI 320 or 540.
274 A kernel compiled for the Visual Workstation will not run on PCs
275 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
277 config X86_GENERICARCH
278 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
281 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
282 It is intended for a generic binary kernel.
283 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
286 bool "Support for Unisys ES7000 IA32 series"
287 depends on X86_32 && SMP
289 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
290 supposed to run on an IA32-based Unisys ES7000 system.
291 Only choose this option if you have such a system, otherwise you
295 bool "Support for ScaleMP vSMP"
296 depends on X86_64 && PCI
298 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
299 supposed to run on these EM64T-based machines. Only choose this option
300 if you have one of these machines.
304 config SCHED_NO_NO_OMIT_FRAME_POINTER
306 prompt "Single-depth WCHAN output"
309 Calculate simpler /proc/<PID>/wchan values. If this option
310 is disabled then wchan values will recurse back to the
311 caller function. This provides more accurate wchan values,
312 at the expense of slightly more scheduling overhead.
314 If in doubt, say "Y".
316 menuconfig PARAVIRT_GUEST
317 bool "Paravirtualized guest support"
319 Say Y here to get to see options related to running Linux under
320 various hypervisors. This option alone does not add any kernel code.
322 If you say N, all options in this submenu will be skipped and disabled.
326 source "arch/x86/xen/Kconfig"
329 bool "VMI Guest support"
332 depends on !(X86_VISWS || X86_VOYAGER)
334 VMI provides a paravirtualized interface to the VMware ESX server
335 (it could be used by other hypervisors in theory too, but is not
336 at the moment), by linking the kernel to a GPL-ed ROM module
337 provided by the hypervisor.
339 source "arch/x86/lguest/Kconfig"
342 bool "Enable paravirtualization code"
343 depends on !(X86_VISWS || X86_VOYAGER)
345 This changes the kernel so it can modify itself when it is run
346 under a hypervisor, potentially improving performance significantly
347 over full virtualization. However, when run without a hypervisor
348 the kernel is theoretically slower and slightly larger.
354 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
357 config HAVE_ARCH_PARSE_SRAT
361 config X86_SUMMIT_NUMA
363 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
365 config X86_CYCLONE_TIMER
367 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
369 config ES7000_CLUSTERED_APIC
371 depends on SMP && X86_ES7000 && MPENTIUMIII
373 source "arch/x86/Kconfig.cpu"
377 prompt "HPET Timer Support" if X86_32
379 Use the IA-PC HPET (High Precision Event Timer) to manage
380 time in preference to the PIT and RTC, if a HPET is
382 HPET is the next generation timer replacing legacy 8254s.
383 The HPET provides a stable time base on SMP
384 systems, unlike the TSC, but it is more expensive to access,
385 as it is off-chip. You can find the HPET spec at
386 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
388 You can safely choose Y here. However, HPET will only be
389 activated if the platform and the BIOS support this feature.
390 Otherwise the 8254 will be used for timing services.
392 Choose N to continue using the legacy 8254 timer.
394 config HPET_EMULATE_RTC
396 depends on HPET_TIMER && (RTC=y || RTC=m)
398 # Mark as embedded because too many people got it wrong.
399 # The code disables itself when not needed.
401 bool "GART IOMMU support" if EMBEDDED
405 depends on X86_64 && PCI
407 Support for full DMA access of devices with 32bit memory access only
408 on systems with more than 3GB. This is usually needed for USB,
409 sound, many IDE/SATA chipsets and some other devices.
410 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
411 based hardware IOMMU and a software bounce buffer based IOMMU used
412 on Intel systems and as fallback.
413 The code is only active when needed (enough memory and limited
414 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
418 bool "IBM Calgary IOMMU support"
420 depends on X86_64 && PCI && EXPERIMENTAL
422 Support for hardware IOMMUs in IBM's xSeries x366 and x460
423 systems. Needed to run systems with more than 3GB of memory
424 properly with 32-bit PCI devices that do not support DAC
425 (Double Address Cycle). Calgary also supports bus level
426 isolation, where all DMAs pass through the IOMMU. This
427 prevents them from going anywhere except their intended
428 destination. This catches hard-to-find kernel bugs and
429 mis-behaving drivers and devices that do not use the DMA-API
430 properly to set up their DMA buffers. The IOMMU can be
431 turned off at boot time with the iommu=off parameter.
432 Normally the kernel will make the right choice by itself.
435 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
437 prompt "Should Calgary be enabled by default?"
438 depends on CALGARY_IOMMU
440 Should Calgary be enabled by default? if you choose 'y', Calgary
441 will be used (if it exists). If you choose 'n', Calgary will not be
442 used even if it exists. If you choose 'n' and would like to use
443 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
446 # need this always selected by IOMMU for the VIA workaround
450 Support for software bounce buffers used on x86-64 systems
451 which don't have a hardware IOMMU (e.g. the current generation
452 of Intel's x86-64 CPUs). Using this PCI devices which can only
453 access 32-bits of memory can be used on systems with more than
454 3 GB of memory. If unsure, say Y.
458 int "Maximum number of CPUs (2-255)"
461 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
464 This allows you to specify the maximum number of CPUs which this
465 kernel will support. The maximum supported value is 255 and the
466 minimum value which makes sense is 2.
468 This is purely to save memory - each supported CPU adds
469 approximately eight kilobytes to the kernel image.
472 bool "SMT (Hyperthreading) scheduler support"
473 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
475 SMT scheduler support improves the CPU scheduler's decision making
476 when dealing with Intel Pentium 4 chips with HyperThreading at a
477 cost of slightly increased overhead in some places. If unsure say
482 prompt "Multi-core scheduler support"
483 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
485 Multi-core scheduler support improves the CPU scheduler's decision
486 making when dealing with multi-core CPU chips at a cost of slightly
487 increased overhead in some places. If unsure say N here.
489 source "kernel/Kconfig.preempt"
492 bool "Local APIC support on uniprocessors"
493 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
495 A local APIC (Advanced Programmable Interrupt Controller) is an
496 integrated interrupt controller in the CPU. If you have a single-CPU
497 system which has a processor with a local APIC, you can say Y here to
498 enable and use it. If you say Y here even though your machine doesn't
499 have a local APIC, then the kernel will still run with no slowdown at
500 all. The local APIC supports CPU-generated self-interrupts (timer,
501 performance counters), and the NMI watchdog which detects hard
505 bool "IO-APIC support on uniprocessors"
506 depends on X86_UP_APIC
508 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
509 SMP-capable replacement for PC-style interrupt controllers. Most
510 SMP systems and many recent uniprocessor systems have one.
512 If you have a single-CPU system with an IO-APIC, you can say Y here
513 to use it. If you say Y here even though your machine doesn't have
514 an IO-APIC, then the kernel will still run with no slowdown at all.
516 config X86_LOCAL_APIC
518 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
522 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
524 config X86_VISWS_APIC
526 depends on X86_32 && X86_VISWS
529 bool "Machine Check Exception"
530 depends on !X86_VOYAGER
532 Machine Check Exception support allows the processor to notify the
533 kernel if it detects a problem (e.g. overheating, component failure).
534 The action the kernel takes depends on the severity of the problem,
535 ranging from a warning message on the console, to halting the machine.
536 Your processor must be a Pentium or newer to support this - check the
537 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
538 have a design flaw which leads to false MCE events - hence MCE is
539 disabled on all P5 processors, unless explicitly enabled with "mce"
540 as a boot argument. Similarly, if MCE is built in and creates a
541 problem on some new non-standard machine, you can boot with "nomce"
542 to disable it. MCE support simply ignores non-MCE processors like
543 the 386 and 486, so nearly everyone can say Y here.
547 prompt "Intel MCE features"
548 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
550 Additional support for intel specific MCE features such as
555 prompt "AMD MCE features"
556 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
558 Additional support for AMD specific MCE features such as
559 the DRAM Error Threshold.
561 config X86_MCE_NONFATAL
562 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
563 depends on X86_32 && X86_MCE
565 Enabling this feature starts a timer that triggers every 5 seconds which
566 will look at the machine check registers to see if anything happened.
567 Non-fatal problems automatically get corrected (but still logged).
568 Disable this if you don't want to see these messages.
569 Seeing the messages this option prints out may be indicative of dying
570 or out-of-spec (ie, overclocked) hardware.
571 This option only does something on certain CPUs.
572 (AMD Athlon/Duron and Intel Pentium 4)
574 config X86_MCE_P4THERMAL
575 bool "check for P4 thermal throttling interrupt."
576 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
578 Enabling this feature will cause a message to be printed when the P4
579 enters thermal throttling.
582 bool "Enable VM86 support" if EMBEDDED
586 This option is required by programs like DOSEMU to run 16-bit legacy
587 code on X86 processors. It also may be needed by software like
588 XFree86 to initialize some video cards via BIOS. Disabling this
589 option saves about 6k.
592 tristate "Toshiba Laptop support"
595 This adds a driver to safely access the System Management Mode of
596 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
597 not work on models with a Phoenix BIOS. The System Management Mode
598 is used to set the BIOS and power saving options on Toshiba portables.
600 For information on utilities to make use of this driver see the
601 Toshiba Linux utilities web site at:
602 <http://www.buzzard.org.uk/toshiba/>.
604 Say Y if you intend to run this kernel on a Toshiba portable.
608 tristate "Dell laptop support"
611 This adds a driver to safely access the System Management Mode
612 of the CPU on the Dell Inspiron 8000. The System Management Mode
613 is used to read cpu temperature and cooling fan status and to
614 control the fans on the I8K portables.
616 This driver has been tested only on the Inspiron 8000 but it may
617 also work with other Dell laptops. You can force loading on other
618 models by passing the parameter `force=1' to the module. Use at
621 For information on utilities to make use of this driver see the
622 I8K Linux utilities web site at:
623 <http://people.debian.org/~dz/i8k/>
625 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
628 config X86_REBOOTFIXUPS
630 prompt "Enable X86 board specific fixups for reboot"
631 depends on X86_32 && X86
633 This enables chipset and/or board specific fixups to be done
634 in order to get reboot to work correctly. This is only needed on
635 some combinations of hardware and BIOS. The symptom, for which
636 this config is intended, is when reboot ends with a stalled/hung
639 Currently, the only fixup is for the Geode machines using
640 CS5530A and CS5536 chipsets.
642 Say Y if you want to enable the fixup. Currently, it's safe to
643 enable this option even if you don't need it.
647 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
650 If you say Y here, you will be able to update the microcode on
651 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
652 Pentium III, Pentium 4, Xeon etc. You will obviously need the
653 actual microcode binary data itself which is not shipped with the
656 For latest news and information on obtaining all the required
657 ingredients for this driver, check:
658 <http://www.urbanmyth.org/microcode/>.
660 To compile this driver as a module, choose M here: the
661 module will be called microcode.
663 config MICROCODE_OLD_INTERFACE
668 tristate "/dev/cpu/*/msr - Model-specific register support"
670 This device gives privileged processes access to the x86
671 Model-Specific Registers (MSRs). It is a character device with
672 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
673 MSR accesses are directed to a specific CPU on multi-processor
677 tristate "/dev/cpu/*/cpuid - CPU information support"
679 This device gives processes access to the x86 CPUID instruction to
680 be executed on a specific processor. It is a character device
681 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
685 prompt "High Memory Support"
686 default HIGHMEM4G if !X86_NUMAQ
687 default HIGHMEM64G if X86_NUMAQ
692 depends on !X86_NUMAQ
694 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
695 However, the address space of 32-bit x86 processors is only 4
696 Gigabytes large. That means that, if you have a large amount of
697 physical memory, not all of it can be "permanently mapped" by the
698 kernel. The physical memory that's not permanently mapped is called
701 If you are compiling a kernel which will never run on a machine with
702 more than 1 Gigabyte total physical RAM, answer "off" here (default
703 choice and suitable for most users). This will result in a "3GB/1GB"
704 split: 3GB are mapped so that each process sees a 3GB virtual memory
705 space and the remaining part of the 4GB virtual memory space is used
706 by the kernel to permanently map as much physical memory as
709 If the machine has between 1 and 4 Gigabytes physical RAM, then
712 If more than 4 Gigabytes is used then answer "64GB" here. This
713 selection turns Intel PAE (Physical Address Extension) mode on.
714 PAE implements 3-level paging on IA32 processors. PAE is fully
715 supported by Linux, PAE mode is implemented on all recent Intel
716 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
717 then the kernel will not boot on CPUs that don't support PAE!
719 The actual amount of total physical memory will either be
720 auto detected or can be forced by using a kernel command line option
721 such as "mem=256M". (Try "man bootparam" or see the documentation of
722 your boot loader (lilo or loadlin) about how to pass options to the
723 kernel at boot time.)
725 If unsure, say "off".
729 depends on !X86_NUMAQ
731 Select this if you have a 32-bit processor and between 1 and 4
732 gigabytes of physical RAM.
736 depends on !M386 && !M486
739 Select this if you have a 32-bit processor and more than 4
740 gigabytes of physical RAM.
745 depends on EXPERIMENTAL
746 prompt "Memory split" if EMBEDDED
750 Select the desired split between kernel and user memory.
752 If the address range available to the kernel is less than the
753 physical memory installed, the remaining memory will be available
754 as "high memory". Accessing high memory is a little more costly
755 than low memory, as it needs to be mapped into the kernel first.
756 Note that increasing the kernel address space limits the range
757 available to user programs, making the address space there
758 tighter. Selecting anything other than the default 3G/1G split
759 will also likely make your kernel incompatible with binary-only
762 If you are not absolutely sure what you are doing, leave this
766 bool "3G/1G user/kernel split"
767 config VMSPLIT_3G_OPT
769 bool "3G/1G user/kernel split (for full 1G low memory)"
771 bool "2G/2G user/kernel split"
772 config VMSPLIT_2G_OPT
774 bool "2G/2G user/kernel split (for full 2G low memory)"
776 bool "1G/3G user/kernel split"
781 default 0xB0000000 if VMSPLIT_3G_OPT
782 default 0x80000000 if VMSPLIT_2G
783 default 0x78000000 if VMSPLIT_2G_OPT
784 default 0x40000000 if VMSPLIT_1G
790 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
794 prompt "PAE (Physical Address Extension) Support"
795 depends on X86_32 && !HIGHMEM4G
796 select RESOURCES_64BIT
798 PAE is required for NX support, and furthermore enables
799 larger swapspace support for non-overcommit purposes. It
800 has the cost of more pagetable lookup overhead, and also
801 consumes more pagetable space per process.
803 # Common NUMA Features
805 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
807 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
809 default y if (X86_NUMAQ || X86_SUMMIT)
811 Enable NUMA (Non Uniform Memory Access) support.
812 The kernel will try to allocate memory used by a CPU on the
813 local memory controller of the CPU and add some more
814 NUMA awareness to the kernel.
816 For i386 this is currently highly experimental and should be only
817 used for kernel development. It might also cause boot failures.
818 For x86_64 this is recommended on all multiprocessor Opteron systems.
819 If the system is EM64T, you should say N unless your system is
822 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
823 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
827 prompt "Old style AMD Opteron NUMA detection"
828 depends on X86_64 && NUMA && PCI
830 Enable K8 NUMA node topology detection. You should say Y here if
831 you have a multi processor AMD K8 system. This uses an old
832 method to read the NUMA configuration directly from the builtin
833 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
834 instead, which also takes priority if both are compiled in.
836 config X86_64_ACPI_NUMA
838 prompt "ACPI NUMA detection"
839 depends on X86_64 && NUMA && ACPI && PCI
842 Enable ACPI SRAT based node topology detection.
845 bool "NUMA emulation"
846 depends on X86_64 && NUMA
848 Enable NUMA emulation. A flat machine will be split
849 into virtual nodes when booted with "numa=fake=N", where N is the
850 number of nodes. This is only useful for debugging.
855 default "6" if X86_64
856 default "4" if X86_NUMAQ
858 depends on NEED_MULTIPLE_NODES
860 config HAVE_ARCH_BOOTMEM_NODE
862 depends on X86_32 && NUMA
864 config ARCH_HAVE_MEMORY_PRESENT
866 depends on X86_32 && DISCONTIGMEM
868 config NEED_NODE_MEMMAP_SIZE
870 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
872 config HAVE_ARCH_ALLOC_REMAP
874 depends on X86_32 && NUMA
876 config ARCH_FLATMEM_ENABLE
878 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
880 config ARCH_DISCONTIGMEM_ENABLE
882 depends on NUMA && X86_32
884 config ARCH_DISCONTIGMEM_DEFAULT
886 depends on NUMA && X86_32
888 config ARCH_SPARSEMEM_DEFAULT
892 config ARCH_SPARSEMEM_ENABLE
894 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
895 select SPARSEMEM_STATIC if X86_32
896 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
898 config ARCH_SELECT_MEMORY_MODEL
900 depends on ARCH_SPARSEMEM_ENABLE
902 config ARCH_MEMORY_PROBE
904 depends on MEMORY_HOTPLUG
909 bool "Allocate 3rd-level pagetables from highmem"
910 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
912 The VM uses one page table entry for each page of physical memory.
913 For systems with a lot of RAM, this can be wasteful of precious
914 low memory. Setting this option will put user-space page table
915 entries in high memory.
917 config MATH_EMULATION
919 prompt "Math emulation" if X86_32
921 Linux can emulate a math coprocessor (used for floating point
922 operations) if you don't have one. 486DX and Pentium processors have
923 a math coprocessor built in, 486SX and 386 do not, unless you added
924 a 487DX or 387, respectively. (The messages during boot time can
925 give you some hints here ["man dmesg"].) Everyone needs either a
926 coprocessor or this emulation.
928 If you don't have a math coprocessor, you need to say Y here; if you
929 say Y here even though you have a coprocessor, the coprocessor will
930 be used nevertheless. (This behavior can be changed with the kernel
931 command line option "no387", which comes handy if your coprocessor
932 is broken. Try "man bootparam" or see the documentation of your boot
933 loader (lilo or loadlin) about how to pass options to the kernel at
934 boot time.) This means that it is a good idea to say Y here if you
935 intend to use this kernel on different machines.
937 More information about the internals of the Linux math coprocessor
938 emulation can be found in <file:arch/x86/math-emu/README>.
940 If you are not sure, say Y; apart from resulting in a 66 KB bigger
941 kernel, it won't hurt.
944 bool "MTRR (Memory Type Range Register) support"
946 On Intel P6 family processors (Pentium Pro, Pentium II and later)
947 the Memory Type Range Registers (MTRRs) may be used to control
948 processor access to memory ranges. This is most useful if you have
949 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
950 allows bus write transfers to be combined into a larger transfer
951 before bursting over the PCI/AGP bus. This can increase performance
952 of image write operations 2.5 times or more. Saying Y here creates a
953 /proc/mtrr file which may be used to manipulate your processor's
954 MTRRs. Typically the X server should use this.
956 This code has a reasonably generic interface so that similar
957 control registers on other processors can be easily supported
960 The Cyrix 6x86, 6x86MX and M II processors have Address Range
961 Registers (ARRs) which provide a similar functionality to MTRRs. For
962 these, the ARRs are used to emulate the MTRRs.
963 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
964 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
965 write-combining. All of these processors are supported by this code
966 and it makes sense to say Y here if you have one of them.
968 Saying Y here also fixes a problem with buggy SMP BIOSes which only
969 set the MTRRs for the boot CPU and not for the secondary CPUs. This
970 can lead to all sorts of problems, so it's good to say Y here.
972 You can safely say Y even if your machine doesn't have MTRRs, you'll
973 just add about 9 KB to your kernel.
975 See <file:Documentation/mtrr.txt> for more information.
979 prompt "EFI runtime service support"
982 This enables the kernel to use EFI runtime services that are
983 available (such as the EFI variable services).
985 This option is only useful on systems that have EFI firmware.
986 In addition, you should use the latest ELILO loader available
987 at <http://elilo.sourceforge.net> in order to take advantage
988 of EFI runtime services. However, even with this option, the
989 resultant kernel should continue to boot on existing non-EFI
994 prompt "Enable kernel irq balancing"
995 depends on X86_32 && SMP && X86_IO_APIC
997 The default yes will allow the kernel to do irq load balancing.
998 Saying no will keep the kernel from doing irq load balancing.
1000 # turning this on wastes a bunch of space.
1001 # Summit needs it only when NUMA is on
1004 depends on X86_32 && (((X86_SUMMIT || X86_GENERICARCH) && NUMA) || (X86 && EFI))
1008 prompt "Enable seccomp to safely compute untrusted bytecode"
1011 This kernel feature is useful for number crunching applications
1012 that may need to compute untrusted bytecode during their
1013 execution. By using pipes or other transports made available to
1014 the process as file descriptors supporting the read/write
1015 syscalls, it's possible to isolate those applications in
1016 their own address space using seccomp. Once seccomp is
1017 enabled via /proc/<pid>/seccomp, it cannot be disabled
1018 and the task is only allowed to execute a few safe syscalls
1019 defined by each seccomp mode.
1021 If unsure, say Y. Only embedded should say N here.
1023 config CC_STACKPROTECTOR
1024 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1025 depends on X86_64 && EXPERIMENTAL
1027 This option turns on the -fstack-protector GCC feature. This
1028 feature puts, at the beginning of critical functions, a canary
1029 value on the stack just before the return address, and validates
1030 the value just before actually returning. Stack based buffer
1031 overflows (that need to overwrite this return address) now also
1032 overwrite the canary, which gets detected and the attack is then
1033 neutralized via a kernel panic.
1035 This feature requires gcc version 4.2 or above, or a distribution
1036 gcc with the feature backported. Older versions are automatically
1037 detected and for those versions, this configuration option is ignored.
1039 config CC_STACKPROTECTOR_ALL
1040 bool "Use stack-protector for all functions"
1041 depends on CC_STACKPROTECTOR
1043 Normally, GCC only inserts the canary value protection for
1044 functions that use large-ish on-stack buffers. By enabling
1045 this option, GCC will be asked to do this for ALL functions.
1047 source kernel/Kconfig.hz
1050 bool "kexec system call"
1052 kexec is a system call that implements the ability to shutdown your
1053 current kernel, and to start another kernel. It is like a reboot
1054 but it is independent of the system firmware. And like a reboot
1055 you can start any kernel with it, not just Linux.
1057 The name comes from the similarity to the exec system call.
1059 It is an ongoing process to be certain the hardware in a machine
1060 is properly shutdown, so do not be surprised if this code does not
1061 initially work for you. It may help to enable device hotplugging
1062 support. As of this writing the exact hardware interface is
1063 strongly in flux, so no good recommendation can be made.
1066 bool "kernel crash dumps (EXPERIMENTAL)"
1067 depends on EXPERIMENTAL
1068 depends on X86_64 || (X86_32 && HIGHMEM)
1070 Generate crash dump after being started by kexec.
1071 This should be normally only set in special crash dump kernels
1072 which are loaded in the main kernel with kexec-tools into
1073 a specially reserved region and then later executed after
1074 a crash by kdump/kexec. The crash dump kernel must be compiled
1075 to a memory address not used by the main kernel or BIOS using
1076 PHYSICAL_START, or it must be built as a relocatable image
1077 (CONFIG_RELOCATABLE=y).
1078 For more details see Documentation/kdump/kdump.txt
1080 config PHYSICAL_START
1081 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1082 default "0x1000000" if X86_NUMAQ
1083 default "0x200000" if X86_64
1086 This gives the physical address where the kernel is loaded.
1088 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1089 bzImage will decompress itself to above physical address and
1090 run from there. Otherwise, bzImage will run from the address where
1091 it has been loaded by the boot loader and will ignore above physical
1094 In normal kdump cases one does not have to set/change this option
1095 as now bzImage can be compiled as a completely relocatable image
1096 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1097 address. This option is mainly useful for the folks who don't want
1098 to use a bzImage for capturing the crash dump and want to use a
1099 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1100 to be specifically compiled to run from a specific memory area
1101 (normally a reserved region) and this option comes handy.
1103 So if you are using bzImage for capturing the crash dump, leave
1104 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1105 Otherwise if you plan to use vmlinux for capturing the crash dump
1106 change this value to start of the reserved region (Typically 16MB
1107 0x1000000). In other words, it can be set based on the "X" value as
1108 specified in the "crashkernel=YM@XM" command line boot parameter
1109 passed to the panic-ed kernel. Typically this parameter is set as
1110 crashkernel=64M@16M. Please take a look at
1111 Documentation/kdump/kdump.txt for more details about crash dumps.
1113 Usage of bzImage for capturing the crash dump is recommended as
1114 one does not have to build two kernels. Same kernel can be used
1115 as production kernel and capture kernel. Above option should have
1116 gone away after relocatable bzImage support is introduced. But it
1117 is present because there are users out there who continue to use
1118 vmlinux for dump capture. This option should go away down the
1121 Don't change this unless you know what you are doing.
1124 bool "Build a relocatable kernel (EXPERIMENTAL)"
1125 depends on EXPERIMENTAL
1127 This builds a kernel image that retains relocation information
1128 so it can be loaded someplace besides the default 1MB.
1129 The relocations tend to make the kernel binary about 10% larger,
1130 but are discarded at runtime.
1132 One use is for the kexec on panic case where the recovery kernel
1133 must live at a different physical address than the primary
1136 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1137 it has been loaded at and the compile time physical address
1138 (CONFIG_PHYSICAL_START) is ignored.
1140 config PHYSICAL_ALIGN
1142 prompt "Alignment value to which kernel should be aligned" if X86_32
1143 default "0x100000" if X86_32
1144 default "0x200000" if X86_64
1145 range 0x2000 0x400000
1147 This value puts the alignment restrictions on physical address
1148 where kernel is loaded and run from. Kernel is compiled for an
1149 address which meets above alignment restriction.
1151 If bootloader loads the kernel at a non-aligned address and
1152 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1153 address aligned to above value and run from there.
1155 If bootloader loads the kernel at a non-aligned address and
1156 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1157 load address and decompress itself to the address it has been
1158 compiled for and run from there. The address for which kernel is
1159 compiled already meets above alignment restrictions. Hence the
1160 end result is that kernel runs from a physical address meeting
1161 above alignment restrictions.
1163 Don't change this unless you know what you are doing.
1166 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1167 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1169 Say Y here to experiment with turning CPUs off and on, and to
1170 enable suspend on SMP systems. CPUs can be controlled through
1171 /sys/devices/system/cpu.
1172 Say N if you want to disable CPU hotplug and don't need to
1177 prompt "Compat VDSO support"
1178 depends on X86_32 || IA32_EMULATION
1180 Map the 32-bit VDSO to the predictable old-style address too.
1182 Say N here if you are running a sufficiently recent glibc
1183 version (2.3.3 or later), to remove the high-mapped
1184 VDSO mapping and to exclusively use the randomized VDSO.
1190 config ARCH_ENABLE_MEMORY_HOTPLUG
1192 depends on X86_64 || (X86_32 && HIGHMEM)
1194 config HAVE_ARCH_EARLY_PFN_TO_NID
1198 menu "Power management options"
1199 depends on !X86_VOYAGER
1201 config ARCH_HIBERNATION_HEADER
1203 depends on X86_64 && HIBERNATION
1205 source "kernel/power/Kconfig"
1207 source "drivers/acpi/Kconfig"
1212 depends on APM || APM_MODULE
1215 tristate "APM (Advanced Power Management) BIOS support"
1216 depends on X86_32 && PM_SLEEP && !X86_VISWS
1218 APM is a BIOS specification for saving power using several different
1219 techniques. This is mostly useful for battery powered laptops with
1220 APM compliant BIOSes. If you say Y here, the system time will be
1221 reset after a RESUME operation, the /proc/apm device will provide
1222 battery status information, and user-space programs will receive
1223 notification of APM "events" (e.g. battery status change).
1225 If you select "Y" here, you can disable actual use of the APM
1226 BIOS by passing the "apm=off" option to the kernel at boot time.
1228 Note that the APM support is almost completely disabled for
1229 machines with more than one CPU.
1231 In order to use APM, you will need supporting software. For location
1232 and more information, read <file:Documentation/pm.txt> and the
1233 Battery Powered Linux mini-HOWTO, available from
1234 <http://www.tldp.org/docs.html#howto>.
1236 This driver does not spin down disk drives (see the hdparm(8)
1237 manpage ("man 8 hdparm") for that), and it doesn't turn off
1238 VESA-compliant "green" monitors.
1240 This driver does not support the TI 4000M TravelMate and the ACER
1241 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1242 desktop machines also don't have compliant BIOSes, and this driver
1243 may cause those machines to panic during the boot phase.
1245 Generally, if you don't have a battery in your machine, there isn't
1246 much point in using this driver and you should say N. If you get
1247 random kernel OOPSes or reboots that don't seem to be related to
1248 anything, try disabling/enabling this option (or disabling/enabling
1251 Some other things you should try when experiencing seemingly random,
1254 1) make sure that you have enough swap space and that it is
1256 2) pass the "no-hlt" option to the kernel
1257 3) switch on floating point emulation in the kernel and pass
1258 the "no387" option to the kernel
1259 4) pass the "floppy=nodma" option to the kernel
1260 5) pass the "mem=4M" option to the kernel (thereby disabling
1261 all but the first 4 MB of RAM)
1262 6) make sure that the CPU is not over clocked.
1263 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1264 8) disable the cache from your BIOS settings
1265 9) install a fan for the video card or exchange video RAM
1266 10) install a better fan for the CPU
1267 11) exchange RAM chips
1268 12) exchange the motherboard.
1270 To compile this driver as a module, choose M here: the
1271 module will be called apm.
1275 config APM_IGNORE_USER_SUSPEND
1276 bool "Ignore USER SUSPEND"
1278 This option will ignore USER SUSPEND requests. On machines with a
1279 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1280 series notebooks, it is necessary to say Y because of a BIOS bug.
1282 config APM_DO_ENABLE
1283 bool "Enable PM at boot time"
1285 Enable APM features at boot time. From page 36 of the APM BIOS
1286 specification: "When disabled, the APM BIOS does not automatically
1287 power manage devices, enter the Standby State, enter the Suspend
1288 State, or take power saving steps in response to CPU Idle calls."
1289 This driver will make CPU Idle calls when Linux is idle (unless this
1290 feature is turned off -- see "Do CPU IDLE calls", below). This
1291 should always save battery power, but more complicated APM features
1292 will be dependent on your BIOS implementation. You may need to turn
1293 this option off if your computer hangs at boot time when using APM
1294 support, or if it beeps continuously instead of suspending. Turn
1295 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1296 T400CDT. This is off by default since most machines do fine without
1300 bool "Make CPU Idle calls when idle"
1302 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1303 On some machines, this can activate improved power savings, such as
1304 a slowed CPU clock rate, when the machine is idle. These idle calls
1305 are made after the idle loop has run for some length of time (e.g.,
1306 333 mS). On some machines, this will cause a hang at boot time or
1307 whenever the CPU becomes idle. (On machines with more than one CPU,
1308 this option does nothing.)
1310 config APM_DISPLAY_BLANK
1311 bool "Enable console blanking using APM"
1313 Enable console blanking using the APM. Some laptops can use this to
1314 turn off the LCD backlight when the screen blanker of the Linux
1315 virtual console blanks the screen. Note that this is only used by
1316 the virtual console screen blanker, and won't turn off the backlight
1317 when using the X Window system. This also doesn't have anything to
1318 do with your VESA-compliant power-saving monitor. Further, this
1319 option doesn't work for all laptops -- it might not turn off your
1320 backlight at all, or it might print a lot of errors to the console,
1321 especially if you are using gpm.
1323 config APM_ALLOW_INTS
1324 bool "Allow interrupts during APM BIOS calls"
1326 Normally we disable external interrupts while we are making calls to
1327 the APM BIOS as a measure to lessen the effects of a badly behaving
1328 BIOS implementation. The BIOS should reenable interrupts if it
1329 needs to. Unfortunately, some BIOSes do not -- especially those in
1330 many of the newer IBM Thinkpads. If you experience hangs when you
1331 suspend, try setting this to Y. Otherwise, say N.
1333 config APM_REAL_MODE_POWER_OFF
1334 bool "Use real mode APM BIOS call to power off"
1336 Use real mode APM BIOS calls to switch off the computer. This is
1337 a work-around for a number of buggy BIOSes. Switch this option on if
1338 your computer crashes instead of powering off properly.
1342 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1344 source "drivers/cpuidle/Kconfig"
1349 menu "Bus options (PCI etc.)"
1352 bool "PCI support" if !X86_VISWS
1353 depends on !X86_VOYAGER
1355 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1357 Find out whether you have a PCI motherboard. PCI is the name of a
1358 bus system, i.e. the way the CPU talks to the other stuff inside
1359 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1360 VESA. If you have PCI, say Y, otherwise N.
1362 The PCI-HOWTO, available from
1363 <http://www.tldp.org/docs.html#howto>, contains valuable
1364 information about which PCI hardware does work under Linux and which
1368 prompt "PCI access mode"
1369 depends on X86_32 && PCI && !X86_VISWS
1372 On PCI systems, the BIOS can be used to detect the PCI devices and
1373 determine their configuration. However, some old PCI motherboards
1374 have BIOS bugs and may crash if this is done. Also, some embedded
1375 PCI-based systems don't have any BIOS at all. Linux can also try to
1376 detect the PCI hardware directly without using the BIOS.
1378 With this option, you can specify how Linux should detect the
1379 PCI devices. If you choose "BIOS", the BIOS will be used,
1380 if you choose "Direct", the BIOS won't be used, and if you
1381 choose "MMConfig", then PCI Express MMCONFIG will be used.
1382 If you choose "Any", the kernel will try MMCONFIG, then the
1383 direct access method and falls back to the BIOS if that doesn't
1384 work. If unsure, go with the default, which is "Any".
1389 config PCI_GOMMCONFIG
1402 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1404 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1407 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1411 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1418 bool "Support mmconfig PCI config space access"
1419 depends on X86_64 && PCI && ACPI
1422 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1423 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1425 DMA remapping (DMAR) devices support enables independent address
1426 translations for Direct Memory Access (DMA) from devices.
1427 These DMA remapping devices are reported via ACPI tables
1428 and include PCI device scope covered by these DMA
1433 prompt "Support for Graphics workaround"
1436 Current Graphics drivers tend to use physical address
1437 for DMA and avoid using DMA APIs. Setting this config
1438 option permits the IOMMU driver to set a unity map for
1439 all the OS-visible memory. Hence the driver can continue
1440 to use physical addresses for DMA.
1442 config DMAR_FLOPPY_WA
1446 Floppy disk drivers are know to bypass DMA API calls
1447 thereby failing to work when IOMMU is enabled. This
1448 workaround will setup a 1:1 mapping for the first
1449 16M to make floppy (an ISA device) work.
1451 source "drivers/pci/pcie/Kconfig"
1453 source "drivers/pci/Kconfig"
1455 # x86_64 have no ISA slots, but do have ISA-style DMA.
1463 depends on !(X86_VOYAGER || X86_VISWS)
1465 Find out whether you have ISA slots on your motherboard. ISA is the
1466 name of a bus system, i.e. the way the CPU talks to the other stuff
1467 inside your box. Other bus systems are PCI, EISA, MicroChannel
1468 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1469 newer boards don't support it. If you have ISA, say Y, otherwise N.
1475 The Extended Industry Standard Architecture (EISA) bus was
1476 developed as an open alternative to the IBM MicroChannel bus.
1478 The EISA bus provided some of the features of the IBM MicroChannel
1479 bus while maintaining backward compatibility with cards made for
1480 the older ISA bus. The EISA bus saw limited use between 1988 and
1481 1995 when it was made obsolete by the PCI bus.
1483 Say Y here if you are building a kernel for an EISA-based machine.
1487 source "drivers/eisa/Kconfig"
1490 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1491 default y if X86_VOYAGER
1493 MicroChannel Architecture is found in some IBM PS/2 machines and
1494 laptops. It is a bus system similar to PCI or ISA. See
1495 <file:Documentation/mca.txt> (and especially the web page given
1496 there) before attempting to build an MCA bus kernel.
1498 source "drivers/mca/Kconfig"
1501 tristate "NatSemi SCx200 support"
1502 depends on !X86_VOYAGER
1504 This provides basic support for National Semiconductor's
1505 (now AMD's) Geode processors. The driver probes for the
1506 PCI-IDs of several on-chip devices, so its a good dependency
1507 for other scx200_* drivers.
1509 If compiled as a module, the driver is named scx200.
1511 config SCx200HR_TIMER
1512 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1513 depends on SCx200 && GENERIC_TIME
1516 This driver provides a clocksource built upon the on-chip
1517 27MHz high-resolution timer. Its also a workaround for
1518 NSC Geode SC-1100's buggy TSC, which loses time when the
1519 processor goes idle (as is done by the scheduler). The
1520 other workaround is idle=poll boot option.
1522 config GEODE_MFGPT_TIMER
1524 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1525 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1527 This driver provides a clock event source based on the MFGPT
1528 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1529 MFGPTs have a better resolution and max interval than the
1530 generic PIT, and are suitable for use as high-res timers.
1536 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1538 source "drivers/pcmcia/Kconfig"
1540 source "drivers/pci/hotplug/Kconfig"
1545 menu "Executable file formats / Emulations"
1547 source "fs/Kconfig.binfmt"
1549 config IA32_EMULATION
1550 bool "IA32 Emulation"
1552 select COMPAT_BINFMT_ELF
1554 Include code to run 32-bit programs under a 64-bit kernel. You should
1555 likely turn this on, unless you're 100% sure that you don't have any
1556 32-bit programs left.
1559 tristate "IA32 a.out support"
1560 depends on IA32_EMULATION
1562 Support old a.out binaries in the 32bit emulation.
1566 depends on IA32_EMULATION
1568 config COMPAT_FOR_U64_ALIGNMENT
1572 config SYSVIPC_COMPAT
1574 depends on X86_64 && COMPAT && SYSVIPC
1579 source "net/Kconfig"
1581 source "drivers/Kconfig"
1583 source "drivers/firmware/Kconfig"
1587 source "kernel/Kconfig.instrumentation"
1589 source "arch/x86/Kconfig.debug"
1591 source "security/Kconfig"
1593 source "crypto/Kconfig"
1595 source "lib/Kconfig"
projects / linux-2.6-omap-h63xx.git / blob