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