drivers/scsi/Kconfig

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