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