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