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