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