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