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