drivers/scsi/Kconfig

   1 menu "SCSI device support"
   2
   3 config SCSI_MOD
   4        tristate
   5        default y if SCSI=n || SCSI=y
   6        default m if SCSI=m
   7
   8 config RAID_ATTRS
   9         tristate "RAID Transport Class"
  10         default n
  11         depends on BLOCK
  12         depends on SCSI_MOD
  13         ---help---
  14           Provides RAID
  15
  16 config SCSI
  17         tristate "SCSI device support"
  18         depends on BLOCK
  19         select SCSI_DMA if HAS_DMA
  20         ---help---
  21           If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  22           any other SCSI device under Linux, say Y and make sure that you know
  23           the name of your SCSI host adapter (the card inside your computer
  24           that "speaks" the SCSI protocol, also called SCSI controller),
  25           because you will be asked for it.
  26
  27           You also need to say Y here if you have a device which speaks
  28           the SCSI protocol.  Examples of this include the parallel port
  29           version of the IOMEGA ZIP drive, USB storage devices, Fibre
  30           Channel, and FireWire storage.
  31
  32           To compile this driver as a module, choose M here and read
  33           <file:Documentation/scsi/scsi.txt>.
  34           The module will be called scsi_mod.
  35
  36           However, do not compile this as a module if your root file system
  37           (the one containing the directory /) is located on a SCSI device.
  38
  39 config SCSI_DMA
  40         bool
  41         default n
  42
  43 config SCSI_NETLINK
  44         bool
  45         default n
  46         depends on NET
  47
  48 config SCSI_MQ_DEFAULT
  49         bool "SCSI: use blk-mq I/O path by default"
  50         depends on SCSI
  51         ---help---
  52           This option enables the new blk-mq based I/O path for SCSI
  53           devices by default.  With the option the scsi_mod.use_blk_mq
  54           module/boot option defaults to Y, without it to N, but it can
  55           still be overridden either way.
  56
  57           If unsure say N.
  58
  59 config SCSI_PROC_FS
  60         bool "legacy /proc/scsi/ support"
  61         depends on SCSI && PROC_FS
  62         default y
  63         ---help---
  64           This option enables support for the various files in
  65           /proc/scsi.  In Linux 2.6 this has been superseded by
  66           files in sysfs but many legacy applications rely on this.
  67
  68           If unsure say Y.
  69
  70 comment "SCSI support type (disk, tape, CD-ROM)"
  71         depends on SCSI
  72
  73 config BLK_DEV_SD
  74         tristate "SCSI disk support"
  75         depends on SCSI
  76         ---help---
  77           If you want to use SCSI hard disks, Fibre Channel disks,
  78           Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
  79           USB storage or the SCSI or parallel port version of
  80           the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
  81           the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  82           <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  83           CD-ROMs.
  84
  85           To compile this driver as a module, choose M here and read
  86           <file:Documentation/scsi/scsi.txt>.
  87           The module will be called sd_mod.
  88
  89           Do not compile this driver as a module if your root file system
  90           (the one containing the directory /) is located on a SCSI disk.
  91           In this case, do not compile the driver for your SCSI host adapter
  92           (below) as a module either.
  93
  94 config CHR_DEV_ST
  95         tristate "SCSI tape support"
  96         depends on SCSI
  97         ---help---
  98           If you want to use a SCSI tape drive under Linux, say Y and read the
  99           SCSI-HOWTO, available from
 100           <http://www.tldp.org/docs.html#howto>, and
 101           <file:Documentation/scsi/st.txt> in the kernel source.  This is NOT
 102           for SCSI CD-ROMs.
 103
 104           To compile this driver as a module, choose M here and read
 105           <file:Documentation/scsi/scsi.txt>. The module will be called st.
 106
 107 config CHR_DEV_OSST
 108         tristate "SCSI OnStream SC-x0 tape support"
 109         depends on SCSI
 110         ---help---
 111           The OnStream SC-x0 SCSI tape drives cannot be driven by the
 112           standard st driver, but instead need this special osst driver and
 113           use the  /dev/osstX char device nodes (major 206).  Via usb-storage,
 114           you may be able to drive the USB-x0 and DI-x0 drives as well.
 115           Note that there is also a second generation of OnStream
 116           tape drives (ADR-x0) that supports the standard SCSI-2 commands for
 117           tapes (QIC-157) and can be driven by the standard driver st.
 118           For more information, you may have a look at the SCSI-HOWTO
 119           <http://www.tldp.org/docs.html#howto>  and
 120           <file:Documentation/scsi/osst.txt>  in the kernel source.
 121           More info on the OnStream driver may be found on
 122           <http://sourceforge.net/projects/osst/>
 123           Please also have a look at the standard st docu, as most of it
 124           applies to osst as well.
 125
 126           To compile this driver as a module, choose M here and read
 127           <file:Documentation/scsi/scsi.txt>. The module will be called osst.
 128
 129 config BLK_DEV_SR
 130         tristate "SCSI CDROM support"
 131         depends on SCSI
 132         ---help---
 133           If you want to use a CD or DVD drive attached to your computer
 134           by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
 135           and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
 136
 137           Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
 138
 139           To compile this driver as a module, choose M here and read
 140           <file:Documentation/scsi/scsi.txt>.
 141           The module will be called sr_mod.
 142
 143 config BLK_DEV_SR_VENDOR
 144         bool "Enable vendor-specific extensions (for SCSI CDROM)"
 145         depends on BLK_DEV_SR
 146         help
 147           This enables the usage of vendor specific SCSI commands. This is
 148           required to support multisession CDs with old NEC/TOSHIBA cdrom
 149           drives (and HP Writers). If you have such a drive and get the first
 150           session only, try saying Y here; everybody else says N.
 151
 152 config CHR_DEV_SG
 153         tristate "SCSI generic support"
 154         depends on SCSI
 155         ---help---
 156           If you want to use SCSI scanners, synthesizers or CD-writers or just
 157           about anything having "SCSI" in its name other than hard disks,
 158           CD-ROMs or tapes, say Y here. These won't be supported by the kernel
 159           directly, so you need some additional software which knows how to
 160           talk to these devices using the SCSI protocol:
 161
 162           For scanners, look at SANE (<http://www.sane-project.org/>). For CD
 163           writer software look at Cdrtools
 164           (<http://cdrecord.berlios.de/private/cdrecord.html>)
 165           and for burning a "disk at once": CDRDAO
 166           (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
 167           quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
 168           For other devices, it's possible that you'll have to write the
 169           driver software yourself. Please read the file
 170           <file:Documentation/scsi/scsi-generic.txt> for more information.
 171
 172           To compile this driver as a module, choose M here and read
 173           <file:Documentation/scsi/scsi.txt>. The module will be called sg.
 174
 175           If unsure, say N.
 176
 177 config CHR_DEV_SCH
 178         tristate "SCSI media changer support"
 179         depends on SCSI
 180         ---help---
 181           This is a driver for SCSI media changers.  Most common devices are
 182           tape libraries and MOD/CDROM jukeboxes.  *Real* jukeboxes, you
 183           don't need this for those tiny 6-slot cdrom changers.  Media
 184           changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
 185           If you have such hardware and want to use it with linux, say Y
 186           here.  Check <file:Documentation/scsi/scsi-changer.txt> for details.
 187
 188           If you want to compile this as a module ( = code which can be
 189           inserted in and removed from the running kernel whenever you want),
 190           say M here and read <file:Documentation/kbuild/modules.txt> and
 191           <file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
 192           If unsure, say N.
 193
 194 config SCSI_ENCLOSURE
 195         tristate "SCSI Enclosure Support"
 196         depends on SCSI && ENCLOSURE_SERVICES
 197         help
 198           Enclosures are devices sitting on or in SCSI backplanes that
 199           manage devices.  If you have a disk cage, the chances are that
 200           it has an enclosure device.  Selecting this option will just allow
 201           certain enclosure conditions to be reported and is not required.
 202
 203 config SCSI_CONSTANTS
 204         bool "Verbose SCSI error reporting (kernel size +=75K)"
 205         depends on SCSI
 206         help
 207           The error messages regarding your SCSI hardware will be easier to
 208           understand if you say Y here; it will enlarge your kernel by about
 209           75 KB. If in doubt, say Y.
 210
 211 config SCSI_LOGGING
 212         bool "SCSI logging facility"
 213         depends on SCSI
 214         ---help---
 215           This turns on a logging facility that can be used to debug a number
 216           of SCSI related problems.
 217
 218           If you say Y here, no logging output will appear by default, but you
 219           can enable logging by saying Y to "/proc file system support" and
 220           "Sysctl support" below and executing the command
 221
 222           echo <bitmask> > /proc/sys/dev/scsi/logging_level
 223
 224           where <bitmask> is a four byte value representing the logging type
 225           and logging level for each type of logging selected.
 226
 227           There are a number of logging types and you can find them in the
 228           source at <file:drivers/scsi/scsi_logging.h>. The logging levels
 229           are also described in that file and they determine the verbosity of
 230           the logging for each logging type.
 231
 232           If you say N here, it may be harder to track down some types of SCSI
 233           problems. If you say Y here your kernel will be somewhat larger, but
 234           there should be no noticeable performance impact as long as you have
 235           logging turned off.
 236
 237 config SCSI_SCAN_ASYNC
 238         bool "Asynchronous SCSI scanning"
 239         depends on SCSI
 240         help
 241           The SCSI subsystem can probe for devices while the rest of the
 242           system continues booting, and even probe devices on different
 243           busses in parallel, leading to a significant speed-up.
 244
 245           You can override this choice by specifying "scsi_mod.scan=sync"
 246           or async on the kernel's command line.
 247
 248           Note that this setting also affects whether resuming from
 249           system suspend will be performed asynchronously.
 250
 251 menu "SCSI Transports"
 252         depends on SCSI
 253
 254 config SCSI_SPI_ATTRS
 255         tristate "Parallel SCSI (SPI) Transport Attributes"
 256         depends on SCSI
 257         help
 258           If you wish to export transport-specific information about
 259           each attached SCSI device to sysfs, say Y.  Otherwise, say N.
 260
 261 config SCSI_FC_ATTRS
 262         tristate "FiberChannel Transport Attributes"
 263         depends on SCSI && NET
 264         select SCSI_NETLINK
 265         help
 266           If you wish to export transport-specific information about
 267           each attached FiberChannel device to sysfs, say Y.
 268           Otherwise, say N.
 269
 270 config SCSI_ISCSI_ATTRS
 271         tristate "iSCSI Transport Attributes"
 272         depends on SCSI && NET
 273         select BLK_DEV_BSGLIB
 274         help
 275           If you wish to export transport-specific information about
 276           each attached iSCSI device to sysfs, say Y.
 277           Otherwise, say N.
 278
 279 config SCSI_SAS_ATTRS
 280         tristate "SAS Transport Attributes"
 281         depends on SCSI
 282         select BLK_DEV_BSG
 283         help
 284           If you wish to export transport-specific information about
 285           each attached SAS device to sysfs, say Y.
 286
 287 source "drivers/scsi/libsas/Kconfig"
 288
 289 config SCSI_SRP_ATTRS
 290         tristate "SRP Transport Attributes"
 291         depends on SCSI
 292         help
 293           If you wish to export transport-specific information about
 294           each attached SRP device to sysfs, say Y.
 295
 296 endmenu
 297
 298 menuconfig SCSI_LOWLEVEL
 299         bool "SCSI low-level drivers"
 300         depends on SCSI!=n
 301         default y
 302
 303 if SCSI_LOWLEVEL && SCSI
 304
 305 config ISCSI_TCP
 306         tristate "iSCSI Initiator over TCP/IP"
 307         depends on SCSI && INET
 308         select CRYPTO
 309         select CRYPTO_MD5
 310         select CRYPTO_CRC32C
 311         select SCSI_ISCSI_ATTRS
 312         help
 313          The iSCSI Driver provides a host with the ability to access storage
 314          through an IP network. The driver uses the iSCSI protocol to transport
 315          SCSI requests and responses over a TCP/IP network between the host
 316          (the "initiator") and "targets".  Architecturally, the iSCSI driver
 317          combines with the host's TCP/IP stack, network drivers, and Network
 318          Interface Card (NIC) to provide the same functions as a SCSI or a
 319          Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
 320
 321          To compile this driver as a module, choose M here: the
 322          module will be called iscsi_tcp.
 323
 324          The userspace component needed to initialize the driver, documentation,
 325          and sample configuration files can be found here:
 326
 327          http://open-iscsi.org
 328
 329 config ISCSI_BOOT_SYSFS
 330         tristate "iSCSI Boot Sysfs Interface"
 331         default n
 332         help
 333           This option enables support for exposing iSCSI boot information
 334           via sysfs to userspace. If you wish to export this information,
 335           say Y. Otherwise, say N.
 336
 337 source "drivers/scsi/cxgbi/Kconfig"
 338 source "drivers/scsi/bnx2i/Kconfig"
 339 source "drivers/scsi/bnx2fc/Kconfig"
 340 source "drivers/scsi/be2iscsi/Kconfig"
 341 source "drivers/scsi/cxlflash/Kconfig"
 342
 343 config SGIWD93_SCSI
 344         tristate "SGI WD93C93 SCSI Driver"
 345         depends on SGI_HAS_WD93 && SCSI
 346         help
 347           If you have a Western Digital WD93 SCSI controller on
 348           an SGI MIPS system, say Y.  Otherwise, say N.
 349
 350 config BLK_DEV_3W_XXXX_RAID
 351         tristate "3ware 5/6/7/8xxx ATA-RAID support"
 352         depends on PCI && SCSI
 353         help
 354           3ware is the only hardware ATA-Raid product in Linux to date.
 355           This card is 2,4, or 8 channel master mode support only.
 356           SCSI support required!!!
 357
 358           <http://www.3ware.com/>
 359
 360           Please read the comments at the top of
 361           <file:drivers/scsi/3w-xxxx.c>.
 362
 363 config SCSI_HPSA
 364         tristate "HP Smart Array SCSI driver"
 365         depends on PCI && SCSI
 366         select CHECK_SIGNATURE
 367         help
 368           This driver supports HP Smart Array Controllers (circa 2009).
 369           It is a SCSI alternative to the cciss driver, which is a block
 370           driver.  Anyone wishing to use HP Smart Array controllers who
 371           would prefer the devices be presented to linux as SCSI devices,
 372           rather than as generic block devices should say Y here.
 373
 374 config SCSI_3W_9XXX
 375         tristate "3ware 9xxx SATA-RAID support"
 376         depends on PCI && SCSI
 377         help
 378           This driver supports the 9000 series 3ware SATA-RAID cards.
 379
 380           <http://www.amcc.com>
 381
 382           Please read the comments at the top of
 383           <file:drivers/scsi/3w-9xxx.c>.
 384
 385 config SCSI_3W_SAS
 386         tristate "3ware 97xx SAS/SATA-RAID support"
 387         depends on PCI && SCSI
 388         help
 389           This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
 390
 391           <http://www.lsi.com>
 392
 393           Please read the comments at the top of
 394           <file:drivers/scsi/3w-sas.c>.
 395
 396 config SCSI_7000FASST
 397         tristate "7000FASST SCSI support"
 398         depends on ISA && SCSI && ISA_DMA_API
 399         select CHECK_SIGNATURE
 400         help
 401           This driver supports the Western Digital 7000 SCSI host adapter
 402           family.  Some information is in the source:
 403           <file:drivers/scsi/wd7000.c>.
 404
 405           To compile this driver as a module, choose M here: the
 406           module will be called wd7000.
 407
 408 config SCSI_ACARD
 409         tristate "ACARD SCSI support"
 410         depends on PCI && SCSI
 411         help
 412           This driver supports the ACARD SCSI host adapter.
 413           Support Chip <ATP870 ATP876 ATP880 ATP885>
 414           To compile this driver as a module, choose M here: the
 415           module will be called atp870u.
 416
 417 config SCSI_AHA152X
 418         tristate "Adaptec AHA152X/2825 support"
 419         depends on ISA && SCSI
 420         select SCSI_SPI_ATTRS
 421         select CHECK_SIGNATURE
 422         ---help---
 423           This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
 424           SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
 425           must be manually specified in this case.
 426
 427           It is explained in section 3.3 of the SCSI-HOWTO, available from
 428           <http://www.tldp.org/docs.html#howto>. You might also want to
 429           read the file <file:Documentation/scsi/aha152x.txt>.
 430
 431           To compile this driver as a module, choose M here: the
 432           module will be called aha152x.
 433
 434 config SCSI_AHA1542
 435         tristate "Adaptec AHA1542 support"
 436         depends on ISA && SCSI && ISA_DMA_API
 437         ---help---
 438           This is support for a SCSI host adapter.  It is explained in section
 439           3.4 of the SCSI-HOWTO, available from
 440           <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
 441           purchased by Adaptec, and some former Trantor products are being
 442           sold under the Adaptec name.  If it doesn't work out of the box, you
 443           may have to change some settings in <file:drivers/scsi/aha1542.h>.
 444
 445           To compile this driver as a module, choose M here: the
 446           module will be called aha1542.
 447
 448 config SCSI_AHA1740
 449         tristate "Adaptec AHA1740 support"
 450         depends on EISA && SCSI
 451         ---help---
 452           This is support for a SCSI host adapter.  It is explained in section
 453           3.5 of the SCSI-HOWTO, available from
 454           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
 455           of the box, you may have to change some settings in
 456           <file:drivers/scsi/aha1740.h>.
 457
 458           To compile this driver as a module, choose M here: the
 459           module will be called aha1740.
 460
 461 config SCSI_AACRAID
 462         tristate "Adaptec AACRAID support"
 463         depends on SCSI && PCI
 464         help
 465           This driver supports a variety of Dell, HP, Adaptec, IBM and
 466           ICP storage products. For a list of supported products, refer
 467           to <file:Documentation/scsi/aacraid.txt>.
 468
 469           To compile this driver as a module, choose M here: the module
 470           will be called aacraid.
 471
 472
 473 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
 474 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
 475 source "drivers/scsi/aic94xx/Kconfig"
 476 source "drivers/scsi/mvsas/Kconfig"
 477
 478 config SCSI_MVUMI
 479         tristate "Marvell UMI driver"
 480         depends on SCSI && PCI
 481         help
 482           Module for Marvell Universal Message Interface(UMI) driver
 483
 484           To compile this driver as a module, choose M here: the
 485           module will be called mvumi.
 486
 487 config SCSI_DPT_I2O
 488         tristate "Adaptec I2O RAID support "
 489         depends on SCSI && PCI && VIRT_TO_BUS
 490         help
 491           This driver supports all of Adaptec's I2O based RAID controllers as
 492           well as the DPT SmartRaid V cards.  This is an Adaptec maintained
 493           driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
 494
 495           To compile this driver as a module, choose M here: the
 496           module will be called dpt_i2o.
 497
 498 config SCSI_ADVANSYS
 499         tristate "AdvanSys SCSI support"
 500         depends on SCSI
 501         depends on ISA || EISA || PCI
 502         help
 503           This is a driver for all SCSI host adapters manufactured by
 504           AdvanSys. It is documented in the kernel source in
 505           <file:drivers/scsi/advansys.c>.
 506
 507           To compile this driver as a module, choose M here: the
 508           module will be called advansys.
 509
 510 config SCSI_IN2000
 511         tristate "Always IN2000 SCSI support"
 512         depends on ISA && SCSI
 513         help
 514           This is support for an ISA bus SCSI host adapter.  You'll find more
 515           information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
 516           out of the box, you may have to change the jumpers for IRQ or
 517           address selection.
 518
 519           To compile this driver as a module, choose M here: the
 520           module will be called in2000.
 521
 522 config SCSI_ARCMSR
 523         tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
 524         depends on PCI && SCSI
 525         help
 526           This driver supports all of ARECA's SATA/SAS RAID controller cards.
 527           This is an ARECA-maintained driver by Erich Chen.
 528           If you have any problems, please mail to: <erich@areca.com.tw>.
 529           Areca supports Linux RAID config tools.
 530           Please link <http://www.areca.com.tw>
 531
 532           To compile this driver as a module, choose M here: the
 533           module will be called arcmsr (modprobe arcmsr).
 534
 535 source "drivers/scsi/esas2r/Kconfig"
 536 source "drivers/scsi/megaraid/Kconfig.megaraid"
 537 source "drivers/scsi/mpt2sas/Kconfig"
 538 source "drivers/scsi/mpt3sas/Kconfig"
 539 source "drivers/scsi/ufs/Kconfig"
 540
 541 config SCSI_HPTIOP
 542         tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
 543         depends on SCSI && PCI
 544         help
 545           This option enables support for HighPoint RocketRAID 3xxx/4xxx
 546           controllers.
 547
 548           To compile this driver as a module, choose M here; the module
 549           will be called hptiop. If unsure, say N.
 550
 551 config SCSI_BUSLOGIC
 552         tristate "BusLogic SCSI support"
 553         depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
 554         ---help---
 555           This is support for BusLogic MultiMaster and FlashPoint SCSI Host
 556           Adapters. Consult the SCSI-HOWTO, available from
 557           <http://www.tldp.org/docs.html#howto>, and the files
 558           <file:Documentation/scsi/BusLogic.txt> and
 559           <file:Documentation/scsi/FlashPoint.txt> for more information.
 560           Note that support for FlashPoint is only available for 32-bit
 561           x86 configurations.
 562
 563           To compile this driver as a module, choose M here: the
 564           module will be called BusLogic.
 565
 566 config SCSI_FLASHPOINT
 567         bool "FlashPoint support"
 568         depends on SCSI_BUSLOGIC && PCI
 569         help
 570           This option allows you to add FlashPoint support to the
 571           BusLogic SCSI driver. The FlashPoint SCCB Manager code is
 572           substantial, so users of MultiMaster Host Adapters may not
 573           wish to include it.
 574
 575 config VMWARE_PVSCSI
 576         tristate "VMware PVSCSI driver support"
 577         depends on PCI && SCSI && X86
 578         help
 579           This driver supports VMware's para virtualized SCSI HBA.
 580           To compile this driver as a module, choose M here: the
 581           module will be called vmw_pvscsi.
 582
 583 config XEN_SCSI_FRONTEND
 584         tristate "XEN SCSI frontend driver"
 585         depends on SCSI && XEN
 586         select XEN_XENBUS_FRONTEND
 587         help
 588           The XEN SCSI frontend driver allows the kernel to access SCSI Devices
 589           within another guest OS (usually Dom0).
 590           Only needed if the kernel is running in a XEN guest and generic
 591           SCSI access to a device is needed.
 592
 593 config HYPERV_STORAGE
 594         tristate "Microsoft Hyper-V virtual storage driver"
 595         depends on SCSI && HYPERV
 596         default HYPERV
 597         help
 598           Select this option to enable the Hyper-V virtual storage driver.
 599
 600 config LIBFC
 601         tristate "LibFC module"
 602         depends on SCSI_FC_ATTRS
 603         select CRC32
 604         ---help---
 605           Fibre Channel library module
 606
 607 config LIBFCOE
 608         tristate "LibFCoE module"
 609         depends on LIBFC
 610         ---help---
 611           Library for Fibre Channel over Ethernet module
 612
 613 config FCOE
 614         tristate "FCoE module"
 615         depends on PCI
 616         depends on LIBFCOE
 617         ---help---
 618           Fibre Channel over Ethernet module
 619
 620 config FCOE_FNIC
 621         tristate "Cisco FNIC Driver"
 622         depends on PCI && X86
 623         depends on LIBFCOE
 624         help
 625           This is support for the Cisco PCI-Express FCoE HBA.
 626
 627           To compile this driver as a module, choose M here and read
 628           <file:Documentation/scsi/scsi.txt>.
 629           The module will be called fnic.
 630
 631 config SCSI_SNIC
 632         tristate "Cisco SNIC Driver"
 633         depends on PCI && SCSI
 634         help
 635           This is support for the Cisco PCI-Express SCSI HBA.
 636
 637           To compile this driver as a module, choose M here and read
 638           <file:Documentation/scsi/scsi.txt>.
 639           The module will be called snic.
 640
 641 config SCSI_SNIC_DEBUG_FS
 642         bool "Cisco SNIC Driver Debugfs Support"
 643         depends on SCSI_SNIC && DEBUG_FS
 644         help
 645           This enables to list debugging information from SNIC Driver
 646           available via debugfs file system
 647
 648 config SCSI_DMX3191D
 649         tristate "DMX3191D SCSI support"
 650         depends on PCI && SCSI
 651         select SCSI_SPI_ATTRS
 652         help
 653           This is support for Domex DMX3191D SCSI Host Adapters.
 654
 655           To compile this driver as a module, choose M here: the
 656           module will be called dmx3191d.
 657
 658 config SCSI_DTC3280
 659         tristate "DTC3180/3280 SCSI support"
 660         depends on ISA && SCSI
 661         select SCSI_SPI_ATTRS
 662         select CHECK_SIGNATURE
 663         help
 664           This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
 665           the SCSI-HOWTO, available from
 666           <http://www.tldp.org/docs.html#howto>, and the file
 667           <file:Documentation/scsi/dtc3x80.txt>.
 668
 669           To compile this driver as a module, choose M here: the
 670           module will be called dtc.
 671
 672 config SCSI_EATA
 673         tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
 674         depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
 675         ---help---
 676           This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
 677           ISA and all EISA I/O addresses are probed looking for the "EATA"
 678           signature. The addresses of all the PCI SCSI controllers reported
 679           by the PCI subsystem are probed as well.
 680
 681           You want to read the start of <file:drivers/scsi/eata.c> and the
 682           SCSI-HOWTO, available from
 683           <http://www.tldp.org/docs.html#howto>.
 684
 685           To compile this driver as a module, choose M here: the
 686           module will be called eata.
 687
 688 config SCSI_EATA_TAGGED_QUEUE
 689         bool "enable tagged command queueing"
 690         depends on SCSI_EATA
 691         help
 692           This is a feature of SCSI-2 which improves performance: the host
 693           adapter can send several SCSI commands to a device's queue even if
 694           previous commands haven't finished yet.
 695           This is equivalent to the "eata=tc:y" boot option.
 696
 697 config SCSI_EATA_LINKED_COMMANDS
 698         bool "enable elevator sorting"
 699         depends on SCSI_EATA
 700         help
 701           This option enables elevator sorting for all probed SCSI disks and
 702           CD-ROMs. It definitely reduces the average seek distance when doing
 703           random seeks, but this does not necessarily result in a noticeable
 704           performance improvement: your mileage may vary...
 705           This is equivalent to the "eata=lc:y" boot option.
 706
 707 config SCSI_EATA_MAX_TAGS
 708         int "maximum number of queued commands"
 709         depends on SCSI_EATA
 710         default "16"
 711         help
 712           This specifies how many SCSI commands can be maximally queued for
 713           each probed SCSI device. You should reduce the default value of 16
 714           only if you have disks with buggy or limited tagged command support.
 715           Minimum is 2 and maximum is 62. This value is also the window size
 716           used by the elevator sorting option above. The effective value used
 717           by the driver for each probed SCSI device is reported at boot time.
 718           This is equivalent to the "eata=mq:8" boot option.
 719
 720 config SCSI_EATA_PIO
 721         tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
 722         depends on (ISA || EISA || PCI) && SCSI && BROKEN
 723         ---help---
 724           This driver supports all EATA-PIO protocol compliant SCSI Host
 725           Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
 726           host adapters could also use this driver but are discouraged from
 727           doing so, since this driver only supports hard disks and lacks
 728           numerous features.  You might want to have a look at the SCSI-HOWTO,
 729           available from <http://www.tldp.org/docs.html#howto>.
 730
 731           To compile this driver as a module, choose M here: the
 732           module will be called eata_pio.
 733
 734 config SCSI_FUTURE_DOMAIN
 735         tristate "Future Domain 16xx SCSI/AHA-2920A support"
 736         depends on (ISA || PCI) && SCSI
 737         select CHECK_SIGNATURE
 738         ---help---
 739           This is support for Future Domain's 16-bit SCSI host adapters
 740           (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
 741           other adapters based on the Future Domain chipsets (Quantum
 742           ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
 743           It is explained in section 3.7 of the SCSI-HOWTO, available from
 744           <http://www.tldp.org/docs.html#howto>.
 745
 746           NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
 747           and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
 748           controller support"). This Future Domain driver works with the older
 749           Adaptec AHA-2920A boards with a Future Domain chip on them.
 750
 751           To compile this driver as a module, choose M here: the
 752           module will be called fdomain.
 753
 754 config SCSI_GDTH
 755         tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
 756         depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
 757         ---help---
 758           Formerly called GDT SCSI Disk Array Controller Support.
 759
 760           This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
 761           manufactured by Intel Corporation/ICP vortex GmbH. It is documented
 762           in the kernel source in <file:drivers/scsi/gdth.c> and
 763           <file:drivers/scsi/gdth.h>.
 764
 765           To compile this driver as a module, choose M here: the
 766           module will be called gdth.
 767
 768 config SCSI_ISCI
 769         tristate "Intel(R) C600 Series Chipset SAS Controller"
 770         depends on PCI && SCSI
 771         depends on X86
 772         select SCSI_SAS_LIBSAS
 773         ---help---
 774           This driver supports the 6Gb/s SAS capabilities of the storage
 775           control unit found in the Intel(R) C600 series chipset.
 776
 777 config SCSI_GENERIC_NCR5380
 778         tristate "Generic NCR5380/53c400 SCSI PIO support"
 779         depends on ISA && SCSI
 780         select SCSI_SPI_ATTRS
 781         ---help---
 782           This is a driver for the old NCR 53c80 series of SCSI controllers
 783           on boards using PIO. Most boards such as the Trantor T130 fit this
 784           category, along with a large number of ISA 8bit controllers shipped
 785           for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
 786           you should select the specific driver for that card rather than
 787           generic 5380 support.
 788
 789           It is explained in section 3.8 of the SCSI-HOWTO, available from
 790           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
 791           of the box, you may have to change some settings in
 792           <file:drivers/scsi/g_NCR5380.h>.
 793
 794           To compile this driver as a module, choose M here: the
 795           module will be called g_NCR5380.
 796
 797 config SCSI_GENERIC_NCR5380_MMIO
 798         tristate "Generic NCR5380/53c400 SCSI MMIO support"
 799         depends on ISA && SCSI
 800         select SCSI_SPI_ATTRS
 801         ---help---
 802           This is a driver for the old NCR 53c80 series of SCSI controllers
 803           on boards using memory mapped I/O.
 804           It is explained in section 3.8 of the SCSI-HOWTO, available from
 805           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
 806           of the box, you may have to change some settings in
 807           <file:drivers/scsi/g_NCR5380.h>.
 808
 809           To compile this driver as a module, choose M here: the
 810           module will be called g_NCR5380_mmio.
 811
 812 config SCSI_GENERIC_NCR53C400
 813         bool "Enable NCR53c400 extensions"
 814         depends on SCSI_GENERIC_NCR5380
 815         help
 816           This enables certain optimizations for the NCR53c400 SCSI cards.
 817           You might as well try it out.  Note that this driver will only probe
 818           for the Trantor T130B in its default configuration; you might have
 819           to pass a command line option to the kernel at boot time if it does
 820           not detect your card.  See the file
 821           <file:Documentation/scsi/g_NCR5380.txt> for details.
 822
 823 config SCSI_IPS
 824         tristate "IBM ServeRAID support"
 825         depends on PCI && SCSI
 826         ---help---
 827           This is support for the IBM ServeRAID hardware RAID controllers.
 828           See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
 829           and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
 830           for more information.  If this driver does not work correctly
 831           without modification please contact the author by email at
 832           <ipslinux@adaptec.com>.
 833
 834           To compile this driver as a module, choose M here: the
 835           module will be called ips.
 836
 837 config SCSI_IBMVSCSI
 838         tristate "IBM Virtual SCSI support"
 839         depends on PPC_PSERIES
 840         select SCSI_SRP_ATTRS
 841         help
 842           This is the IBM POWER Virtual SCSI Client
 843
 844           To compile this driver as a module, choose M here: the
 845           module will be called ibmvscsi.
 846
 847 config SCSI_IBMVFC
 848         tristate "IBM Virtual FC support"
 849         depends on PPC_PSERIES && SCSI
 850         depends on SCSI_FC_ATTRS
 851         help
 852           This is the IBM POWER Virtual FC Client
 853
 854           To compile this driver as a module, choose M here: the
 855           module will be called ibmvfc.
 856
 857 config SCSI_IBMVFC_TRACE
 858         bool "enable driver internal trace"
 859         depends on SCSI_IBMVFC
 860         default y
 861         help
 862           If you say Y here, the driver will trace all commands issued
 863           to the adapter. Performance impact is minimal. Trace can be
 864           dumped using /sys/class/scsi_host/hostXX/trace.
 865
 866 config SCSI_INITIO
 867         tristate "Initio 9100U(W) support"
 868         depends on PCI && SCSI
 869         help
 870           This is support for the Initio 91XXU(W) SCSI host adapter.  Please
 871           read the SCSI-HOWTO, available from
 872           <http://www.tldp.org/docs.html#howto>.
 873
 874           To compile this driver as a module, choose M here: the
 875           module will be called initio.
 876
 877 config SCSI_INIA100
 878         tristate "Initio INI-A100U2W support"
 879         depends on PCI && SCSI
 880         help
 881           This is support for the Initio INI-A100U2W SCSI host adapter.
 882           Please read the SCSI-HOWTO, available from
 883           <http://www.tldp.org/docs.html#howto>.
 884
 885           To compile this driver as a module, choose M here: the
 886           module will be called a100u2w.
 887
 888 config SCSI_PPA
 889         tristate "IOMEGA parallel port (ppa - older drives)"
 890         depends on SCSI && PARPORT_PC
 891         ---help---
 892           This driver supports older versions of IOMEGA's parallel port ZIP
 893           drive (a 100 MB removable media device).
 894
 895           Note that you can say N here if you have the SCSI version of the ZIP
 896           drive: it will be supported automatically if you said Y to the
 897           generic "SCSI disk support", above.
 898
 899           If you have the ZIP Plus drive or a more recent parallel port ZIP
 900           drive (if the supplied cable with the drive is labeled "AutoDetect")
 901           then you should say N here and Y to "IOMEGA parallel port (imm -
 902           newer drives)", below.
 903
 904           For more information about this driver and how to use it you should
 905           read the file <file:Documentation/scsi/ppa.txt>.  You should also read
 906           the SCSI-HOWTO, which is available from
 907           <http://www.tldp.org/docs.html#howto>.  If you use this driver,
 908           you will still be able to use the parallel port for other tasks,
 909           such as a printer; it is safe to compile both drivers into the
 910           kernel.
 911
 912           To compile this driver as a module, choose M here: the
 913           module will be called ppa.
 914
 915 config SCSI_IMM
 916         tristate "IOMEGA parallel port (imm - newer drives)"
 917         depends on SCSI && PARPORT_PC
 918         ---help---
 919           This driver supports newer versions of IOMEGA's parallel port ZIP
 920           drive (a 100 MB removable media device).
 921
 922           Note that you can say N here if you have the SCSI version of the ZIP
 923           drive: it will be supported automatically if you said Y to the
 924           generic "SCSI disk support", above.
 925
 926           If you have the ZIP Plus drive or a more recent parallel port ZIP
 927           drive (if the supplied cable with the drive is labeled "AutoDetect")
 928           then you should say Y here; if you have an older ZIP drive, say N
 929           here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
 930
 931           For more information about this driver and how to use it you should
 932           read the file <file:Documentation/scsi/ppa.txt>.  You should also read
 933           the SCSI-HOWTO, which is available from
 934           <http://www.tldp.org/docs.html#howto>.  If you use this driver,
 935           you will still be able to use the parallel port for other tasks,
 936           such as a printer; it is safe to compile both drivers into the
 937           kernel.
 938
 939           To compile this driver as a module, choose M here: the
 940           module will be called imm.
 941
 942 config SCSI_IZIP_EPP16
 943         bool "ppa/imm option - Use slow (but safe) EPP-16"
 944         depends on SCSI_PPA || SCSI_IMM
 945         ---help---
 946           EPP (Enhanced Parallel Port) is a standard for parallel ports which
 947           allows them to act as expansion buses that can handle up to 64
 948           peripheral devices.
 949
 950           Some parallel port chipsets are slower than their motherboard, and
 951           so we have to control the state of the chipset's FIFO queue every
 952           now and then to avoid data loss. This will be done if you say Y
 953           here.
 954
 955           Generally, saying Y is the safe option and slows things down a bit.
 956
 957 config SCSI_IZIP_SLOW_CTR
 958         bool "ppa/imm option - Assume slow parport control register"
 959         depends on SCSI_PPA || SCSI_IMM
 960         help
 961           Some parallel ports are known to have excessive delays between
 962           changing the parallel port control register and good data being
 963           available on the parallel port data/status register. This option
 964           forces a small delay (1.0 usec to be exact) after changing the
 965           control register to let things settle out. Enabling this option may
 966           result in a big drop in performance but some very old parallel ports
 967           (found in 386 vintage machines) will not work properly.
 968
 969           Generally, saying N is fine.
 970
 971 config SCSI_NCR53C406A
 972         tristate "NCR53c406a SCSI support"
 973         depends on ISA && SCSI
 974         help
 975           This is support for the NCR53c406a SCSI host adapter.  For user
 976           configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
 977           in the kernel source.  Also read the SCSI-HOWTO, available from
 978           <http://www.tldp.org/docs.html#howto>.
 979
 980           To compile this driver as a module, choose M here: the
 981           module will be called NCR53c406.
 982
 983 config SCSI_NCR_D700
 984         tristate "NCR Dual 700 MCA SCSI support"
 985         depends on MCA && SCSI
 986         select SCSI_SPI_ATTRS
 987         help
 988           This is a driver for the MicroChannel Dual 700 card produced by
 989           NCR and commonly used in 345x/35xx/4100 class machines.  It always
 990           tries to negotiate sync and uses tag command queueing.
 991
 992           Unless you have an NCR manufactured machine, the chances are that
 993           you do not have this SCSI card, so say N.
 994
 995 config SCSI_LASI700
 996         tristate "HP Lasi SCSI support for 53c700/710"
 997         depends on GSC && SCSI
 998         select SCSI_SPI_ATTRS
 999         help
1000           This is a driver for the SCSI controller in the Lasi chip found in
1001           many PA-RISC workstations & servers.  If you do not know whether you
1002           have a Lasi chip, it is safe to say "Y" here.
1003
1004 config SCSI_SNI_53C710
1005         tristate "SNI RM SCSI support for 53c710"
1006         depends on SNI_RM && SCSI
1007         select SCSI_SPI_ATTRS
1008         select 53C700_LE_ON_BE
1009         help
1010           This is a driver for the onboard SCSI controller found in older
1011           SNI RM workstations & servers.
1012
1013 config 53C700_LE_ON_BE
1014         bool
1015         depends on SCSI_LASI700
1016         default y
1017
1018 config SCSI_STEX
1019         tristate "Promise SuperTrak EX Series support"
1020         depends on PCI && SCSI
1021         ---help---
1022           This driver supports Promise SuperTrak EX series storage controllers.
1023
1024           Promise provides Linux RAID configuration utility for these
1025           controllers. Please visit <http://www.promise.com> to download.
1026
1027           To compile this driver as a module, choose M here: the
1028           module will be called stex.
1029
1030 config 53C700_BE_BUS
1031         bool
1032         depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
1033         default y
1034
1035 config SCSI_SYM53C8XX_2
1036         tristate "SYM53C8XX Version 2 SCSI support"
1037         depends on PCI && SCSI
1038         select SCSI_SPI_ATTRS
1039         ---help---
1040           This driver supports the whole NCR53C8XX/SYM53C8XX family of
1041           PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
1042           Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
1043           language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
1044           controllers; you need to use the Fusion MPT driver for that.
1045
1046           Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
1047           information.
1048
1049 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
1050         int "DMA addressing mode"
1051         depends on SCSI_SYM53C8XX_2
1052         default "1"
1053         ---help---
1054           This option only applies to PCI-SCSI chips that are PCI DAC
1055           capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
1056
1057           When set to 0, the driver will program the chip to only perform
1058           32-bit DMA.  When set to 1, the chip will be able to perform DMA
1059           to addresses up to 1TB.  When set to 2, the driver supports the
1060           full 64-bit DMA address range, but can only address 16 segments
1061           of 4 GB each.  This limits the total addressable range to 64 GB.
1062
1063           Most machines with less than 4GB of memory should use a setting
1064           of 0 for best performance.  If your machine has 4GB of memory
1065           or more, you should set this option to 1 (the default).
1066
1067           The still experimental value 2 (64 bit DMA addressing with 16
1068           x 4GB segments limitation) can be used on systems that require
1069           PCI address bits past bit 39 to be set for the addressing of
1070           memory using PCI DAC cycles.
1071
1072 config SCSI_SYM53C8XX_DEFAULT_TAGS
1073         int "Default tagged command queue depth"
1074         depends on SCSI_SYM53C8XX_2
1075         default "16"
1076         help
1077           This is the default value of the command queue depth the
1078           driver will announce to the generic SCSI layer for devices
1079           that support tagged command queueing. This value can be changed
1080           from the boot command line.  This is a soft limit that cannot
1081           exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
1082
1083 config SCSI_SYM53C8XX_MAX_TAGS
1084         int "Maximum number of queued commands"
1085         depends on SCSI_SYM53C8XX_2
1086         default "64"
1087         help
1088           This option allows you to specify the maximum number of commands
1089           that can be queued to any device, when tagged command queuing is
1090           possible. The driver supports up to 256 queued commands per device.
1091           This value is used as a compiled-in hard limit.
1092
1093 config SCSI_SYM53C8XX_MMIO
1094         bool "Use memory mapped IO"
1095         depends on SCSI_SYM53C8XX_2
1096         default y
1097         help
1098           Memory mapped IO is faster than Port IO.  Most people should
1099           answer Y here, but some machines may have problems.  If you have
1100           to answer N here, please report the problem to the maintainer.
1101
1102 config SCSI_IPR
1103         tristate "IBM Power Linux RAID adapter support"
1104         depends on PCI && SCSI && ATA
1105         select FW_LOADER
1106         ---help---
1107           This driver supports the IBM Power Linux family RAID adapters.
1108           This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
1109           as IBM iSeries 5702, 5703, 5709, and 570A.
1110
1111 config SCSI_IPR_TRACE
1112         bool "enable driver internal trace"
1113         depends on SCSI_IPR
1114         default y
1115         help
1116           If you say Y here, the driver will trace all commands issued
1117           to the adapter. Performance impact is minimal. Trace can be
1118           dumped using /sys/bus/class/scsi_host/hostXX/trace.
1119
1120 config SCSI_IPR_DUMP
1121         bool "enable adapter dump support"
1122         depends on SCSI_IPR
1123         default y
1124         help
1125           If you say Y here, the driver will support adapter crash dump.
1126           If you enable this support, the iprdump daemon can be used
1127           to capture adapter failure analysis information.
1128
1129 config SCSI_ZALON
1130         tristate "Zalon SCSI support"
1131         depends on GSC && SCSI
1132         select SCSI_SPI_ATTRS
1133         help
1134           The Zalon is a GSC/HSC bus interface chip that sits between the
1135           PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1136           C110, J200, J210 and some D, K & R-class machines.  It's also
1137           used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1138           Say Y here if you have one of these machines or cards.
1139
1140 config SCSI_NCR_Q720
1141         tristate "NCR Quad 720 MCA SCSI support"
1142         depends on MCA && SCSI
1143         select SCSI_SPI_ATTRS
1144         help
1145           This is a driver for the MicroChannel Quad 720 card produced by
1146           NCR and commonly used in 345x/35xx/4100 class machines.  It always
1147           tries to negotiate sync and uses tag command queueing.
1148
1149           Unless you have an NCR manufactured machine, the chances are that
1150           you do not have this SCSI card, so say N.
1151
1152 config SCSI_NCR53C8XX_DEFAULT_TAGS
1153         int "default tagged command queue depth"
1154         depends on SCSI_ZALON || SCSI_NCR_Q720
1155         default "8"
1156         ---help---
1157           "Tagged command queuing" is a feature of SCSI-2 which improves
1158           performance: the host adapter can send several SCSI commands to a
1159           device's queue even if previous commands haven't finished yet.
1160           Because the device is intelligent, it can optimize its operations
1161           (like head positioning) based on its own request queue. Some SCSI
1162           devices don't implement this properly; if you want to disable this
1163           feature, enter 0 or 1 here (it doesn't matter which).
1164
1165           The default value is 8 and should be supported by most hard disks.
1166           This value can be overridden from the boot command line using the
1167           'tags' option as follows (example):
1168           'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1169           4, set queue depth to 16 for target 2 and target 3 on controller 0
1170           and set queue depth to 10 for target 0 / lun 2 on controller 1.
1171
1172           The normal answer therefore is to go with the default 8 and to use
1173           a boot command line option for devices that need to use a different
1174           command queue depth.
1175
1176           There is no safe option other than using good SCSI devices.
1177
1178 config SCSI_NCR53C8XX_MAX_TAGS
1179         int "maximum number of queued commands"
1180         depends on SCSI_ZALON || SCSI_NCR_Q720
1181         default "32"
1182         ---help---
1183           This option allows you to specify the maximum number of commands
1184           that can be queued to any device, when tagged command queuing is
1185           possible. The default value is 32. Minimum is 2, maximum is 64.
1186           Modern hard disks are able to support 64 tags and even more, but
1187           do not seem to be faster when more than 32 tags are being used.
1188
1189           So, the normal answer here is to go with the default value 32 unless
1190           you are using very large hard disks with large cache (>= 1 MB) that
1191           are able to take advantage of more than 32 tagged commands.
1192
1193           There is no safe option and the default answer is recommended.
1194
1195 config SCSI_NCR53C8XX_SYNC
1196         int "synchronous transfers frequency in MHz"
1197         depends on SCSI_ZALON || SCSI_NCR_Q720
1198         default "20"
1199         ---help---
1200           The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1201           rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
1202           are respectively the maximum data transfer rates in mega-transfers
1203           per second for each class.  For example, a FAST-20 Wide 16 device is
1204           able to transfer data at 20 million 16 bit packets per second for a
1205           total rate of 40 MB/s.
1206
1207           You may specify 0 if you want to only use asynchronous data
1208           transfers. This is the safest and slowest option. Otherwise, specify
1209           a value between 5 and 80, depending on the capability of your SCSI
1210           controller.  The higher the number, the faster the data transfer.
1211           Note that 80 should normally be ok since the driver decreases the
1212           value automatically according to the controller's capabilities.
1213
1214           Your answer to this question is ignored for controllers with NVRAM,
1215           since the driver will get this information from the user set-up.  It
1216           also can be overridden using a boot setup option, as follows
1217           (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1218           for FAST-20 synchronous data transfer (20 mega-transfers per
1219           second).
1220
1221           The normal answer therefore is not to go with the default but to
1222           select the maximum value 80 allowing the driver to use the maximum
1223           value supported by each controller. If this causes problems with
1224           your SCSI devices, you should come back and decrease the value.
1225
1226           There is no safe option other than using good cabling, right
1227           terminations and SCSI conformant devices.
1228
1229 config SCSI_NCR53C8XX_NO_DISCONNECT
1230         bool "not allow targets to disconnect"
1231         depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1232         help
1233           This option is only provided for safety if you suspect some SCSI
1234           device of yours to not support properly the target-disconnect
1235           feature. In that case, you would say Y here. In general however, to
1236           not allow targets to disconnect is not reasonable if there is more
1237           than 1 device on a SCSI bus. The normal answer therefore is N.
1238
1239 config SCSI_PAS16
1240         tristate "PAS16 SCSI support"
1241         depends on ISA && SCSI
1242         select SCSI_SPI_ATTRS
1243         ---help---
1244           This is support for a SCSI host adapter.  It is explained in section
1245           3.10 of the SCSI-HOWTO, available from
1246           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1247           of the box, you may have to change some settings in
1248           <file:drivers/scsi/pas16.h>.
1249
1250           To compile this driver as a module, choose M here: the
1251           module will be called pas16.
1252
1253 config SCSI_QLOGIC_FAS
1254         tristate "Qlogic FAS SCSI support"
1255         depends on ISA && SCSI
1256         ---help---
1257           This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1258           FastSCSI! cards as well as any other card based on the FASXX chip
1259           (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1260
1261           This driver does NOT support the PCI versions of these cards. The
1262           PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1263           SCSI support"), below.
1264
1265           Information about this driver is contained in
1266           <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
1267           SCSI-HOWTO, available from
1268           <http://www.tldp.org/docs.html#howto>.
1269
1270           To compile this driver as a module, choose M here: the
1271           module will be called qlogicfas.
1272
1273 config SCSI_QLOGIC_1280
1274         tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1275         depends on PCI && SCSI
1276         help
1277           Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1278
1279           To compile this driver as a module, choose M here: the
1280           module will be called qla1280.
1281
1282 config SCSI_QLOGICPTI
1283         tristate "PTI Qlogic, ISP Driver"
1284         depends on SBUS && SCSI
1285         help
1286           This driver supports SBUS SCSI controllers from PTI or QLogic. These
1287           controllers are known under Solaris as qpti and in the openprom as
1288           PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1289           driven by a different driver.
1290
1291           To compile this driver as a module, choose M here: the
1292           module will be called qlogicpti.
1293
1294 source "drivers/scsi/qla2xxx/Kconfig"
1295 source "drivers/scsi/qla4xxx/Kconfig"
1296
1297 config SCSI_LPFC
1298         tristate "Emulex LightPulse Fibre Channel Support"
1299         depends on PCI && SCSI
1300         depends on SCSI_FC_ATTRS
1301         select CRC_T10DIF
1302         help
1303           This lpfc driver supports the Emulex LightPulse
1304           Family of Fibre Channel PCI host adapters.
1305
1306 config SCSI_LPFC_DEBUG_FS
1307         bool "Emulex LightPulse Fibre Channel debugfs Support"
1308         depends on SCSI_LPFC && DEBUG_FS
1309         help
1310           This makes debugging information from the lpfc driver
1311           available via the debugfs filesystem.
1312
1313 config SCSI_SIM710
1314         tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1315         depends on (EISA || MCA) && SCSI
1316         select SCSI_SPI_ATTRS
1317         ---help---
1318           This driver is for NCR53c710 based SCSI host adapters.
1319
1320           It currently supports Compaq EISA cards and NCR MCA cards
1321
1322 config SCSI_SYM53C416
1323         tristate "Symbios 53c416 SCSI support"
1324         depends on ISA && SCSI
1325         ---help---
1326           This is support for the sym53c416 SCSI host adapter, the SCSI
1327           adapter that comes with some HP scanners. This driver requires that
1328           the sym53c416 is configured first using some sort of PnP
1329           configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
1330           are using isapnp then you need to compile this driver as a module
1331           and then load it using insmod after isapnp has run. The parameters
1332           of the configured card(s) should be passed to the driver. The format
1333           is:
1334
1335           insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
1336
1337           To compile this driver as a module, choose M here: the
1338           module will be called sym53c416.
1339
1340 config SCSI_DC395x
1341         tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1342         depends on PCI && SCSI
1343         ---help---
1344           This driver supports PCI SCSI host adapters based on the ASIC
1345           TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1346
1347           This driver works, but is still in experimental status. So better
1348           have a bootable disk and a backup in case of emergency.
1349
1350           Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
1351
1352           To compile this driver as a module, choose M here: the
1353           module will be called dc395x.
1354
1355 config SCSI_AM53C974
1356         tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1357         depends on PCI && SCSI
1358         select SCSI_SPI_ATTRS
1359         ---help---
1360           This driver supports PCI SCSI host adapters based on the Am53C974A
1361           chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1362           PCscsi/PCnet (Am53/79C974) solutions.
1363           This is a new implementation base on the generic esp_scsi driver.
1364
1365           Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1366
1367           Note that this driver does NOT support Tekram DC390W/U/F, which are
1368           based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1369
1370           To compile this driver as a module, choose M here: the
1371           module will be called am53c974.
1372
1373 config SCSI_T128
1374         tristate "Trantor T128/T128F/T228 SCSI support"
1375         depends on ISA && SCSI
1376         select SCSI_SPI_ATTRS
1377         select CHECK_SIGNATURE
1378         ---help---
1379           This is support for a SCSI host adapter. It is explained in section
1380           3.11 of the SCSI-HOWTO, available from
1381           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1382           of the box, you may have to change some settings in
1383           <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
1384           Adaptec, and some former Trantor products are being sold under the
1385           Adaptec name.
1386
1387           To compile this driver as a module, choose M here: the
1388           module will be called t128.
1389
1390 config SCSI_U14_34F
1391         tristate "UltraStor 14F/34F support"
1392         depends on ISA && SCSI && ISA_DMA_API
1393         ---help---
1394           This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
1395           The source at <file:drivers/scsi/u14-34f.c> contains some
1396           information about this hardware.  If the driver doesn't work out of
1397           the box, you may have to change some settings in
1398           <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
1399           <http://www.tldp.org/docs.html#howto>.  Note that there is also
1400           another driver for the same hardware: "UltraStor SCSI support",
1401           below.  You should say Y to both only if you want 24F support as
1402           well.
1403
1404           To compile this driver as a module, choose M here: the
1405           module will be called u14-34f.
1406
1407 config SCSI_U14_34F_TAGGED_QUEUE
1408         bool "enable tagged command queueing"
1409         depends on SCSI_U14_34F
1410         help
1411           This is a feature of SCSI-2 which improves performance: the host
1412           adapter can send several SCSI commands to a device's queue even if
1413           previous commands haven't finished yet.
1414           This is equivalent to the "u14-34f=tc:y" boot option.
1415
1416 config SCSI_U14_34F_LINKED_COMMANDS
1417         bool "enable elevator sorting"
1418         depends on SCSI_U14_34F
1419         help
1420           This option enables elevator sorting for all probed SCSI disks and
1421           CD-ROMs. It definitely reduces the average seek distance when doing
1422           random seeks, but this does not necessarily result in a noticeable
1423           performance improvement: your mileage may vary...
1424           This is equivalent to the "u14-34f=lc:y" boot option.
1425
1426 config SCSI_U14_34F_MAX_TAGS
1427         int "maximum number of queued commands"
1428         depends on SCSI_U14_34F
1429         default "8"
1430         help
1431           This specifies how many SCSI commands can be maximally queued for
1432           each probed SCSI device. You should reduce the default value of 8
1433           only if you have disks with buggy or limited tagged command support.
1434           Minimum is 2 and maximum is 14. This value is also the window size
1435           used by the elevator sorting option above. The effective value used
1436           by the driver for each probed SCSI device is reported at boot time.
1437           This is equivalent to the "u14-34f=mq:8" boot option.
1438
1439 config SCSI_ULTRASTOR
1440         tristate "UltraStor SCSI support"
1441         depends on X86 && ISA && SCSI
1442         ---help---
1443           This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
1444           adapter family.  This driver is explained in section 3.12 of the
1445           SCSI-HOWTO, available from
1446           <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1447           of the box, you may have to change some settings in
1448           <file:drivers/scsi/ultrastor.h>.
1449
1450           Note that there is also another driver for the same hardware:
1451           "UltraStor 14F/34F support", above.
1452
1453           To compile this driver as a module, choose M here: the
1454           module will be called ultrastor.
1455
1456 config SCSI_NSP32
1457         tristate "Workbit NinjaSCSI-32Bi/UDE support"
1458         depends on PCI && SCSI && !64BIT
1459         help
1460           This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1461           SCSI host adapter. Please read the SCSI-HOWTO, available from
1462           <http://www.tldp.org/docs.html#howto>.
1463
1464           To compile this driver as a module, choose M here: the
1465           module will be called nsp32.
1466
1467 config SCSI_WD719X
1468         tristate "Western Digital WD7193/7197/7296 support"
1469         depends on PCI && SCSI
1470         select EEPROM_93CX6
1471         ---help---
1472           This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1473           SCSI controllers (based on WD33C296A chip).
1474
1475 config SCSI_DEBUG
1476         tristate "SCSI debugging host and device simulator"
1477         depends on SCSI
1478         select CRC_T10DIF
1479         help
1480           This pseudo driver simulates one or more hosts (SCSI initiators),
1481           each with one or more targets, each with one or more logical units.
1482           Defaults to one of each, creating a small RAM disk device. Many
1483           parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1484           directory can be tweaked at run time.
1485           See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1486           Mainly used for testing and best as a module. If unsure, say N.
1487
1488 config SCSI_MESH
1489         tristate "MESH (Power Mac internal SCSI) support"
1490         depends on PPC32 && PPC_PMAC && SCSI
1491         help
1492           Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1493           SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1494           other Power Macintoshes do). Say Y to include support for this SCSI
1495           adaptor.
1496
1497           To compile this driver as a module, choose M here: the
1498           module will be called mesh.
1499
1500 config SCSI_MESH_SYNC_RATE
1501         int "maximum synchronous transfer rate (MB/s) (0 = async)"
1502         depends on SCSI_MESH
1503         default "5"
1504         help
1505           On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1506           drives a bus which is entirely internal to the machine (such as the
1507           7500, 7600, 8500, etc.), the MESH is capable of synchronous
1508           operation at up to 10 MB/s. On machines where the SCSI bus
1509           controlled by the MESH can have external devices connected, it is
1510           usually rated at 5 MB/s. 5 is a safe value here unless you know the
1511           MESH SCSI bus is internal only; in that case you can say 10. Say 0
1512           to disable synchronous operation.
1513
1514 config SCSI_MESH_RESET_DELAY_MS
1515         int "initial bus reset delay (ms) (0 = no reset)"
1516         depends on SCSI_MESH
1517         default "4000"
1518
1519 config SCSI_MAC53C94
1520         tristate "53C94 (Power Mac external SCSI) support"
1521         depends on PPC32 && PPC_PMAC && SCSI
1522         help
1523           On Power Macintoshes (and clones) with two SCSI buses, the external
1524           SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1525           machines which only have one SCSI bus, such as the 7200, also use
1526           the 53C94. Say Y to include support for the 53C94.
1527
1528           To compile this driver as a module, choose M here: the
1529           module will be called mac53c94.
1530
1531 source "drivers/scsi/arm/Kconfig"
1532
1533 config JAZZ_ESP
1534         bool "MIPS JAZZ FAS216 SCSI support"
1535         depends on MACH_JAZZ && SCSI
1536         select SCSI_SPI_ATTRS
1537         help
1538           This is the driver for the onboard SCSI host adapter of MIPS Magnum
1539           4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1540           systems.
1541
1542 config A3000_SCSI
1543         tristate "A3000 WD33C93A support"
1544         depends on AMIGA && SCSI
1545         help
1546           If you have an Amiga 3000 and have SCSI devices connected to the
1547           built-in SCSI controller, say Y. Otherwise, say N.
1548
1549           To compile this driver as a module, choose M here: the
1550           module will be called a3000.
1551
1552 config A2091_SCSI
1553         tristate "A2091/A590 WD33C93A support"
1554         depends on ZORRO && SCSI
1555         help
1556           If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1557           say N.
1558
1559           To compile this driver as a module, choose M here: the
1560           module will be called a2091.
1561
1562 config GVP11_SCSI
1563         tristate "GVP Series II WD33C93A support"
1564         depends on ZORRO && SCSI
1565         ---help---
1566           If you have a Great Valley Products Series II SCSI controller,
1567           answer Y. Also say Y if you have a later model of GVP SCSI
1568           controller (such as the GVP A4008 or a Combo board). Otherwise,
1569           answer N. This driver does NOT work for the T-Rex series of
1570           accelerators from TekMagic and GVP-M.
1571
1572           To compile this driver as a module, choose M here: the
1573           module will be called gvp11.
1574
1575 config SCSI_A4000T
1576         tristate "A4000T NCR53c710 SCSI support"
1577         depends on AMIGA && SCSI
1578         select SCSI_SPI_ATTRS
1579         help
1580           If you have an Amiga 4000T and have SCSI devices connected to the
1581           built-in SCSI controller, say Y. Otherwise, say N.
1582
1583           To compile this driver as a module, choose M here: the
1584           module will be called a4000t.
1585
1586 config SCSI_ZORRO7XX
1587         tristate "Zorro NCR53c710 SCSI support"
1588         depends on ZORRO && SCSI
1589         select SCSI_SPI_ATTRS
1590         help
1591           Support for various NCR53c710-based SCSI controllers on Zorro
1592           expansion boards for the Amiga.
1593           This includes:
1594             - the Amiga 4091 Zorro III SCSI-2 controller,
1595             - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1596               (info at
1597               <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1598             - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1599               accelerator card for the Amiga 1200,
1600             - the SCSI controller on the GVP Turbo 040/060 accelerator.
1601
1602 config ATARI_SCSI
1603         tristate "Atari native SCSI support"
1604         depends on ATARI && SCSI
1605         select SCSI_SPI_ATTRS
1606         select NVRAM
1607         ---help---
1608           If you have an Atari with built-in NCR5380 SCSI controller (TT,
1609           Falcon, ...) say Y to get it supported. Of course also, if you have
1610           a compatible SCSI controller (e.g. for Medusa).
1611
1612           To compile this driver as a module, choose M here: the
1613           module will be called atari_scsi.
1614
1615           This driver supports both styles of NCR integration into the
1616           system: the TT style (separate DMA), and the Falcon style (via
1617           ST-DMA, replacing ACSI).  It does NOT support other schemes, like
1618           in the Hades (without DMA).
1619
1620 config ATARI_SCSI_TOSHIBA_DELAY
1621         bool "Long delays for Toshiba CD-ROMs"
1622         depends on ATARI_SCSI
1623         help
1624           This option increases the delay after a SCSI arbitration to
1625           accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1626           use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1627           would impact performance a bit, so say N.
1628
1629 config ATARI_SCSI_RESET_BOOT
1630         bool "Reset SCSI-devices at boottime"
1631         depends on ATARI_SCSI
1632         help
1633           Reset the devices on your Atari whenever it boots.  This makes the
1634           boot process fractionally longer but may assist recovery from errors
1635           that leave the devices with SCSI operations partway completed.
1636
1637 config MAC_SCSI
1638         tristate "Macintosh NCR5380 SCSI"
1639         depends on MAC && SCSI=y
1640         select SCSI_SPI_ATTRS
1641         help
1642           This is the NCR 5380 SCSI controller included on most of the 68030
1643           based Macintoshes.  If you have one of these say Y and read the
1644           SCSI-HOWTO, available from
1645           <http://www.tldp.org/docs.html#howto>.
1646
1647 config SCSI_MAC_ESP
1648         tristate "Macintosh NCR53c9[46] SCSI"
1649         depends on MAC && SCSI
1650         select SCSI_SPI_ATTRS
1651         help
1652           This is the NCR 53c9x SCSI controller found on most of the 68040
1653           based Macintoshes.
1654
1655           To compile this driver as a module, choose M here: the module
1656           will be called mac_esp.
1657
1658 config MVME147_SCSI
1659         bool "WD33C93 SCSI driver for MVME147"
1660         depends on MVME147 && SCSI=y
1661         select SCSI_SPI_ATTRS
1662         help
1663           Support for the on-board SCSI controller on the Motorola MVME147
1664           single-board computer.
1665
1666 config MVME16x_SCSI
1667         tristate "NCR53C710 SCSI driver for MVME16x"
1668         depends on MVME16x && SCSI
1669         select SCSI_SPI_ATTRS
1670         help
1671           The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1672           SCSI controller chip.  Almost everyone using one of these boards
1673           will want to say Y to this question.
1674
1675 config BVME6000_SCSI
1676         tristate "NCR53C710 SCSI driver for BVME6000"
1677         depends on BVME6000 && SCSI
1678         select SCSI_SPI_ATTRS
1679         help
1680           The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1681           SCSI controller chip.  Almost everyone using one of these boards
1682           will want to say Y to this question.
1683
1684 config SUN3_SCSI
1685         tristate "Sun3 NCR5380 SCSI"
1686         depends on SUN3 && SCSI
1687         select SCSI_SPI_ATTRS
1688         help
1689           This option will enable support for the OBIO (onboard io) NCR5380
1690           SCSI controller found in the Sun 3/50 and 3/60, as well as for
1691           "Sun3" type VME scsi controllers also based on the NCR5380.
1692           General Linux information on the Sun 3 series (now discontinued)
1693           is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1694
1695 config SUN3X_ESP
1696         bool "Sun3x ESP SCSI"
1697         depends on SUN3X && SCSI=y
1698         select SCSI_SPI_ATTRS
1699         help
1700           The ESP was an on-board SCSI controller used on Sun 3/80
1701           machines.  Say Y here to compile in support for it.
1702
1703 config SCSI_SUNESP
1704         tristate "Sparc ESP Scsi Driver"
1705         depends on SBUS && SCSI
1706         select SCSI_SPI_ATTRS
1707         help
1708           This is the driver for the Sun ESP SCSI host adapter. The ESP
1709           chipset is present in most SPARC SBUS-based computers and
1710           supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1711           esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1712
1713           To compile this driver as a module, choose M here: the
1714           module will be called sun_esp.
1715
1716 config ZFCP
1717         tristate "FCP host bus adapter driver for IBM eServer zSeries"
1718         depends on S390 && QDIO && SCSI
1719         depends on SCSI_FC_ATTRS
1720         help
1721           If you want to access SCSI devices attached to your IBM eServer
1722           zSeries by means of Fibre Channel interfaces say Y.
1723           For details please refer to the documentation provided by IBM at
1724           <http://oss.software.ibm.com/developerworks/opensource/linux390>
1725
1726           This driver is also available as a module. This module will be
1727           called zfcp. If you want to compile it as a module, say M here
1728           and read <file:Documentation/kbuild/modules.txt>.
1729
1730 config SCSI_PMCRAID
1731         tristate "PMC SIERRA Linux MaxRAID adapter support"
1732         depends on PCI && SCSI && NET
1733         ---help---
1734           This driver supports the PMC SIERRA MaxRAID adapters.
1735
1736 config SCSI_PM8001
1737         tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1738         depends on PCI && SCSI
1739         select SCSI_SAS_LIBSAS
1740         help
1741           This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1742           based host adapters.
1743
1744 config SCSI_BFA_FC
1745         tristate "Brocade BFA Fibre Channel Support"
1746         depends on PCI && SCSI
1747         depends on SCSI_FC_ATTRS
1748         help
1749           This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1750
1751           To compile this driver as a module, choose M here. The module will
1752           be called bfa.
1753
1754 config SCSI_VIRTIO
1755         tristate "virtio-scsi support"
1756         depends on VIRTIO
1757         help
1758           This is the virtual HBA driver for virtio.  If the kernel will
1759           be used in a virtual machine, say Y or M.
1760
1761 source "drivers/scsi/csiostor/Kconfig"
1762
1763 endif # SCSI_LOWLEVEL
1764
1765 source "drivers/scsi/pcmcia/Kconfig"
1766
1767 source "drivers/scsi/device_handler/Kconfig"
1768
1769 source "drivers/scsi/osd/Kconfig"
1770
1771 endmenu