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