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