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