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