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