drivers/scsi/Kconfig

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