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