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