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