kconfig

来自「linux 内核源代码」· 代码 · 共 1,739 行 · 第 1/5 页

TXT
1,739
字号
menu "SCSI device support"config RAID_ATTRS	tristate "RAID Transport Class"	default n	depends on BLOCK	---help---	  Provides RAIDconfig SCSI	tristate "SCSI device support"	depends on BLOCK	select SCSI_DMA if HAS_DMA	---help---	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or	  any other SCSI device under Linux, say Y and make sure that you know	  the name of your SCSI host adapter (the card inside your computer	  that "speaks" the SCSI protocol, also called SCSI controller),	  because you will be asked for it.	  You also need to say Y here if you have a device which speaks	  the SCSI protocol.  Examples of this include the parallel port	  version of the IOMEGA ZIP drive, USB storage devices, Fibre	  Channel, FireWire storage and the IDE-SCSI emulation driver.	  To compile this driver as a module, choose M here and read	  <file:Documentation/scsi/scsi.txt>.	  The module will be called scsi_mod.	  However, do not compile this as a module if your root file system	  (the one containing the directory /) is located on a SCSI device.config SCSI_DMA	bool	default nconfig SCSI_TGT	tristate "SCSI target support"	depends on SCSI && EXPERIMENTAL	---help---	  If you want to use SCSI target mode drivers enable this option.	  If you choose M, the module will be called scsi_tgt.config SCSI_NETLINK	bool	default	n	select NETconfig SCSI_PROC_FS	bool "legacy /proc/scsi/ support"	depends on SCSI && PROC_FS	default y	---help---	  This option enables support for the various files in	  /proc/scsi.  In Linux 2.6 this has been superseded by	  files in sysfs but many legacy applications rely on this.	  If unsure say Y.comment "SCSI support type (disk, tape, CD-ROM)"	depends on SCSIconfig BLK_DEV_SD	tristate "SCSI disk support"	depends on SCSI	---help---	  If you want to use SCSI hard disks, Fibre Channel disks,	  Serial ATA (SATA) or Parallel ATA (PATA) hard disks,	  USB storage or the SCSI or parallel port version of	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI	  CD-ROMs.	  To compile this driver as a module, choose M here and read	  <file:Documentation/scsi/scsi.txt>.	  The module will be called sd_mod.	  Do not compile this driver as a module if your root file system	  (the one containing the directory /) is located on a SCSI disk.	  In this case, do not compile the driver for your SCSI host adapter	  (below) as a module either.config CHR_DEV_ST	tristate "SCSI tape support"	depends on SCSI	---help---	  If you want to use a SCSI tape drive under Linux, say Y and read the	  SCSI-HOWTO, available from	  <http://www.tldp.org/docs.html#howto>, and	  <file:Documentation/scsi/st.txt> in the kernel source.  This is NOT	  for SCSI CD-ROMs.	  To compile this driver as a module, choose M here and read	  <file:Documentation/scsi/scsi.txt>. The module will be called st.config CHR_DEV_OSST	tristate "SCSI OnStream SC-x0 tape support"	depends on SCSI	---help---	  The OnStream SC-x0 SCSI tape drives cannot be driven by the	  standard st driver, but instead need this special osst driver and	  use the  /dev/osstX char device nodes (major 206).  Via usb-storage	  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives	  as well.  Note that there is also a second generation of OnStream	  tape drives (ADR-x0) that supports the standard SCSI-2 commands for	  tapes (QIC-157) and can be driven by the standard driver st.	  For more information, you may have a look at the SCSI-HOWTO	  <http://www.tldp.org/docs.html#howto>  and	  <file:Documentation/scsi/osst.txt>  in the kernel source.	  More info on the OnStream driver may be found on	  <http://linux1.onstream.nl/test/>	  Please also have a look at the standard st docu, as most of it	  applies to osst as well.	  To compile this driver as a module, choose M here and read	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.config BLK_DEV_SR	tristate "SCSI CDROM support"	depends on SCSI	---help---	  If you want to use a SCSI or FireWire CD-ROM under Linux,	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at	  <http://www.tldp.org/docs.html#howto>. Also make sure to say	  Y or M to "ISO 9660 CD-ROM file system support" later.	  To compile this driver as a module, choose M here and read	  <file:Documentation/scsi/scsi.txt>.	  The module will be called sr_mod.config BLK_DEV_SR_VENDOR	bool "Enable vendor-specific extensions (for SCSI CDROM)"	depends on BLK_DEV_SR	help	  This enables the usage of vendor specific SCSI commands. This is	  required to support multisession CDs with old NEC/TOSHIBA cdrom	  drives (and HP Writers). If you have such a drive and get the first	  session only, try saying Y here; everybody else says N.config CHR_DEV_SG	tristate "SCSI generic support"	depends on SCSI	---help---	  If you want to use SCSI scanners, synthesizers or CD-writers or just	  about anything having "SCSI" in its name other than hard disks,	  CD-ROMs or tapes, say Y here. These won't be supported by the kernel	  directly, so you need some additional software which knows how to	  talk to these devices using the SCSI protocol:	  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD	  writer software look at Cdrtools	  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)	  and for burning a "disk at once": CDRDAO	  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high	  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).	  For other devices, it's possible that you'll have to write the	  driver software yourself. Please read the file	  <file:Documentation/scsi/scsi-generic.txt> for more information.	  To compile this driver as a module, choose M here and read	  <file:Documentation/scsi/scsi.txt>. The module will be called sg.	  If unsure, say N.config CHR_DEV_SCH	tristate "SCSI media changer support"	depends on SCSI	---help---	  This is a driver for SCSI media changers.  Most common devices are	  tape libraries and MOD/CDROM jukeboxes.  *Real* jukeboxes, you	  don't need this for those tiny 6-slot cdrom changers.  Media	  changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.	  If you have such hardware and want to use it with linux, say Y	  here.  Check <file:Documentation/scsi/scsi-changer.txt> for details.		  If you want to compile this as a module ( = code which can be	  inserted in and removed from the running kernel whenever you want),	  say M here and read <file:Documentation/kbuild/modules.txt> and	  <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.	  If unsure, say N.	comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"	depends on SCSIconfig SCSI_MULTI_LUN	bool "Probe all LUNs on each SCSI device"	depends on SCSI	help	  If you have a SCSI device that supports more than one LUN (Logical	  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you	  can say Y here to force the SCSI driver to probe for multiple LUNs.	  A SCSI device with multiple LUNs acts logically like multiple SCSI	  devices. The vast majority of SCSI devices have only one LUN, and	  so most people can say N here. The max_luns boot/module parameter 	  allows to override this setting.config SCSI_CONSTANTS	bool "Verbose SCSI error reporting (kernel size +=12K)"	depends on SCSI	help	  The error messages regarding your SCSI hardware will be easier to	  understand if you say Y here; it will enlarge your kernel by about	  12 KB. If in doubt, say Y.config SCSI_LOGGING	bool "SCSI logging facility"	depends on SCSI	---help---	  This turns on a logging facility that can be used to debug a number	  of SCSI related problems.	  If you say Y here, no logging output will appear by default, but you	  can enable logging by saying Y to "/proc file system support" and	  "Sysctl support" below and executing the command	  echo "scsi log token [level]" > /proc/scsi/scsi	  at boot time after the /proc file system has been mounted.	  There are a number of things that can be used for 'token' (you can	  find them in the source: <file:drivers/scsi/scsi.c>), and this	  allows you to select the types of information you want, and the	  level allows you to select the level of verbosity.	  If you say N here, it may be harder to track down some types of SCSI	  problems. If you say Y here your kernel will be somewhat larger, but	  there should be no noticeable performance impact as long as you have	  logging turned off.config SCSI_SCAN_ASYNC	bool "Asynchronous SCSI scanning"	depends on SCSI	help	  The SCSI subsystem can probe for devices while the rest of the	  system continues booting, and even probe devices on different	  busses in parallel, leading to a significant speed-up.	  If you have built SCSI as modules, enabling this option can	  be a problem as the devices may not have been found by the	  time your system expects them to have been.  You can load the	  scsi_wait_scan module to ensure that all scans have completed.	  If you build your SCSI drivers into the kernel, then everything	  will work fine if you say Y here.	  You can override this choice by specifying "scsi_mod.scan=sync"	  or async on the kernel's command line.config SCSI_WAIT_SCAN	tristate	default m	depends on SCSI	depends on MODULESmenu "SCSI Transports"	depends on SCSIconfig SCSI_SPI_ATTRS	tristate "Parallel SCSI (SPI) Transport Attributes"	depends on SCSI	help	  If you wish to export transport-specific information about	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.config SCSI_FC_ATTRS	tristate "FiberChannel Transport Attributes"	depends on SCSI	select SCSI_NETLINK	help	  If you wish to export transport-specific information about	  each attached FiberChannel device to sysfs, say Y.	  Otherwise, say N.config SCSI_FC_TGT_ATTRS	bool "SCSI target support for FiberChannel Transport Attributes"	depends on SCSI_FC_ATTRS	depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS	help		If you want to use SCSI target mode drivers enable this option.config SCSI_ISCSI_ATTRS	tristate "iSCSI Transport Attributes"	depends on SCSI && NET	help	  If you wish to export transport-specific information about	  each attached iSCSI device to sysfs, say Y.	  Otherwise, say N.config SCSI_SAS_ATTRS	tristate "SAS Transport Attributes"	depends on SCSI && BLK_DEV_BSG	help	  If you wish to export transport-specific information about	  each attached SAS device to sysfs, say Y.source "drivers/scsi/libsas/Kconfig"config SCSI_SRP_ATTRS	tristate "SRP Transport Attributes"	depends on SCSI	help	  If you wish to export transport-specific information about	  each attached SRP device to sysfs, say Y.config SCSI_SRP_TGT_ATTRS	bool "SCSI target support for SRP Transport Attributes"	depends on SCSI_SRP_ATTRS	depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS	help		If you want to use SCSI target mode drivers enable this option.endmenumenuconfig SCSI_LOWLEVEL	bool "SCSI low-level drivers"	depends on SCSI!=n	default yif SCSI_LOWLEVELconfig ISCSI_TCP	tristate "iSCSI Initiator over TCP/IP"	depends on SCSI && INET	select CRYPTO	select CRYPTO_MD5	select CRYPTO_CRC32C	select SCSI_ISCSI_ATTRS	help	 The iSCSI Driver provides a host with the ability to access storage	 through an IP network. The driver uses the iSCSI protocol to transport	 SCSI requests and responses over a TCP/IP network between the host	 (the "initiator") and "targets".  Architecturally, the iSCSI driver	 combines with the host's TCP/IP stack, network drivers, and Network	 Interface Card (NIC) to provide the same functions as a SCSI or a	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).	 To compile this driver as a module, choose M here: the	 module will be called iscsi_tcp.	 The userspace component needed to initialize the driver, documentation,	 and sample configuration files can be found here:	 http://linux-iscsi.sf.netconfig SGIWD93_SCSI	tristate "SGI WD93C93 SCSI Driver"	depends on SGI_IP22 && SCSI

⌨️ 快捷键说明

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