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/megaraid/Kconfig.megaraid" 605source "drivers/scsi/mpt2sas/Kconfig" 606source "drivers/scsi/mpt3sas/Kconfig" 607source "drivers/scsi/ufs/Kconfig" 608 609config SCSI_HPTIOP 610 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support" 611 depends on SCSI && PCI 612 help 613 This option enables support for HighPoint RocketRAID 3xxx/4xxx 614 controllers. 615 616 To compile this driver as a module, choose M here; the module 617 will be called hptiop. If unsure, say N. 618 619config SCSI_BUSLOGIC 620 tristate "BusLogic SCSI support" 621 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS 622 ---help--- 623 This is support for BusLogic MultiMaster and FlashPoint SCSI Host 624 Adapters. Consult the SCSI-HOWTO, available from 625 <http://www.tldp.org/docs.html#howto>, and the files 626 <file:Documentation/scsi/BusLogic.txt> and 627 <file:Documentation/scsi/FlashPoint.txt> for more information. 628 Note that support for FlashPoint is only available for 32-bit 629 x86 configurations. 630 631 To compile this driver as a module, choose M here: the 632 module will be called BusLogic. 633 634config SCSI_FLASHPOINT 635 bool "FlashPoint support" 636 depends on SCSI_BUSLOGIC && PCI 637 help 638 This option allows you to add FlashPoint support to the 639 BusLogic SCSI driver. The FlashPoint SCCB Manager code is 640 substantial, so users of MultiMaster Host Adapters may not 641 wish to include it. 642 643config VMWARE_PVSCSI 644 tristate "VMware PVSCSI driver support" 645 depends on PCI && SCSI && X86 646 help 647 This driver supports VMware's para virtualized SCSI HBA. 648 To compile this driver as a module, choose M here: the 649 module will be called vmw_pvscsi. 650 651config HYPERV_STORAGE 652 tristate "Microsoft Hyper-V virtual storage driver" 653 depends on SCSI && HYPERV 654 default HYPERV 655 help 656 Select this option to enable the Hyper-V virtual storage driver. 657 658config LIBFC 659 tristate "LibFC module" 660 select SCSI_FC_ATTRS 661 select CRC32 662 ---help--- 663 Fibre Channel library module 664 665config LIBFCOE 666 tristate "LibFCoE module" 667 select LIBFC 668 ---help--- 669 Library for Fibre Channel over Ethernet module 670 671config FCOE 672 tristate "FCoE module" 673 depends on PCI 674 select LIBFCOE 675 ---help--- 676 Fibre Channel over Ethernet module 677 678config FCOE_FNIC 679 tristate "Cisco FNIC Driver" 680 depends on PCI && X86 681 select LIBFCOE 682 help 683 This is support for the Cisco PCI-Express FCoE HBA. 684 685 To compile this driver as a module, choose M here and read 686 <file:Documentation/scsi/scsi.txt>. 687 The module will be called fnic. 688 689config SCSI_DMX3191D 690 tristate "DMX3191D SCSI support" 691 depends on PCI && SCSI 692 select SCSI_SPI_ATTRS 693 help 694 This is support for Domex DMX3191D SCSI Host Adapters. 695 696 To compile this driver as a module, choose M here: the 697 module will be called dmx3191d. 698 699config SCSI_DTC3280 700 tristate "DTC3180/3280 SCSI support" 701 depends on ISA && SCSI 702 select SCSI_SPI_ATTRS 703 select CHECK_SIGNATURE 704 help 705 This is support for DTC 3180/3280 SCSI Host Adapters. Please read 706 the SCSI-HOWTO, available from 707 <http://www.tldp.org/docs.html#howto>, and the file 708 <file:Documentation/scsi/dtc3x80.txt>. 709 710 To compile this driver as a module, choose M here: the 711 module will be called dtc. 712 713config SCSI_EATA 714 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support" 715 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API 716 ---help--- 717 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT 718 ISA and all EISA I/O addresses are probed looking for the "EATA" 719 signature. The addresses of all the PCI SCSI controllers reported 720 by the PCI subsystem are probed as well. 721 722 You want to read the start of <file:drivers/scsi/eata.c> and the 723 SCSI-HOWTO, available from 724 <http://www.tldp.org/docs.html#howto>. 725 726 To compile this driver as a module, choose M here: the 727 module will be called eata. 728 729config SCSI_EATA_TAGGED_QUEUE 730 bool "enable tagged command queueing" 731 depends on SCSI_EATA 732 help 733 This is a feature of SCSI-2 which improves performance: the host 734 adapter can send several SCSI commands to a device's queue even if 735 previous commands haven't finished yet. 736 This is equivalent to the "eata=tc:y" boot option. 737 738config SCSI_EATA_LINKED_COMMANDS 739 bool "enable elevator sorting" 740 depends on SCSI_EATA 741 help 742 This option enables elevator sorting for all probed SCSI disks and 743 CD-ROMs. It definitely reduces the average seek distance when doing 744 random seeks, but this does not necessarily result in a noticeable 745 performance improvement: your mileage may vary... 746 This is equivalent to the "eata=lc:y" boot option. 747 748config SCSI_EATA_MAX_TAGS 749 int "maximum number of queued commands" 750 depends on SCSI_EATA 751 default "16" 752 help 753 This specifies how many SCSI commands can be maximally queued for 754 each probed SCSI device. You should reduce the default value of 16 755 only if you have disks with buggy or limited tagged command support. 756 Minimum is 2 and maximum is 62. This value is also the window size 757 used by the elevator sorting option above. The effective value used 758 by the driver for each probed SCSI device is reported at boot time. 759 This is equivalent to the "eata=mq:8" boot option. 760 761config SCSI_EATA_PIO 762 tristate "EATA-PIO (old DPT PM2001, PM2012A) support" 763 depends on (ISA || EISA || PCI) && SCSI && BROKEN 764 ---help--- 765 This driver supports all EATA-PIO protocol compliant SCSI Host 766 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant 767 host adapters could also use this driver but are discouraged from 768 doing so, since this driver only supports hard disks and lacks 769 numerous features. You might want to have a look at the SCSI-HOWTO, 770 available from <http://www.tldp.org/docs.html#howto>. 771 772 To compile this driver as a module, choose M here: the 773 module will be called eata_pio. 774 775config SCSI_FUTURE_DOMAIN 776 tristate "Future Domain 16xx SCSI/AHA-2920A support" 777 depends on (ISA || PCI) && SCSI 778 select CHECK_SIGNATURE 779 ---help--- 780 This is support for Future Domain's 16-bit SCSI host adapters 781 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and 782 other adapters based on the Future Domain chipsets (Quantum 783 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board). 784 It is explained in section 3.7 of the SCSI-HOWTO, available from 785 <http://www.tldp.org/docs.html#howto>. 786 787 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip 788 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI 789 controller support"). This Future Domain driver works with the older 790 Adaptec AHA-2920A boards with a Future Domain chip on them. 791 792 To compile this driver as a module, choose M here: the 793 module will be called fdomain. 794 795config SCSI_GDTH 796 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support" 797 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API 798 ---help--- 799 Formerly called GDT SCSI Disk Array Controller Support. 800 801 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 802 manufactured by Intel Corporation/ICP vortex GmbH. It is documented 803 in the kernel source in <file:drivers/scsi/gdth.c> and 804 <file:drivers/scsi/gdth.h>. 805 806 To compile this driver as a module, choose M here: the 807 module will be called gdth. 808 809config SCSI_ISCI 810 tristate "Intel(R) C600 Series Chipset SAS Controller" 811 depends on PCI && SCSI 812 depends on X86 813 select SCSI_SAS_LIBSAS 814 ---help--- 815 This driver supports the 6Gb/s SAS capabilities of the storage 816 control unit found in the Intel(R) C600 series chipset. 817 818config SCSI_GENERIC_NCR5380 819 tristate "Generic NCR5380/53c400 SCSI PIO support" 820 depends on ISA && SCSI 821 select SCSI_SPI_ATTRS 822 ---help--- 823 This is a driver for the old NCR 53c80 series of SCSI controllers 824 on boards using PIO. Most boards such as the Trantor T130 fit this 825 category, along with a large number of ISA 8bit controllers shipped 826 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191 827 you should select the specific driver for that card rather than 828 generic 5380 support. 829 830 It is explained in section 3.8 of the SCSI-HOWTO, available from 831 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 832 of the box, you may have to change some settings in 833 <file:drivers/scsi/g_NCR5380.h>. 834 835 To compile this driver as a module, choose M here: the 836 module will be called g_NCR5380. 837 838config SCSI_GENERIC_NCR5380_MMIO 839 tristate "Generic NCR5380/53c400 SCSI MMIO support" 840 depends on ISA && SCSI 841 select SCSI_SPI_ATTRS 842 ---help--- 843 This is a driver for the old NCR 53c80 series of SCSI controllers 844 on boards using memory mapped I/O. 845 It is explained in section 3.8 of the SCSI-HOWTO, available from 846 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 847 of the box, you may have to change some settings in 848 <file:drivers/scsi/g_NCR5380.h>. 849 850 To compile this driver as a module, choose M here: the 851 module will be called g_NCR5380_mmio. 852 853config SCSI_GENERIC_NCR53C400 854 bool "Enable NCR53c400 extensions" 855 depends on SCSI_GENERIC_NCR5380 856 help 857 This enables certain optimizations for the NCR53c400 SCSI cards. 858 You might as well try it out. Note that this driver will only probe 859 for the Trantor T130B in its default configuration; you might have 860 to pass a command line option to the kernel at boot time if it does 861 not detect your card. See the file 862 <file:Documentation/scsi/g_NCR5380.txt> for details. 863 864config SCSI_IPS 865 tristate "IBM ServeRAID support" 866 depends on PCI && SCSI 867 ---help--- 868 This is support for the IBM ServeRAID hardware RAID controllers. 869 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html> 870 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID> 871 for more information. If this driver does not work correctly 872 without modification please contact the author by email at 873 <ipslinux@adaptec.com>. 874 875 To compile this driver as a module, choose M here: the 876 module will be called ips. 877 878config SCSI_IBMVSCSI 879 tristate "IBM Virtual SCSI support" 880 depends on PPC_PSERIES 881 select SCSI_SRP_ATTRS 882 help 883 This is the IBM POWER Virtual SCSI Client 884 885 To compile this driver as a module, choose M here: the 886 module will be called ibmvscsi. 887 888config SCSI_IBMVSCSIS 889 tristate "IBM Virtual SCSI Server support" 890 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS 891 help 892 This is the SRP target driver for IBM pSeries virtual environments. 893 894 The userspace component needed to initialize the driver and 895 documentation can be found: 896 897 http://stgt.berlios.de/ 898 899 To compile this driver as a module, choose M here: the 900 module will be called ibmvstgt. 901 902config SCSI_IBMVFC 903 tristate "IBM Virtual FC support" 904 depends on PPC_PSERIES && SCSI 905 select SCSI_FC_ATTRS 906 help 907 This is the IBM POWER Virtual FC Client 908 909 To compile this driver as a module, choose M here: the 910 module will be called ibmvfc. 911 912config SCSI_IBMVFC_TRACE 913 bool "enable driver internal trace" 914 depends on SCSI_IBMVFC 915 default y 916 help 917 If you say Y here, the driver will trace all commands issued 918 to the adapter. Performance impact is minimal. Trace can be 919 dumped using /sys/class/scsi_host/hostXX/trace. 920 921config SCSI_INITIO 922 tristate "Initio 9100U(W) support" 923 depends on PCI && SCSI 924 help 925 This is support for the Initio 91XXU(W) SCSI host adapter. Please 926 read the SCSI-HOWTO, available from 927 <http://www.tldp.org/docs.html#howto>. 928 929 To compile this driver as a module, choose M here: the 930 module will be called initio. 931 932config SCSI_INIA100 933 tristate "Initio INI-A100U2W support" 934 depends on PCI && SCSI 935 help 936 This is support for the Initio INI-A100U2W SCSI host adapter. 937 Please read the SCSI-HOWTO, available from 938 <http://www.tldp.org/docs.html#howto>. 939 940 To compile this driver as a module, choose M here: the 941 module will be called a100u2w. 942 943config SCSI_PPA 944 tristate "IOMEGA parallel port (ppa - older drives)" 945 depends on SCSI && PARPORT_PC 946 ---help--- 947 This driver supports older versions of IOMEGA's parallel port ZIP 948 drive (a 100 MB removable media device). 949 950 Note that you can say N here if you have the SCSI version of the ZIP 951 drive: it will be supported automatically if you said Y to the 952 generic "SCSI disk support", above. 953 954 If you have the ZIP Plus drive or a more recent parallel port ZIP 955 drive (if the supplied cable with the drive is labeled "AutoDetect") 956 then you should say N here and Y to "IOMEGA parallel port (imm - 957 newer drives)", below. 958 959 For more information about this driver and how to use it you should 960 read the file <file:Documentation/scsi/ppa.txt>. You should also read 961 the SCSI-HOWTO, which is available from 962 <http://www.tldp.org/docs.html#howto>. If you use this driver, 963 you will still be able to use the parallel port for other tasks, 964 such as a printer; it is safe to compile both drivers into the 965 kernel. 966 967 To compile this driver as a module, choose M here: the 968 module will be called ppa. 969 970config SCSI_IMM 971 tristate "IOMEGA parallel port (imm - newer drives)" 972 depends on SCSI && PARPORT_PC 973 ---help--- 974 This driver supports newer versions of IOMEGA's parallel port ZIP 975 drive (a 100 MB removable media device). 976 977 Note that you can say N here if you have the SCSI version of the ZIP 978 drive: it will be supported automatically if you said Y to the 979 generic "SCSI disk support", above. 980 981 If you have the ZIP Plus drive or a more recent parallel port ZIP 982 drive (if the supplied cable with the drive is labeled "AutoDetect") 983 then you should say Y here; if you have an older ZIP drive, say N 984 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above. 985 986 For more information about this driver and how to use it you should 987 read the file <file:Documentation/scsi/ppa.txt>. You should also read 988 the SCSI-HOWTO, which is available from 989 <http://www.tldp.org/docs.html#howto>. If you use this driver, 990 you will still be able to use the parallel port for other tasks, 991 such as a printer; it is safe to compile both drivers into the 992 kernel. 993 994 To compile this driver as a module, choose M here: the 995 module will be called imm. 996 997config SCSI_IZIP_EPP16 998 bool "ppa/imm option - Use slow (but safe) EPP-16" 999 depends on SCSI_PPA || SCSI_IMM 1000 ---help--- 1001 EPP (Enhanced Parallel Port) is a standard for parallel ports which 1002 allows them to act as expansion buses that can handle up to 64 1003 peripheral devices. 1004 1005 Some parallel port chipsets are slower than their motherboard, and 1006 so we have to control the state of the chipset's FIFO queue every 1007 now and then to avoid data loss. This will be done if you say Y 1008 here. 1009 1010 Generally, saying Y is the safe option and slows things down a bit. 1011 1012config SCSI_IZIP_SLOW_CTR 1013 bool "ppa/imm option - Assume slow parport control register" 1014 depends on SCSI_PPA || SCSI_IMM 1015 help 1016 Some parallel ports are known to have excessive delays between 1017 changing the parallel port control register and good data being 1018 available on the parallel port data/status register. This option 1019 forces a small delay (1.0 usec to be exact) after changing the 1020 control register to let things settle out. Enabling this option may 1021 result in a big drop in performance but some very old parallel ports 1022 (found in 386 vintage machines) will not work properly. 1023 1024 Generally, saying N is fine. 1025 1026config SCSI_NCR53C406A 1027 tristate "NCR53c406a SCSI support" 1028 depends on ISA && SCSI 1029 help 1030 This is support for the NCR53c406a SCSI host adapter. For user 1031 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c> 1032 in the kernel source. Also read the SCSI-HOWTO, available from 1033 <http://www.tldp.org/docs.html#howto>. 1034 1035 To compile this driver as a module, choose M here: the 1036 module will be called NCR53c406. 1037 1038config SCSI_NCR_D700 1039 tristate "NCR Dual 700 MCA SCSI support" 1040 depends on MCA && SCSI 1041 select SCSI_SPI_ATTRS 1042 help 1043 This is a driver for the MicroChannel Dual 700 card produced by 1044 NCR and commonly used in 345x/35xx/4100 class machines. It always 1045 tries to negotiate sync and uses tag command queueing. 1046 1047 Unless you have an NCR manufactured machine, the chances are that 1048 you do not have this SCSI card, so say N. 1049 1050config SCSI_LASI700 1051 tristate "HP Lasi SCSI support for 53c700/710" 1052 depends on GSC && SCSI 1053 select SCSI_SPI_ATTRS 1054 help 1055 This is a driver for the SCSI controller in the Lasi chip found in 1056 many PA-RISC workstations & servers. If you do not know whether you 1057 have a Lasi chip, it is safe to say "Y" here. 1058 1059config SCSI_SNI_53C710 1060 tristate "SNI RM SCSI support for 53c710" 1061 depends on SNI_RM && SCSI 1062 select SCSI_SPI_ATTRS 1063 select 53C700_LE_ON_BE 1064 help 1065 This is a driver for the onboard SCSI controller found in older 1066 SNI RM workstations & servers. 1067 1068config 53C700_LE_ON_BE 1069 bool 1070 depends on SCSI_LASI700 1071 default y 1072 1073config SCSI_STEX 1074 tristate "Promise SuperTrak EX Series support" 1075 depends on PCI && SCSI 1076 ---help--- 1077 This driver supports Promise SuperTrak EX series storage controllers. 1078 1079 Promise provides Linux RAID configuration utility for these 1080 controllers. Please visit <http://www.promise.com> to download. 1081 1082 To compile this driver as a module, choose M here: the 1083 module will be called stex. 1084 1085config 53C700_BE_BUS 1086 bool 1087 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI 1088 default y 1089 1090config SCSI_SYM53C8XX_2 1091 tristate "SYM53C8XX Version 2 SCSI support" 1092 depends on PCI && SCSI 1093 select SCSI_SPI_ATTRS 1094 ---help--- 1095 This driver supports the whole NCR53C8XX/SYM53C8XX family of 1096 PCI-SCSI controllers. It also supports the subset of LSI53C10XX 1097 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS 1098 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI 1099 controllers; you need to use the Fusion MPT driver for that. 1100 1101 Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more 1102 information. 1103 1104config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE 1105 int "DMA addressing mode" 1106 depends on SCSI_SYM53C8XX_2 1107 default "1" 1108 ---help--- 1109 This option only applies to PCI-SCSI chips that are PCI DAC 1110 capable (875A, 895A, 896, 1010-33, 1010-66, 1000). 1111 1112 When set to 0, the driver will program the chip to only perform 1113 32-bit DMA. When set to 1, the chip will be able to perform DMA 1114 to addresses up to 1TB. When set to 2, the driver supports the 1115 full 64-bit DMA address range, but can only address 16 segments 1116 of 4 GB each. This limits the total addressable range to 64 GB. 1117 1118 Most machines with less than 4GB of memory should use a setting 1119 of 0 for best performance. If your machine has 4GB of memory 1120 or more, you should set this option to 1 (the default). 1121 1122 The still experimental value 2 (64 bit DMA addressing with 16 1123 x 4GB segments limitation) can be used on systems that require 1124 PCI address bits past bit 39 to be set for the addressing of 1125 memory using PCI DAC cycles. 1126 1127config SCSI_SYM53C8XX_DEFAULT_TAGS 1128 int "Default tagged command queue depth" 1129 depends on SCSI_SYM53C8XX_2 1130 default "16" 1131 help 1132 This is the default value of the command queue depth the 1133 driver will announce to the generic SCSI layer for devices 1134 that support tagged command queueing. This value can be changed 1135 from the boot command line. This is a soft limit that cannot 1136 exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS. 1137 1138config SCSI_SYM53C8XX_MAX_TAGS 1139 int "Maximum number of queued commands" 1140 depends on SCSI_SYM53C8XX_2 1141 default "64" 1142 help 1143 This option allows you to specify the maximum number of commands 1144 that can be queued to any device, when tagged command queuing is 1145 possible. The driver supports up to 256 queued commands per device. 1146 This value is used as a compiled-in hard limit. 1147 1148config SCSI_SYM53C8XX_MMIO 1149 bool "Use memory mapped IO" 1150 depends on SCSI_SYM53C8XX_2 1151 default y 1152 help 1153 Memory mapped IO is faster than Port IO. Most people should 1154 answer Y here, but some machines may have problems. If you have 1155 to answer N here, please report the problem to the maintainer. 1156 1157config SCSI_IPR 1158 tristate "IBM Power Linux RAID adapter support" 1159 depends on PCI && SCSI && ATA 1160 select FW_LOADER 1161 ---help--- 1162 This driver supports the IBM Power Linux family RAID adapters. 1163 This includes IBM pSeries 5712, 5703, 5709, and 570A, as well 1164 as IBM iSeries 5702, 5703, 5709, and 570A. 1165 1166config SCSI_IPR_TRACE 1167 bool "enable driver internal trace" 1168 depends on SCSI_IPR 1169 default y 1170 help 1171 If you say Y here, the driver will trace all commands issued 1172 to the adapter. Performance impact is minimal. Trace can be 1173 dumped using /sys/bus/class/scsi_host/hostXX/trace. 1174 1175config SCSI_IPR_DUMP 1176 bool "enable adapter dump support" 1177 depends on SCSI_IPR 1178 default y 1179 help 1180 If you say Y here, the driver will support adapter crash dump. 1181 If you enable this support, the iprdump daemon can be used 1182 to capture adapter failure analysis information. 1183 1184config SCSI_ZALON 1185 tristate "Zalon SCSI support" 1186 depends on GSC && SCSI 1187 select SCSI_SPI_ATTRS 1188 help 1189 The Zalon is a GSC/HSC bus interface chip that sits between the 1190 PA-RISC processor and the NCR 53c720 SCSI controller on C100, 1191 C110, J200, J210 and some D, K & R-class machines. It's also 1192 used on the add-in Bluefish, Barracuda & Shrike SCSI cards. 1193 Say Y here if you have one of these machines or cards. 1194 1195config SCSI_NCR_Q720 1196 tristate "NCR Quad 720 MCA SCSI support" 1197 depends on MCA && SCSI 1198 select SCSI_SPI_ATTRS 1199 help 1200 This is a driver for the MicroChannel Quad 720 card produced by 1201 NCR and commonly used in 345x/35xx/4100 class machines. It always 1202 tries to negotiate sync and uses tag command queueing. 1203 1204 Unless you have an NCR manufactured machine, the chances are that 1205 you do not have this SCSI card, so say N. 1206 1207config SCSI_NCR53C8XX_DEFAULT_TAGS 1208 int "default tagged command queue depth" 1209 depends on SCSI_ZALON || SCSI_NCR_Q720 1210 default "8" 1211 ---help--- 1212 "Tagged command queuing" is a feature of SCSI-2 which improves 1213 performance: the host adapter can send several SCSI commands to a 1214 device's queue even if previous commands haven't finished yet. 1215 Because the device is intelligent, it can optimize its operations 1216 (like head positioning) based on its own request queue. Some SCSI 1217 devices don't implement this properly; if you want to disable this 1218 feature, enter 0 or 1 here (it doesn't matter which). 1219 1220 The default value is 8 and should be supported by most hard disks. 1221 This value can be overridden from the boot command line using the 1222 'tags' option as follows (example): 1223 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 1224 4, set queue depth to 16 for target 2 and target 3 on controller 0 1225 and set queue depth to 10 for target 0 / lun 2 on controller 1. 1226 1227 The normal answer therefore is to go with the default 8 and to use 1228 a boot command line option for devices that need to use a different 1229 command queue depth. 1230 1231 There is no safe option other than using good SCSI devices. 1232 1233config SCSI_NCR53C8XX_MAX_TAGS 1234 int "maximum number of queued commands" 1235 depends on SCSI_ZALON || SCSI_NCR_Q720 1236 default "32" 1237 ---help--- 1238 This option allows you to specify the maximum number of commands 1239 that can be queued to any device, when tagged command queuing is 1240 possible. The default value is 32. Minimum is 2, maximum is 64. 1241 Modern hard disks are able to support 64 tags and even more, but 1242 do not seem to be faster when more than 32 tags are being used. 1243 1244 So, the normal answer here is to go with the default value 32 unless 1245 you are using very large hard disks with large cache (>= 1 MB) that 1246 are able to take advantage of more than 32 tagged commands. 1247 1248 There is no safe option and the default answer is recommended. 1249 1250config SCSI_NCR53C8XX_SYNC 1251 int "synchronous transfers frequency in MHz" 1252 depends on SCSI_ZALON || SCSI_NCR_Q720 1253 default "20" 1254 ---help--- 1255 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer 1256 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers 1257 are respectively the maximum data transfer rates in mega-transfers 1258 per second for each class. For example, a FAST-20 Wide 16 device is 1259 able to transfer data at 20 million 16 bit packets per second for a 1260 total rate of 40 MB/s. 1261 1262 You may specify 0 if you want to only use asynchronous data 1263 transfers. This is the safest and slowest option. Otherwise, specify 1264 a value between 5 and 80, depending on the capability of your SCSI 1265 controller. The higher the number, the faster the data transfer. 1266 Note that 80 should normally be ok since the driver decreases the 1267 value automatically according to the controller's capabilities. 1268 1269 Your answer to this question is ignored for controllers with NVRAM, 1270 since the driver will get this information from the user set-up. It 1271 also can be overridden using a boot setup option, as follows 1272 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate 1273 for FAST-20 synchronous data transfer (20 mega-transfers per 1274 second). 1275 1276 The normal answer therefore is not to go with the default but to 1277 select the maximum value 80 allowing the driver to use the maximum 1278 value supported by each controller. If this causes problems with 1279 your SCSI devices, you should come back and decrease the value. 1280 1281 There is no safe option other than using good cabling, right 1282 terminations and SCSI conformant devices. 1283 1284config SCSI_NCR53C8XX_NO_DISCONNECT 1285 bool "not allow targets to disconnect" 1286 depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0 1287 help 1288 This option is only provided for safety if you suspect some SCSI 1289 device of yours to not support properly the target-disconnect 1290 feature. In that case, you would say Y here. In general however, to 1291 not allow targets to disconnect is not reasonable if there is more 1292 than 1 device on a SCSI bus. The normal answer therefore is N. 1293 1294config SCSI_PAS16 1295 tristate "PAS16 SCSI support" 1296 depends on ISA && SCSI 1297 select SCSI_SPI_ATTRS 1298 ---help--- 1299 This is support for a SCSI host adapter. It is explained in section 1300 3.10 of the SCSI-HOWTO, available from 1301 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 1302 of the box, you may have to change some settings in 1303 <file:drivers/scsi/pas16.h>. 1304 1305 To compile this driver as a module, choose M here: the 1306 module will be called pas16. 1307 1308config SCSI_QLOGIC_FAS 1309 tristate "Qlogic FAS SCSI support" 1310 depends on ISA && SCSI 1311 ---help--- 1312 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic 1313 FastSCSI! cards as well as any other card based on the FASXX chip 1314 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards). 1315 1316 This driver does NOT support the PCI versions of these cards. The 1317 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP 1318 SCSI support"), below. 1319 1320 Information about this driver is contained in 1321 <file:Documentation/scsi/qlogicfas.txt>. You should also read the 1322 SCSI-HOWTO, available from 1323 <http://www.tldp.org/docs.html#howto>. 1324 1325 To compile this driver as a module, choose M here: the 1326 module will be called qlogicfas. 1327 1328config SCSI_QLOGIC_1280 1329 tristate "Qlogic QLA 1240/1x80/1x160 SCSI support" 1330 depends on PCI && SCSI 1331 help 1332 Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter. 1333 1334 To compile this driver as a module, choose M here: the 1335 module will be called qla1280. 1336 1337config SCSI_QLOGICPTI 1338 tristate "PTI Qlogic, ISP Driver" 1339 depends on SBUS && SCSI 1340 help 1341 This driver supports SBUS SCSI controllers from PTI or QLogic. These 1342 controllers are known under Solaris as qpti and in the openprom as 1343 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are 1344 driven by a different driver. 1345 1346 To compile this driver as a module, choose M here: the 1347 module will be called qlogicpti. 1348 1349source "drivers/scsi/qla2xxx/Kconfig" 1350source "drivers/scsi/qla4xxx/Kconfig" 1351 1352config SCSI_LPFC 1353 tristate "Emulex LightPulse Fibre Channel Support" 1354 depends on PCI && SCSI 1355 select SCSI_FC_ATTRS 1356 select GENERIC_CSUM 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