kconfig
来自「Linux Kernel 2.6.9 for OMAP1710」· 代码 · 共 1,566 行 · 第 1/3 页
TXT
1,566 行
bool depends on NEC_OSPREY default yconfig ARC_CONSOLE bool "ARC console support" depends on SGI_IP22 || SNI_RM200_PCIconfig ARC_MEMORY bool depends on MACH_JAZZ || SNI_RM200_PCI || SGI_IP32 default yconfig ARC_PROMLIB bool depends on MACH_JAZZ || SNI_RM200_PCI || SGI_IP22 || SGI_IP32 default yconfig ARC64 bool depends on SGI_IP27 default yconfig BOOT_ELF64 bool depends on SGI_IP27 default y#config MAPPED_PCI_IO y# bool# depends on SGI_IP27# default yconfig QL_ISP_A64 bool depends on SGI_IP27 default yconfig TOSHIBA_BOARDS bool depends on TOSHIBA_JMR3927 || TOSHIBA_RBTX4927 default yconfig TANBAC_TB0219 bool "Added TANBAC TB0219 Base board support" depends on TANBAC_TB0229endmenumenu "CPU selection"choice prompt "CPU type" default CPU_R4X00config CPU_MIPS32 bool "MIPS32"config CPU_MIPS64 bool "MIPS64"config CPU_R3000 bool "R3000" depends on MIPS32 help Please make sure to pick the right CPU type. Linux/MIPS is not designed to be generic, i.e. Kernels compiled for R3000 CPUs will *not* work on R4000 machines and vice versa. However, since most of the supported machines have an R4000 (or similar) CPU, R4x00 might be a safe bet. If the resulting kernel does not work, try to recompile with R3000.config CPU_TX39XX bool "R39XX" depends on MIPS32config CPU_VR41XX bool "R41xx" help The options selects support for the NEC VR41xx series of processors. Only choose this option if you have one of these processors as a kernel built with this option will not run on any other type of processor or vice versa.config CPU_R4300 bool "R4300" help MIPS Technologies R4300-series processors.config CPU_R4X00 bool "R4x00" help MIPS Technologies R4000-series processors other than 4300, including the R4000, R4400, R4600, and 4700.config CPU_TX49XX bool "R49XX"config CPU_R5000 bool "R5000" help MIPS Technologies R5000-series processors other than the Nevada.config CPU_R5432 bool "R5432"config CPU_R6000 bool "R6000" depends on MIPS32 && EXPERIMENTAL help MIPS Technologies R6000 and R6000A series processors. Note these processors are extremly rare and the support for them is incomplete.config CPU_NEVADA bool "R52xx" help MIPS Technologies R52x0-series ("Nevada") processors.config CPU_R8000 bool "R8000" depends on MIPS64 && EXPERIMENTAL help MIPS Technologies R8000 processors. Note these processors are uncommon and the support for them is incomplete.config CPU_R10000 bool "R10000" help MIPS Technologies R10000-series processors.config CPU_RM7000 bool "RM7000"config CPU_RM9000 bool "RM9000"config CPU_SB1 bool "SB1"endchoicechoice prompt "Kernel page size" default PAGE_SIZE_4KBconfig PAGE_SIZE_4KB bool "4kB" help This option select the standard 4kB Linux page size. On some R3000-family processors this is the only available page size. Using 4kB page size will minimize memory consumption and is therefore recommended for low memory systems.config PAGE_SIZE_8KB bool "8kB" depends on EXPERIMENTAL && CPU_R8000 help Using 8kB page size will result in higher performance kernel at the price of higher memory consumption. This option is available only on the R8000 processor. Not that at the time of this writing this option is still high experimental; there are also issues with compatibility of user applications.config PAGE_SIZE_16KB bool "16kB" depends on EXPERIMENTAL && !CPU_R3000 && !CPU_TX39XX help Using 16kB page size will result in higher performance kernel at the price of higher memory consumption. This option is available on all non-R3000 family processor. Not that at the time of this writing this option is still high experimental; there are also issues with compatibility of user applications.config PAGE_SIZE_64KB bool "64kB" depends on EXPERIMENTAL && !CPU_R3000 && !CPU_TX39XX help Using 64kB page size will result in higher performance kernel at the price of higher memory consumption. This option is available on all non-R3000 family processor. Not that at the time of this writing this option is still high experimental; there are also issues with compatibility of user applications.endchoiceconfig BOARD_SCACHE boolconfig IP22_CPU_SCACHE bool select BOARD_SCACHEconfig R5000_CPU_SCACHE bool select BOARD_SCACHEconfig RM7000_CPU_SCACHE bool select BOARD_SCACHEconfig SIBYTE_DMA_PAGEOPS bool "Use DMA to clear/copy pages" depends on CPU_SB1 help Instead of using the CPU to zero and copy pages, use a Data Mover channel. These DMA channels are otherwise unused by the standard SiByte Linux port. Seems to give a small performance benefit.config CPU_HAS_PREFETCH bool "Enable prefetches" if CPU_SB1 && !CPU_SB1_PASS_2 default y if CPU_MIPS32 || CPU_MIPS64 || CPU_RM7000 || CPU_RM9000 || CPU_R10000config VTAG_ICACHE bool "Support for Virtual Tagged I-cache" if CPU_MIPS64 || CPU_MIPS32 default y if CPU_SB1config SB1_PASS_1_WORKAROUNDS bool depends on CPU_SB1_PASS_1 default yconfig SB1_PASS_2_WORKAROUNDS bool depends on CPU_SB1 && (CPU_SB1_PASS_2_2 || CPU_SB1_PASS_2) default yconfig SB1_PASS_2_1_WORKAROUNDS bool depends on CPU_SB1 && CPU_SB1_PASS_2 default yconfig 64BIT_PHYS_ADDR bool "Support for 64-bit physical address space" depends on (CPU_R4X00 || CPU_R5000 || CPU_RM7000 || CPU_RM9000 || CPU_R10000 || CPU_SB1 || CPU_MIPS32 || CPU_MIPS64) && MIPS32config CPU_ADVANCED bool "Override CPU Options" depends on MIPS32 help Saying yes here allows you to select support for various features your CPU may or may not have. Most people should say N here.config CPU_HAS_LLSC bool "ll/sc Instructions available" if CPU_ADVANCED default y if !CPU_ADVANCED && !CPU_R3000 && !CPU_VR41XX && !CPU_TX39XX help MIPS R4000 series and later provide the Load Linked (ll) and Store Conditional (sc) instructions. More information is available at <http://www.go-ecs.com/mips/miptek1.htm>. Say Y here if your CPU has the ll and sc instructions. Say Y here for better performance, N if you don't know. You must say Y here for multiprocessor machines.config CPU_HAS_LLDSCD bool "lld/scd Instructions available" if CPU_ADVANCED default y if !CPU_ADVANCED && !CPU_R3000 && !CPU_VR41XX && !CPU_TX39XX && !CPU_MIPS32 help Say Y here if your CPU has the lld and scd instructions, the 64-bit equivalents of ll and sc. Say Y here for better performance, N if you don't know. You must say Y here for multiprocessor machines.config CPU_HAS_WB bool "Writeback Buffer available" if CPU_ADVANCED default y if !CPU_ADVANCED && CPU_R3000 && MACH_DECSTATION help Say N here for slightly better performance. You must say Y here for machines which require flushing of write buffers in software. Saying Y is the safe option; N may result in kernel malfunction and crashes.config CPU_HAS_SYNC bool depends on !CPU_R3000 default y## - Highmem only makes sense for the 32-bit kernel.# - The current highmem code will only work properly on physically indexed# caches such as R3000, SB1, R7000 or those that look like they're virtually# indexed such as R4000/R4400 SC and MC versions or R10000. So for the# moment we protect the user and offer the highmem option only on machines# where it's known to be safe. This will not offer highmem on a few systems# such as MIPS32 and MIPS64 CPUs which may have virtual and physically# indexed CPUs but we're playing safe.# - We should not offer highmem for system of which we already know that they# don't have memory configurations that could gain from highmem support in# the kernel because they don't support configurations with RAM at physical# addresses > 0x20000000.#config HIGHMEM bool "High Memory Support" depends on MIPS32 && (CPU_R3000 || CPU_SB1 || CPU_R7000 || CPU_RM9000 || CPU_R10000) && !(BAGET_MIPS || MACH_DECSTATION || MOMENCO_JAGUAR_ATX)config SMP bool "Multi-Processing support" depends on CPU_RM9000 || (SIBYTE_SB1250 && !SIBYTE_STANDALONE) || SGI_IP27 ---help--- This enables support for systems with more than one CPU. If you have a system with only one CPU, like most personal computers, say N. If you have a system with more than one CPU, say Y. If you say N here, the kernel will run on single and multiprocessor machines, but will use only one CPU of a multiprocessor machine. If you say Y here, the kernel will run on many, but not all, singleprocessor machines. On a singleprocessor machine, the kernel will run faster if you say N here. People using multiprocessor machines who say Y here should also say Y to "Enhanced Real Time Clock Support", below. See also the <file:Documentation/smp.txt> and the SMP-HOWTO available at <http://www.tldp.org/docs.html#howto>. If you don't know what to do here, say N.config NR_CPUS int "Maximum number of CPUs (2-64)" range 2 64 depends on SMP default "64" if SGI_IP27 default "2" help This allows you to specify the maximum number of CPUs which this kernel will support. The maximum supported value is 32 for 32-bit kernel and 64 for 64-bit kernels; the minimum value which makes sense is 2. This is purely to save memory - each supported CPU adds approximately eight kilobytes to the kernel image.config PREEMPT bool "Preemptible Kernel" help This option reduces the latency of the kernel when reacting to real-time or interactive events by allowing a low priority process to be preempted even if it is in kernel mode executing a system call. This allows applications to run more reliably even when the system is under load.config RTC_DS1742 bool "DS1742 BRAM/RTC support" depends on TOSHIBA_JMR3927 || TOSHIBA_RBTX4927config MIPS_INSANE_LARGE bool "Support for large 64-bit configurations" depends on CPU_R10000 && MIPS64 help MIPS R10000 does support a 44 bit / 16TB address space as opposed to previous 64-bit processors which only supported 40 bit / 1TB. If you need processes of more than 1TB virtual address space, say Y here. This will result in additional memory usage, so it is not recommended for normal users.config RWSEM_GENERIC_SPINLOCK bool default yendmenumenu "Bus options (PCI, PCMCIA, EISA, ISA, TC)"config HW_HAS_PCI boolconfig PCI bool "Support for PCI controller" depends on HW_HAS_PCI help Find out whether you have a PCI motherboard. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. Other bus systems are ISA, EISA, or VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available from <http://www.tldp.org/docs.html#howto>, contains valuable information about which PCI hardware does work under Linux and which doesn't.source "drivers/pci/Kconfig"## ISA support is now enabled via select. Too many systems still have the one# or other ISA chip on the board that users don't know about so don't expect# users to choose the right thing ...#config ISA boolconfig EISA bool "EISA support" depends on SGI_IP22 || SNI_RM200_PCI select ISA ---help--- The Extended Industry Standard Architecture (EISA) bus was developed as an open alternative to the IBM MicroChannel bus. The EISA bus provided some of the features of the IBM MicroChannel bus while maintaining backward compatibility with cards made for the older ISA bus. The EISA bus saw limited use between 1988 and 1995 when it was made obsolete by the PCI bus. Say Y here if you are building a kernel for an EISA-based machine. Otherwise, say N.source "drivers/eisa/Kconfig"config TC bool "TURBOchannel support" depends on MACH_DECSTATION help TurboChannel is a DEC (now Compaq (now HP)) bus for Alpha and MIPS processors. Documentation on writing device drivers for TurboChannel is available at: <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.#config ACCESSBUS# bool "Access.Bus support"# depends on TCconfig MMU bool default yconfig MCA boolconfig SBUS boolsource "drivers/pcmcia/Kconfig"source "drivers/pci/hotplug/Kconfig"endmenumenu "Executable file formats"source "fs/Kconfig.binfmt"config TRAD_SIGNALS bool default y if MIPS32config BINFMT_IRIX bool "Include IRIX binary compatibility" depends on !CPU_LITTLE_ENDIAN && MIPS32config MIPS32_COMPAT bool "Kernel support for Linux/MIPS 32-bit binary compatibility" depends on MIPS64 help Select this option if you want Linux/MIPS 32-bit binary compatibility. Since all software available for Linux/MIPS is currently 32-bit you should say Y here.config COMPAT bool depends on MIPS32_COMPAT default yconfig MIPS32_O32 bool "Kernel support for o32 binaries" depends on MIPS32_COMPAT help Select this option if you want to run o32 binaries. These are pure 32-bit binaries as used by the 32-bit Linux/MIPS port. Most of existing binaries are in this format. If unsure, say Y.config MIPS32_N32 bool "Kernel support for n32 binaries" depends on MIPS32_COMPAT help Select this option if you want to run n32 binaries. These are 64-bit binaries using 32-bit quantities for addressing and certain data that would normally be 64-bit. They are used in special cases. If unsure, say N.config BINFMT_ELF32 bool default y if MIPS32_O32 || MIPS32_N32config PM bool "Power Management support (EXPERIMENTAL)" depends on EXPERIMENTAL && MACH_AU1X00endmenumenu "MIPS initrd options" depends on BLK_DEV_INITRDconfig EMBEDDED_RAMDISK bool "Embed root filesystem ramdisk into the kernel"config EMBEDDED_RAMDISK_IMAGE string "Filename of gziped ramdisk image" depends on EMBEDDED_RAMDISK default "ramdisk.gz" help This is the filename of the ramdisk image to be built into the kernel. Relative pathnames are relative to arch/mips/ramdisk/. The ramdisk image is not part of the kernel distribution; you must provide one yourself.endmenusource "drivers/Kconfig"source "fs/Kconfig"source "arch/mips/Kconfig.debug"source "security/Kconfig"source "crypto/Kconfig"source "lib/Kconfig"⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?