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