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