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