kconfig

来自「linux 内核源代码」· 代码 · 共 674 行 · 第 1/2 页

TXT
674
字号
config ALPHA_NONAME	bool	depends on ALPHA_BOOK1 || ALPHA_NONAME_CH	default y	help	  The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia	  UDB).  This design was produced by Digital's Technical OEM (TOEM)	  group. It uses the 21066 processor running at 166MHz or 233MHz. It	  is a baby-AT size, and runs from a standard PC power supply. It has	  5 ISA slots and 3 PCI slots (one pair are a shared slot). There are	  2 versions, with either PS/2 or large DIN connectors for the	  keyboard.config ALPHA_EV4	bool	depends on ALPHA_JENSEN || (ALPHA_SABLE && !ALPHA_GAMMA) || ALPHA_LYNX || ALPHA_NORITAKE && !ALPHA_PRIMO || ALPHA_MIKASA && !ALPHA_PRIMO || ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P_CH || ALPHA_XL || ALPHA_NONAME || ALPHA_EB66 || ALPHA_EB66P || ALPHA_P2K	default y if !ALPHA_LYNXconfig ALPHA_LCA	bool	depends on ALPHA_NONAME || ALPHA_EB66 || ALPHA_EB66P || ALPHA_P2K	default yconfig ALPHA_APECS	bool	depends on !ALPHA_PRIMO && (ALPHA_NORITAKE || ALPHA_MIKASA) || ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P_CH || ALPHA_XL	default yconfig ALPHA_EB64P	bool	depends on ALPHA_CABRIOLET || ALPHA_EB64P_CH	default y	help	  Uses 21064 or 21064A and APECs.  Has ISA and PCI expansion (3 ISA,	  2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.	  ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI	  (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),	  SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM.  PC-AT size.	  Runs from standard PC power supply.config ALPHA_EV5	bool "EV5 CPU(s) (model 5/xxx)?" if ALPHA_LYNX	default y if ALPHA_RX164 || ALPHA_RAWHIDE || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_SABLE && ALPHA_GAMMA || ALPHA_NORITAKE && ALPHA_PRIMO || ALPHA_MIKASA && ALPHA_PRIMO || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCORconfig ALPHA_EV4	bool	default y if ALPHA_LYNX && !ALPHA_EV5config ALPHA_CIA	bool	depends on ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_NORITAKE && ALPHA_PRIMO || ALPHA_MIKASA && ALPHA_PRIMO || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR	default yconfig ALPHA_EV56	bool "EV56 CPU (speed >= 366MHz)?" if ALPHA_ALCOR	default y if ALPHA_RX164 || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_PC164 || ALPHA_TAKARAconfig ALPHA_EV56	prompt "EV56 CPU (speed >= 333MHz)?"	depends on ALPHA_NORITAKE || ALPHA_PRIMOconfig ALPHA_EV56	prompt "EV56 CPU (speed >= 400MHz)?"	depends on ALPHA_RAWHIDEconfig ALPHA_PRIMO	bool "EV5 CPU daughtercard (model 5/xxx)?"	depends on ALPHA_NORITAKE || ALPHA_MIKASA	help	  Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.config ALPHA_GAMMA	bool "EV5 CPU(s) (model 5/xxx)?"	depends on ALPHA_SABLE	help	  Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.config ALPHA_GAMMA	bool	depends on ALPHA_LYNX	default yconfig ALPHA_T2	bool	depends on ALPHA_SABLE || ALPHA_LYNX	default yconfig ALPHA_PYXIS	bool	depends on ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN	default yconfig ALPHA_EV6	bool	depends on ALPHA_NAUTILUS || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_DP264 || ALPHA_EIGER || ALPHA_MARVEL	default yconfig ALPHA_TSUNAMI	bool	depends on ALPHA_SHARK || ALPHA_DP264 || ALPHA_EIGER	default yconfig ALPHA_EV67	bool "EV67 (or later) CPU (speed > 600MHz)?" if ALPHA_DP264 || ALPHA_EIGER	default y if ALPHA_NAUTILUS || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_MARVEL	help	  Is this a machine based on the EV67 core?  If in doubt, select N here	  and the machine will be treated as an EV6.config ALPHA_EV7	bool	depends on ALPHA_MARVEL	default yconfig ALPHA_MCPCIA	bool	depends on ALPHA_RAWHIDE	default yconfig ALPHA_POLARIS	bool	depends on ALPHA_RX164	default yconfig ALPHA_IRONGATE	bool	depends on ALPHA_NAUTILUS	default yconfig GENERIC_HWEIGHT	bool	default y if !ALPHA_EV67config ALPHA_AVANTI	bool	depends on ALPHA_XL || ALPHA_AVANTI_CH	default y	help	  Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based	  Alphas. Info at	  <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.config ALPHA_BROKEN_IRQ_MASK	bool	depends on ALPHA_GENERIC || ALPHA_PC164	default yconfig VGA_HOSE	bool	depends on ALPHA_GENERIC || ALPHA_TITAN || ALPHA_MARVEL || ALPHA_TSUNAMI	default y	help	  Support VGA on an arbitrary hose; needed for several platforms	  which always have multiple hoses, and whose consoles support it.config ALPHA_SRM	bool "Use SRM as bootloader" if ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_NAUTILUS || ALPHA_NONAME	default y if ALPHA_JENSEN || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_LYNX || ALPHA_NORITAKE || ALPHA_DP264 || ALPHA_RAWHIDE || ALPHA_EIGER || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_MARVEL	---help---	  There are two different types of booting firmware on Alphas: SRM,	  which is command line driven, and ARC, which uses menus and arrow	  keys. Details about the Linux/Alpha booting process are contained in	  the Linux/Alpha FAQ, accessible on the WWW from	  <http://www.alphalinux.org/>.	  The usual way to load Linux on an Alpha machine is to use MILO	  (a bootloader that lets you pass command line parameters to the	  kernel just like lilo does for the x86 architecture) which can be	  loaded either from ARC or can be installed directly as a permanent	  firmware replacement from floppy (which requires changing a certain	  jumper on the motherboard). If you want to do either of these, say N	  here. If MILO doesn't work on your system (true for Jensen	  motherboards), you can bypass it altogether and boot Linux directly	  from an SRM console; say Y here in order to do that. Note that you	  won't be able to boot from an IDE disk using SRM.	  If unsure, say N.config EISA	bool	depends on ALPHA_GENERIC || ALPHA_JENSEN || ALPHA_ALCOR || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_LYNX || ALPHA_NORITAKE || ALPHA_RAWHIDE	default yconfig ARCH_MAY_HAVE_PC_FDC	def_bool yconfig SMP	bool "Symmetric multi-processing support"	depends on ALPHA_SABLE || ALPHA_LYNX || ALPHA_RAWHIDE || ALPHA_DP264 || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_GENERIC || ALPHA_SHARK || ALPHA_MARVEL	---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.	  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 HAVE_DEC_LOCK	bool	depends on SMP	default yconfig NR_CPUS	int "Maximum number of CPUs (2-32)"	range 2 32	depends on SMP	default "32" if ALPHA_GENERIC || ALPHA_MARVEL	default "4" if !ALPHA_GENERIC && !ALPHA_MARVEL	help	  MARVEL support can handle a maximum of 32 CPUs, all the others          with working support have a maximum of 4 CPUs.config ARCH_DISCONTIGMEM_ENABLE	bool "Discontiguous Memory Support (EXPERIMENTAL)"	depends on EXPERIMENTAL	help	  Say Y to support efficient handling of discontiguous physical memory,	  for architectures which are either NUMA (Non-Uniform Memory Access)	  or have huge holes in the physical address space for other reasons.	  See <file:Documentation/vm/numa> for more.source "mm/Kconfig"config NUMA	bool "NUMA Support (EXPERIMENTAL)"	depends on DISCONTIGMEM && BROKEN	help	  Say Y to compile the kernel to support NUMA (Non-Uniform Memory	  Access).  This option is for configuring high-end multiprocessor	  server machines.  If in doubt, say N.config NODES_SHIFT	int	default "7"	depends on NEED_MULTIPLE_NODES# LARGE_VMALLOC is racy, if you *really* need it then fix it firstconfig ALPHA_LARGE_VMALLOC	bool	---help---	  Process creation and other aspects of virtual memory management can	  be streamlined if we restrict the kernel to one PGD for all vmalloc	  allocations.  This equates to about 8GB.	  Under normal circumstances, this is so far and above what is needed	  as to be laughable.  However, there are certain applications (such	  as benchmark-grade in-kernel web serving) that can make use of as	  much vmalloc space as is available.	  Say N unless you know you need gobs and gobs of vmalloc space.config VERBOSE_MCHECK	bool "Verbose Machine Checks"config VERBOSE_MCHECK_ON	int "Verbose Printing Mode (0=off, 1=on, 2=all)"	depends on VERBOSE_MCHECK	default 1	---help---	  This option allows the default printing mode to be set, and then	  possibly overridden by a boot command argument.	  For example, if one wanted the option of printing verbose	  machine checks, but wanted the default to be as if verbose	  machine check printing was turned off, then one would choose	  the printing mode to be 0. Then, upon reboot, one could add	  the boot command line "verbose_mcheck=1" to get the normal	  verbose machine check printing, or "verbose_mcheck=2" to get	  the maximum information available.	  Take the default (1) unless you want more control or more info.source "drivers/pci/Kconfig"source "drivers/eisa/Kconfig"source "drivers/pcmcia/Kconfig"config SRM_ENV	tristate "SRM environment through procfs"	depends on PROC_FS	---help---	  If you enable this option, a subdirectory inside /proc called	  /proc/srm_environment will give you access to the all important	  SRM environment variables (those which have a name) and also	  to all others (by their internal number).	  SRM is something like a BIOS for Alpha machines. There are some	  other such BIOSes, like AlphaBIOS, which this driver cannot	  support (hey, that's not SRM!).	  Despite the fact that this driver doesn't work on all Alphas (but	  only on those which have SRM as their firmware), it's save to	  build it even if your particular machine doesn't know about SRM	  (or if you intend to compile a generic kernel). It will simply	  not create those subdirectory in /proc (and give you some warning,	  of course).	  This driver is also available as a module and will be called	  srm_env then.source "fs/Kconfig.binfmt"endmenusource "net/Kconfig"source "drivers/Kconfig"source "fs/Kconfig"source "kernel/Kconfig.instrumentation"source "arch/alpha/Kconfig.debug"# DUMMY_CONSOLE may be defined in drivers/video/console/Kconfig# but we also need it if VGA_HOSE is setconfig DUMMY_CONSOLE	bool	depends on VGA_HOSE	default ysource "security/Kconfig"source "crypto/Kconfig"source "lib/Kconfig"

⌨️ 快捷键说明

复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?