drivers/scsi/Kconfig

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