1menu "SCSI device support" 2 3config RAID_ATTRS 4 tristate "RAID Transport Class" 5 default n 6 depends on BLOCK 7 ---help--- 8 Provides RAID 9 10config SCSI 11 tristate "SCSI device support" 12 depends on BLOCK 13 select SCSI_DMA if HAS_DMA 14 ---help--- 15 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or 16 any other SCSI device under Linux, say Y and make sure that you know 17 the name of your SCSI host adapter (the card inside your computer 18 that "speaks" the SCSI protocol, also called SCSI controller), 19 because you will be asked for it. 20 21 You also need to say Y here if you have a device which speaks 22 the SCSI protocol. Examples of this include the parallel port 23 version of the IOMEGA ZIP drive, USB storage devices, Fibre 24 Channel, FireWire storage and the IDE-SCSI emulation driver. 25 26 To compile this driver as a module, choose M here and read 27 <file:Documentation/scsi/scsi.txt>. 28 The module will be called scsi_mod. 29 30 However, do not compile this as a module if your root file system 31 (the one containing the directory /) is located on a SCSI device. 32 33config SCSI_DMA 34 bool 35 default n 36 37config SCSI_TGT 38 tristate "SCSI target support" 39 depends on SCSI && EXPERIMENTAL 40 ---help--- 41 If you want to use SCSI target mode drivers enable this option. 42 If you choose M, the module will be called scsi_tgt. 43 44config SCSI_NETLINK 45 bool 46 default n 47 select NET 48 49config SCSI_PROC_FS 50 bool "legacy /proc/scsi/ support" 51 depends on SCSI && PROC_FS 52 default y 53 ---help--- 54 This option enables support for the various files in 55 /proc/scsi. In Linux 2.6 this has been superseded by 56 files in sysfs but many legacy applications rely on this. 57 58 If unsure say Y. 59 60comment "SCSI support type (disk, tape, CD-ROM)" 61 depends on SCSI 62 63config BLK_DEV_SD 64 tristate "SCSI disk support" 65 depends on SCSI 66 select CRC_T10DIF if BLK_DEV_INTEGRITY 67 ---help--- 68 If you want to use SCSI hard disks, Fibre Channel disks, 69 Serial ATA (SATA) or Parallel ATA (PATA) hard disks, 70 USB storage or the SCSI or parallel port version of 71 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO, 72 the Disk-HOWTO and the Multi-Disk-HOWTO, available from 73 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI 74 CD-ROMs. 75 76 To compile this driver as a module, choose M here and read 77 <file:Documentation/scsi/scsi.txt>. 78 The module will be called sd_mod. 79 80 Do not compile this driver as a module if your root file system 81 (the one containing the directory /) is located on a SCSI disk. 82 In this case, do not compile the driver for your SCSI host adapter 83 (below) as a module either. 84 85config CHR_DEV_ST 86 tristate "SCSI tape support" 87 depends on SCSI 88 ---help--- 89 If you want to use a SCSI tape drive under Linux, say Y and read the 90 SCSI-HOWTO, available from 91 <http://www.tldp.org/docs.html#howto>, and 92 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT 93 for SCSI CD-ROMs. 94 95 To compile this driver as a module, choose M here and read 96 <file:Documentation/scsi/scsi.txt>. The module will be called st. 97 98config CHR_DEV_OSST 99 tristate "SCSI OnStream SC-x0 tape support" 100 depends on SCSI 101 ---help--- 102 The OnStream SC-x0 SCSI tape drives cannot be driven by the 103 standard st driver, but instead need this special osst driver and 104 use the /dev/osstX char device nodes (major 206). Via usb-storage 105 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives 106 as well. Note that there is also a second generation of OnStream 107 tape drives (ADR-x0) that supports the standard SCSI-2 commands for 108 tapes (QIC-157) and can be driven by the standard driver st. 109 For more information, you may have a look at the SCSI-HOWTO 110 <http://www.tldp.org/docs.html#howto> and 111 <file:Documentation/scsi/osst.txt> in the kernel source. 112 More info on the OnStream driver may be found on 113 <http://linux1.onstream.nl/test/> 114 Please also have a look at the standard st docu, as most of it 115 applies to osst as well. 116 117 To compile this driver as a module, choose M here and read 118 <file:Documentation/scsi/scsi.txt>. The module will be called osst. 119 120config BLK_DEV_SR 121 tristate "SCSI CDROM support" 122 depends on SCSI 123 ---help--- 124 If you want to use a SCSI or FireWire CD-ROM under Linux, 125 say Y and read the SCSI-HOWTO and the CDROM-HOWTO at 126 <http://www.tldp.org/docs.html#howto>. Also make sure to say 127 Y or M to "ISO 9660 CD-ROM file system support" later. 128 129 To compile this driver as a module, choose M here and read 130 <file:Documentation/scsi/scsi.txt>. 131 The module will be called sr_mod. 132 133config BLK_DEV_SR_VENDOR 134 bool "Enable vendor-specific extensions (for SCSI CDROM)" 135 depends on BLK_DEV_SR 136 help 137 This enables the usage of vendor specific SCSI commands. This is 138 required to support multisession CDs with old NEC/TOSHIBA cdrom 139 drives (and HP Writers). If you have such a drive and get the first 140 session only, try saying Y here; everybody else says N. 141 142config CHR_DEV_SG 143 tristate "SCSI generic support" 144 depends on SCSI 145 ---help--- 146 If you want to use SCSI scanners, synthesizers or CD-writers or just 147 about anything having "SCSI" in its name other than hard disks, 148 CD-ROMs or tapes, say Y here. These won't be supported by the kernel 149 directly, so you need some additional software which knows how to 150 talk to these devices using the SCSI protocol: 151 152 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD 153 writer software look at Cdrtools 154 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>) 155 and for burning a "disk at once": CDRDAO 156 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high 157 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>). 158 For other devices, it's possible that you'll have to write the 159 driver software yourself. Please read the file 160 <file:Documentation/scsi/scsi-generic.txt> for more information. 161 162 To compile this driver as a module, choose M here and read 163 <file:Documentation/scsi/scsi.txt>. The module will be called sg. 164 165 If unsure, say N. 166 167config CHR_DEV_SCH 168 tristate "SCSI media changer support" 169 depends on SCSI 170 ---help--- 171 This is a driver for SCSI media changers. Most common devices are 172 tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you 173 don't need this for those tiny 6-slot cdrom changers. Media 174 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi. 175 If you have such hardware and want to use it with linux, say Y 176 here. Check <file:Documentation/scsi/scsi-changer.txt> for details. 177 178 If you want to compile this as a module ( = code which can be 179 inserted in and removed from the running kernel whenever you want), 180 say M here and read <file:Documentation/kbuild/modules.txt> and 181 <file:Documentation/scsi/scsi.txt>. The module will be called ch.o. 182 If unsure, say N. 183 184config SCSI_ENCLOSURE 185 tristate "SCSI Enclosure Support" 186 depends on SCSI && ENCLOSURE_SERVICES 187 help 188 Enclosures are devices sitting on or in SCSI backplanes that 189 manage devices. If you have a disk cage, the chances are that 190 it has an enclosure device. Selecting this option will just allow 191 certain enclosure conditions to be reported and is not required. 192 193comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs" 194 depends on SCSI 195 196config SCSI_MULTI_LUN 197 bool "Probe all LUNs on each SCSI device" 198 depends on SCSI 199 help 200 If you have a SCSI device that supports more than one LUN (Logical 201 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you 202 can say Y here to force the SCSI driver to probe for multiple LUNs. 203 A SCSI device with multiple LUNs acts logically like multiple SCSI 204 devices. The vast majority of SCSI devices have only one LUN, and 205 so most people can say N here. The max_luns boot/module parameter 206 allows to override this setting. 207 208config SCSI_CONSTANTS 209 bool "Verbose SCSI error reporting (kernel size +=12K)" 210 depends on SCSI 211 help 212 The error messages regarding your SCSI hardware will be easier to 213 understand if you say Y here; it will enlarge your kernel by about 214 12 KB. If in doubt, say Y. 215 216config SCSI_LOGGING 217 bool "SCSI logging facility" 218 depends on SCSI 219 ---help--- 220 This turns on a logging facility that can be used to debug a number 221 of SCSI related problems. 222 223 If you say Y here, no logging output will appear by default, but you 224 can enable logging by saying Y to "/proc file system support" and 225 "Sysctl support" below and executing the command 226 227 echo "scsi log token [level]" > /proc/scsi/scsi 228 229 at boot time after the /proc file system has been mounted. 230 231 There are a number of things that can be used for 'token' (you can 232 find them in the source: <file:drivers/scsi/scsi.c>), and this 233 allows you to select the types of information you want, and the 234 level allows you to select the level of verbosity. 235 236 If you say N here, it may be harder to track down some types of SCSI 237 problems. If you say Y here your kernel will be somewhat larger, but 238 there should be no noticeable performance impact as long as you have 239 logging turned off. 240 241config SCSI_SCAN_ASYNC 242 bool "Asynchronous SCSI scanning" 243 depends on SCSI 244 help 245 The SCSI subsystem can probe for devices while the rest of the 246 system continues booting, and even probe devices on different 247 busses in parallel, leading to a significant speed-up. 248 249 If you have built SCSI as modules, enabling this option can 250 be a problem as the devices may not have been found by the 251 time your system expects them to have been. You can load the 252 scsi_wait_scan module to ensure that all scans have completed. 253 If you build your SCSI drivers into the kernel, then everything 254 will work fine if you say Y here. 255 256 You can override this choice by specifying "scsi_mod.scan=sync" 257 or async on the kernel's command line. 258 259config SCSI_WAIT_SCAN 260 tristate 261 default m 262 depends on SCSI 263 depends on MODULES 264 265menu "SCSI Transports" 266 depends on SCSI 267 268config SCSI_SPI_ATTRS 269 tristate "Parallel SCSI (SPI) Transport Attributes" 270 depends on SCSI 271 help 272 If you wish to export transport-specific information about 273 each attached SCSI device to sysfs, say Y. Otherwise, say N. 274 275config SCSI_FC_ATTRS 276 tristate "FiberChannel Transport Attributes" 277 depends on SCSI 278 select SCSI_NETLINK 279 help 280 If you wish to export transport-specific information about 281 each attached FiberChannel device to sysfs, say Y. 282 Otherwise, say N. 283 284config SCSI_FC_TGT_ATTRS 285 bool "SCSI target support for FiberChannel Transport Attributes" 286 depends on SCSI_FC_ATTRS 287 depends on SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS 288 help 289 If you want to use SCSI target mode drivers enable this option. 290 291config SCSI_ISCSI_ATTRS 292 tristate "iSCSI Transport Attributes" 293 depends on SCSI && NET 294 help 295 If you wish to export transport-specific information about 296 each attached iSCSI device to sysfs, say Y. 297 Otherwise, say N. 298 299config SCSI_SAS_ATTRS 300 tristate "SAS Transport Attributes" 301 depends on SCSI && BLK_DEV_BSG 302 help 303 If you wish to export transport-specific information about 304 each attached SAS device to sysfs, say Y. 305 306source "drivers/scsi/libsas/Kconfig" 307 308config SCSI_SRP_ATTRS 309 tristate "SRP Transport Attributes" 310 depends on SCSI 311 help 312 If you wish to export transport-specific information about 313 each attached SRP device to sysfs, say Y. 314 315config SCSI_SRP_TGT_ATTRS 316 bool "SCSI target support for SRP Transport Attributes" 317 depends on SCSI_SRP_ATTRS 318 depends on SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS 319 help 320 If you want to use SCSI target mode drivers enable this option. 321 322endmenu 323 324menuconfig SCSI_LOWLEVEL 325 bool "SCSI low-level drivers" 326 depends on SCSI!=n 327 default y 328 329if SCSI_LOWLEVEL && SCSI 330 331config ISCSI_TCP 332 tristate "iSCSI Initiator over TCP/IP" 333 depends on SCSI && INET 334 select CRYPTO 335 select CRYPTO_MD5 336 select CRYPTO_CRC32C 337 select SCSI_ISCSI_ATTRS 338 help 339 The iSCSI Driver provides a host with the ability to access storage 340 through an IP network. The driver uses the iSCSI protocol to transport 341 SCSI requests and responses over a TCP/IP network between the host 342 (the "initiator") and "targets". Architecturally, the iSCSI driver 343 combines with the host's TCP/IP stack, network drivers, and Network 344 Interface Card (NIC) to provide the same functions as a SCSI or a 345 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA). 346 347 To compile this driver as a module, choose M here: the 348 module will be called iscsi_tcp. 349 350 The userspace component needed to initialize the driver, documentation, 351 and sample configuration files can be found here: 352 353 http://open-iscsi.org 354 355config SGIWD93_SCSI 356 tristate "SGI WD93C93 SCSI Driver" 357 depends on SGI_HAS_WD93 && SCSI 358 help 359 If you have a Western Digital WD93 SCSI controller on 360 an SGI MIPS system, say Y. Otherwise, say N. 361 362config BLK_DEV_3W_XXXX_RAID 363 tristate "3ware 5/6/7/8xxx ATA-RAID support" 364 depends on PCI && SCSI 365 help 366 3ware is the only hardware ATA-Raid product in Linux to date. 367 This card is 2,4, or 8 channel master mode support only. 368 SCSI support required!!! 369 370 <http://www.3ware.com/> 371 372 Please read the comments at the top of 373 <file:drivers/scsi/3w-xxxx.c>. 374 375config SCSI_3W_9XXX 376 tristate "3ware 9xxx SATA-RAID support" 377 depends on PCI && SCSI 378 help 379 This driver supports the 9000 series 3ware SATA-RAID cards. 380 381 <http://www.amcc.com> 382 383 Please read the comments at the top of 384 <file:drivers/scsi/3w-9xxx.c>. 385 386config SCSI_7000FASST 387 tristate "7000FASST SCSI support" 388 depends on ISA && SCSI && ISA_DMA_API 389 select CHECK_SIGNATURE 390 help 391 This driver supports the Western Digital 7000 SCSI host adapter 392 family. Some information is in the source: 393 <file:drivers/scsi/wd7000.c>. 394 395 To compile this driver as a module, choose M here: the 396 module will be called wd7000. 397 398config SCSI_ACARD 399 tristate "ACARD SCSI support" 400 depends on PCI && SCSI 401 help 402 This driver supports the ACARD SCSI host adapter. 403 Support Chip <ATP870 ATP876 ATP880 ATP885> 404 To compile this driver as a module, choose M here: the 405 module will be called atp870u. 406 407config SCSI_AHA152X 408 tristate "Adaptec AHA152X/2825 support" 409 depends on ISA && SCSI && !64BIT 410 select SCSI_SPI_ATTRS 411 select CHECK_SIGNATURE 412 ---help--- 413 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825 414 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc. 415 must be manually specified in this case. 416 417 It is explained in section 3.3 of the SCSI-HOWTO, available from 418 <http://www.tldp.org/docs.html#howto>. You might also want to 419 read the file <file:Documentation/scsi/aha152x.txt>. 420 421 To compile this driver as a module, choose M here: the 422 module will be called aha152x. 423 424config SCSI_AHA1542 425 tristate "Adaptec AHA1542 support" 426 depends on ISA && SCSI && ISA_DMA_API 427 ---help--- 428 This is support for a SCSI host adapter. It is explained in section 429 3.4 of the SCSI-HOWTO, available from 430 <http://www.tldp.org/docs.html#howto>. Note that Trantor was 431 purchased by Adaptec, and some former Trantor products are being 432 sold under the Adaptec name. If it doesn't work out of the box, you 433 may have to change some settings in <file:drivers/scsi/aha1542.h>. 434 435 To compile this driver as a module, choose M here: the 436 module will be called aha1542. 437 438config SCSI_AHA1740 439 tristate "Adaptec AHA1740 support" 440 depends on EISA && SCSI 441 ---help--- 442 This is support for a SCSI host adapter. It is explained in section 443 3.5 of the SCSI-HOWTO, available from 444 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 445 of the box, you may have to change some settings in 446 <file:drivers/scsi/aha1740.h>. 447 448 To compile this driver as a module, choose M here: the 449 module will be called aha1740. 450 451config SCSI_AACRAID 452 tristate "Adaptec AACRAID support" 453 depends on SCSI && PCI 454 help 455 This driver supports a variety of Dell, HP, Adaptec, IBM and 456 ICP storage products. For a list of supported products, refer 457 to <file:Documentation/scsi/aacraid.txt>. 458 459 To compile this driver as a module, choose M here: the module 460 will be called aacraid. 461 462 463source "drivers/scsi/aic7xxx/Kconfig.aic7xxx" 464 465config SCSI_AIC7XXX_OLD 466 tristate "Adaptec AIC7xxx support (old driver)" 467 depends on (ISA || EISA || PCI ) && SCSI 468 help 469 WARNING This driver is an older aic7xxx driver and is no longer 470 under active development. Adaptec, Inc. is writing a new driver to 471 take the place of this one, and it is recommended that whenever 472 possible, people should use the new Adaptec written driver instead 473 of this one. This driver will eventually be phased out entirely. 474 475 This is support for the various aic7xxx based Adaptec SCSI 476 controllers. These include the 274x EISA cards; 284x VLB cards; 477 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and 478 motherboard based SCSI controllers from Adaptec. It does not support 479 the AAA-13x RAID controllers from Adaptec, nor will it likely ever 480 support them. It does not support the 2920 cards from Adaptec that 481 use the Future Domain SCSI controller chip. For those cards, you 482 need the "Future Domain 16xx SCSI support" driver. 483 484 In general, if the controller is based on an Adaptec SCSI controller 485 chip from the aic777x series or the aic78xx series, this driver 486 should work. The only exception is the 7810 which is specifically 487 not supported (that's the RAID controller chip on the AAA-13x 488 cards). 489 490 Note that the AHA2920 SCSI host adapter is *not* supported by this 491 driver; choose "Future Domain 16xx SCSI support" instead if you have 492 one of those. 493 494 Information on the configuration options for this controller can be 495 found by checking the help file for each of the available 496 configuration options. You should read 497 <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before 498 contacting the maintainer with any questions. The SCSI-HOWTO, 499 available from <http://www.tldp.org/docs.html#howto>, can also 500 be of great help. 501 502 To compile this driver as a module, choose M here: the 503 module will be called aic7xxx_old. 504 505source "drivers/scsi/aic7xxx/Kconfig.aic79xx" 506source "drivers/scsi/aic94xx/Kconfig" 507 508config SCSI_DPT_I2O 509 tristate "Adaptec I2O RAID support " 510 depends on SCSI && PCI && VIRT_TO_BUS 511 help 512 This driver supports all of Adaptec's I2O based RAID controllers as 513 well as the DPT SmartRaid V cards. This is an Adaptec maintained 514 driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>. 515 516 To compile this driver as a module, choose M here: the 517 module will be called dpt_i2o. 518 519config SCSI_ADVANSYS 520 tristate "AdvanSys SCSI support" 521 depends on SCSI && VIRT_TO_BUS 522 depends on ISA || EISA || PCI 523 help 524 This is a driver for all SCSI host adapters manufactured by 525 AdvanSys. It is documented in the kernel source in 526 <file:drivers/scsi/advansys.c>. 527 528 To compile this driver as a module, choose M here: the 529 module will be called advansys. 530 531config SCSI_IN2000 532 tristate "Always IN2000 SCSI support" 533 depends on ISA && SCSI 534 help 535 This is support for an ISA bus SCSI host adapter. You'll find more 536 information in <file:Documentation/scsi/in2000.txt>. If it doesn't work 537 out of the box, you may have to change the jumpers for IRQ or 538 address selection. 539 540 To compile this driver as a module, choose M here: the 541 module will be called in2000. 542 543config SCSI_ARCMSR 544 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter" 545 depends on PCI && SCSI 546 help 547 This driver supports all of ARECA's SATA/SAS RAID controller cards. 548 This is an ARECA-maintained driver by Erich Chen. 549 If you have any problems, please mail to: <erich@areca.com.tw>. 550 Areca supports Linux RAID config tools. 551 Please link <http://www.areca.com.tw> 552 553 To compile this driver as a module, choose M here: the 554 module will be called arcmsr (modprobe arcmsr). 555 556config SCSI_ARCMSR_AER 557 bool "Enable PCI Error Recovery Capability in Areca Driver(ARCMSR)" 558 depends on SCSI_ARCMSR && PCIEAER 559 default n 560 help 561 The advanced error reporting(AER) capability is "NOT" provided by 562 ARC1200/1201/1202 SATA RAID controllers cards. 563 If your card is one of ARC1200/1201/1202, please use the default setting, n. 564 If your card is other models, you could pick it 565 on condition that the kernel version is greater than 2.6.19. 566 This function is maintained driver by Nick Cheng. If you have any 567 problems or suggestion, you are welcome to contact with <nick.cheng@areca.com.tw>. 568 To enable this function, choose Y here. 569 570source "drivers/scsi/megaraid/Kconfig.megaraid" 571 572config SCSI_HPTIOP 573 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support" 574 depends on SCSI && PCI 575 help 576 This option enables support for HighPoint RocketRAID 3xxx/4xxx 577 controllers. 578 579 To compile this driver as a module, choose M here; the module 580 will be called hptiop. If unsure, say N. 581 582config SCSI_BUSLOGIC 583 tristate "BusLogic SCSI support" 584 depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS 585 ---help--- 586 This is support for BusLogic MultiMaster and FlashPoint SCSI Host 587 Adapters. Consult the SCSI-HOWTO, available from 588 <http://www.tldp.org/docs.html#howto>, and the files 589 <file:Documentation/scsi/BusLogic.txt> and 590 <file:Documentation/scsi/FlashPoint.txt> for more information. 591 Note that support for FlashPoint is only available for 32-bit 592 x86 configurations. 593 594 To compile this driver as a module, choose M here: the 595 module will be called BusLogic. 596 597config SCSI_FLASHPOINT 598 bool "FlashPoint support" 599 depends on SCSI_BUSLOGIC && PCI && X86_32 600 help 601 This option allows you to add FlashPoint support to the 602 BusLogic SCSI driver. The FlashPoint SCCB Manager code is 603 substantial, so users of MultiMaster Host Adapters may not 604 wish to include it. 605 606config SCSI_DMX3191D 607 tristate "DMX3191D SCSI support" 608 depends on PCI && SCSI 609 select SCSI_SPI_ATTRS 610 help 611 This is support for Domex DMX3191D SCSI Host Adapters. 612 613 To compile this driver as a module, choose M here: the 614 module will be called dmx3191d. 615 616config SCSI_DTC3280 617 tristate "DTC3180/3280 SCSI support" 618 depends on ISA && SCSI 619 select SCSI_SPI_ATTRS 620 select CHECK_SIGNATURE 621 help 622 This is support for DTC 3180/3280 SCSI Host Adapters. Please read 623 the SCSI-HOWTO, available from 624 <http://www.tldp.org/docs.html#howto>, and the file 625 <file:Documentation/scsi/dtc3x80.txt>. 626 627 To compile this driver as a module, choose M here: the 628 module will be called dtc. 629 630config SCSI_EATA 631 tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support" 632 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API 633 ---help--- 634 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT 635 ISA and all EISA I/O addresses are probed looking for the "EATA" 636 signature. The addresses of all the PCI SCSI controllers reported 637 by the PCI subsystem are probed as well. 638 639 You want to read the start of <file:drivers/scsi/eata.c> and the 640 SCSI-HOWTO, available from 641 <http://www.tldp.org/docs.html#howto>. 642 643 To compile this driver as a module, choose M here: the 644 module will be called eata. 645 646config SCSI_EATA_TAGGED_QUEUE 647 bool "enable tagged command queueing" 648 depends on SCSI_EATA 649 help 650 This is a feature of SCSI-2 which improves performance: the host 651 adapter can send several SCSI commands to a device's queue even if 652 previous commands haven't finished yet. 653 This is equivalent to the "eata=tc:y" boot option. 654 655config SCSI_EATA_LINKED_COMMANDS 656 bool "enable elevator sorting" 657 depends on SCSI_EATA 658 help 659 This option enables elevator sorting for all probed SCSI disks and 660 CD-ROMs. It definitely reduces the average seek distance when doing 661 random seeks, but this does not necessarily result in a noticeable 662 performance improvement: your mileage may vary... 663 This is equivalent to the "eata=lc:y" boot option. 664 665config SCSI_EATA_MAX_TAGS 666 int "maximum number of queued commands" 667 depends on SCSI_EATA 668 default "16" 669 help 670 This specifies how many SCSI commands can be maximally queued for 671 each probed SCSI device. You should reduce the default value of 16 672 only if you have disks with buggy or limited tagged command support. 673 Minimum is 2 and maximum is 62. This value is also the window size 674 used by the elevator sorting option above. The effective value used 675 by the driver for each probed SCSI device is reported at boot time. 676 This is equivalent to the "eata=mq:8" boot option. 677 678config SCSI_EATA_PIO 679 tristate "EATA-PIO (old DPT PM2001, PM2012A) support" 680 depends on (ISA || EISA || PCI) && SCSI && BROKEN 681 ---help--- 682 This driver supports all EATA-PIO protocol compliant SCSI Host 683 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant 684 host adapters could also use this driver but are discouraged from 685 doing so, since this driver only supports hard disks and lacks 686 numerous features. You might want to have a look at the SCSI-HOWTO, 687 available from <http://www.tldp.org/docs.html#howto>. 688 689 To compile this driver as a module, choose M here: the 690 module will be called eata_pio. 691 692config SCSI_FUTURE_DOMAIN 693 tristate "Future Domain 16xx SCSI/AHA-2920A support" 694 depends on (ISA || PCI) && SCSI 695 select CHECK_SIGNATURE 696 ---help--- 697 This is support for Future Domain's 16-bit SCSI host adapters 698 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and 699 other adapters based on the Future Domain chipsets (Quantum 700 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board). 701 It is explained in section 3.7 of the SCSI-HOWTO, available from 702 <http://www.tldp.org/docs.html#howto>. 703 704 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip 705 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI 706 controller support"). This Future Domain driver works with the older 707 Adaptec AHA-2920A boards with a Future Domain chip on them. 708 709 To compile this driver as a module, choose M here: the 710 module will be called fdomain. 711 712config SCSI_FD_MCS 713 tristate "Future Domain MCS-600/700 SCSI support" 714 depends on MCA_LEGACY && SCSI 715 ---help--- 716 This is support for Future Domain MCS 600/700 MCA SCSI adapters. 717 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which 718 is identical to the MCS 700 and hence also supported by this driver. 719 This driver also supports the Reply SB16/SCSI card (the SCSI part). 720 It supports multiple adapters in the same system. 721 722 To compile this driver as a module, choose M here: the 723 module will be called fd_mcs. 724 725config SCSI_GDTH 726 tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support" 727 depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API 728 ---help--- 729 Formerly called GDT SCSI Disk Array Controller Support. 730 731 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 732 manufactured by Intel Corporation/ICP vortex GmbH. It is documented 733 in the kernel source in <file:drivers/scsi/gdth.c> and 734 <file:drivers/scsi/gdth.h>. 735 736 To compile this driver as a module, choose M here: the 737 module will be called gdth. 738 739config SCSI_GENERIC_NCR5380 740 tristate "Generic NCR5380/53c400 SCSI PIO support" 741 depends on ISA && SCSI 742 select SCSI_SPI_ATTRS 743 ---help--- 744 This is a driver for the old NCR 53c80 series of SCSI controllers 745 on boards using PIO. Most boards such as the Trantor T130 fit this 746 category, along with a large number of ISA 8bit controllers shipped 747 for free with SCSI scanners. If you have a PAS16, T128 or DMX3191 748 you should select the specific driver for that card rather than 749 generic 5380 support. 750 751 It is explained in section 3.8 of the SCSI-HOWTO, available from 752 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 753 of the box, you may have to change some settings in 754 <file:drivers/scsi/g_NCR5380.h>. 755 756 To compile this driver as a module, choose M here: the 757 module will be called g_NCR5380. 758 759config SCSI_GENERIC_NCR5380_MMIO 760 tristate "Generic NCR5380/53c400 SCSI MMIO support" 761 depends on ISA && SCSI 762 select SCSI_SPI_ATTRS 763 ---help--- 764 This is a driver for the old NCR 53c80 series of SCSI controllers 765 on boards using memory mapped I/O. 766 It is explained in section 3.8 of the SCSI-HOWTO, available from 767 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 768 of the box, you may have to change some settings in 769 <file:drivers/scsi/g_NCR5380.h>. 770 771 To compile this driver as a module, choose M here: the 772 module will be called g_NCR5380_mmio. 773 774config SCSI_GENERIC_NCR53C400 775 bool "Enable NCR53c400 extensions" 776 depends on SCSI_GENERIC_NCR5380 777 help 778 This enables certain optimizations for the NCR53c400 SCSI cards. 779 You might as well try it out. Note that this driver will only probe 780 for the Trantor T130B in its default configuration; you might have 781 to pass a command line option to the kernel at boot time if it does 782 not detect your card. See the file 783 <file:Documentation/scsi/g_NCR5380.txt> for details. 784 785config SCSI_IBMMCA 786 tristate "IBMMCA SCSI support" 787 depends on MCA && SCSI 788 ---help--- 789 This is support for the IBM SCSI adapter found in many of the PS/2 790 series computers. These machines have an MCA bus, so you need to 791 answer Y to "MCA support" as well and read 792 <file:Documentation/mca.txt>. 793 794 If the adapter isn't found during boot (a common problem for models 795 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel 796 option, where <pun> is the id of the SCSI subsystem (usually 7, but 797 if that doesn't work check your reference diskette). Owners of 798 model 95 with a LED-matrix-display can in addition activate some 799 activity info like under OS/2, but more informative, by setting 800 'ibmmcascsi=display' as an additional kernel parameter. Try "man 801 bootparam" or see the documentation of your boot loader about how to 802 pass options to the kernel. 803 804 To compile this driver as a module, choose M here: the 805 module will be called ibmmca. 806 807config IBMMCA_SCSI_ORDER_STANDARD 808 bool "Standard SCSI-order" 809 depends on SCSI_IBMMCA 810 ---help--- 811 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks 812 are assigned to the drive letters, starting with the lowest SCSI-id 813 (physical number -- pun) to be drive C:, as seen from DOS and 814 similar operating systems. When looking into papers describing the 815 ANSI-SCSI-standard, this assignment of drives appears to be wrong. 816 The SCSI-standard follows a hardware-hierarchy which says that id 7 817 has the highest priority and id 0 the lowest. Therefore, the host 818 adapters are still today everywhere placed as SCSI-id 7 by default. 819 In the SCSI-standard, the drive letters express the priority of the 820 disk. C: should be the hard disk, or a partition on it, with the 821 highest priority. This must therefore be the disk with the highest 822 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the 823 original definition of the SCSI-standard as also industrial- and 824 process-control-machines, like VME-CPUs running under realtime-OSes 825 (e.g. LynxOS, OS9) do. 826 827 If you like to run Linux on your MCA-machine with the same 828 assignment of hard disks as seen from e.g. DOS or OS/2 on your 829 machine, which is in addition conformant to the SCSI-standard, you 830 must say Y here. This is also necessary for MCA-Linux users who want 831 to keep downward compatibility to older releases of the 832 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than 833 June 1997). 834 835 If you like to have the lowest SCSI-id assigned as drive C:, as 836 modern SCSI-BIOSes do, which does not conform to the standard, but 837 is widespread and common in the PC-world of today, you must say N 838 here. If unsure, say Y. 839 840config IBMMCA_SCSI_DEV_RESET 841 bool "Reset SCSI-devices at boottime" 842 depends on SCSI_IBMMCA 843 ---help--- 844 By default, SCSI-devices are reset when the machine is powered on. 845 However, some devices exist, like special-control-devices, 846 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do 847 not reset when switched on. If you say Y here, each device connected 848 to your SCSI-bus will be issued a reset-command after it has been 849 probed, while the kernel is booting. This may cause problems with 850 more modern devices, like hard disks, which do not appreciate these 851 reset commands, and can cause your system to hang. So say Y only if 852 you know that one of your older devices needs it; N is the safe 853 answer. 854 855config SCSI_IPS 856 tristate "IBM ServeRAID support" 857 depends on PCI && SCSI 858 ---help--- 859 This is support for the IBM ServeRAID hardware RAID controllers. 860 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html> 861 for more information. If this driver does not work correctly 862 without modification please contact the author by email at 863 <ipslinux@adaptec.com>. 864 865 To compile this driver as a module, choose M here: the 866 module will be called ips. 867 868config SCSI_IBMVSCSI 869 tristate "IBM Virtual SCSI support" 870 depends on PPC_PSERIES || PPC_ISERIES 871 select SCSI_SRP_ATTRS 872 help 873 This is the IBM POWER Virtual SCSI Client 874 875 To compile this driver as a module, choose M here: the 876 module will be called ibmvscsic. 877 878config SCSI_IBMVSCSIS 879 tristate "IBM Virtual SCSI Server support" 880 depends on PPC_PSERIES && SCSI_SRP && SCSI_SRP_TGT_ATTRS 881 help 882 This is the SRP target driver for IBM pSeries virtual environments. 883 884 The userspace component needed to initialize the driver and 885 documentation can be found: 886 887 http://stgt.berlios.de/ 888 889 To compile this driver as a module, choose M here: the 890 module will be called ibmvstgt. 891 892config SCSI_IBMVFC 893 tristate "IBM Virtual FC support" 894 depends on PPC_PSERIES && SCSI 895 select SCSI_FC_ATTRS 896 help 897 This is the IBM POWER Virtual FC Client 898 899 To compile this driver as a module, choose M here: the 900 module will be called ibmvfc. 901 902config SCSI_IBMVFC_TRACE 903 bool "enable driver internal trace" 904 depends on SCSI_IBMVFC 905 default y 906 help 907 If you say Y here, the driver will trace all commands issued 908 to the adapter. Performance impact is minimal. Trace can be 909 dumped using /sys/class/scsi_host/hostXX/trace. 910 911config SCSI_INITIO 912 tristate "Initio 9100U(W) support" 913 depends on PCI && SCSI 914 help 915 This is support for the Initio 91XXU(W) SCSI host adapter. Please 916 read the SCSI-HOWTO, available from 917 <http://www.tldp.org/docs.html#howto>. 918 919 To compile this driver as a module, choose M here: the 920 module will be called initio. 921 922config SCSI_INIA100 923 tristate "Initio INI-A100U2W support" 924 depends on PCI && SCSI 925 help 926 This is support for the Initio INI-A100U2W SCSI host adapter. 927 Please 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 a100u2w. 932 933config SCSI_PPA 934 tristate "IOMEGA parallel port (ppa - older drives)" 935 depends on SCSI && PARPORT_PC 936 ---help--- 937 This driver supports older versions of IOMEGA's parallel port ZIP 938 drive (a 100 MB removable media device). 939 940 Note that you can say N here if you have the SCSI version of the ZIP 941 drive: it will be supported automatically if you said Y to the 942 generic "SCSI disk support", above. 943 944 If you have the ZIP Plus drive or a more recent parallel port ZIP 945 drive (if the supplied cable with the drive is labeled "AutoDetect") 946 then you should say N here and Y to "IOMEGA parallel port (imm - 947 newer drives)", below. 948 949 For more information about this driver and how to use it you should 950 read the file <file:Documentation/scsi/ppa.txt>. You should also read 951 the SCSI-HOWTO, which is available from 952 <http://www.tldp.org/docs.html#howto>. If you use this driver, 953 you will still be able to use the parallel port for other tasks, 954 such as a printer; it is safe to compile both drivers into the 955 kernel. 956 957 To compile this driver as a module, choose M here: the 958 module will be called ppa. 959 960config SCSI_IMM 961 tristate "IOMEGA parallel port (imm - newer drives)" 962 depends on SCSI && PARPORT_PC 963 ---help--- 964 This driver supports newer versions of IOMEGA's parallel port ZIP 965 drive (a 100 MB removable media device). 966 967 Note that you can say N here if you have the SCSI version of the ZIP 968 drive: it will be supported automatically if you said Y to the 969 generic "SCSI disk support", above. 970 971 If you have the ZIP Plus drive or a more recent parallel port ZIP 972 drive (if the supplied cable with the drive is labeled "AutoDetect") 973 then you should say Y here; if you have an older ZIP drive, say N 974 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above. 975 976 For more information about this driver and how to use it you should 977 read the file <file:Documentation/scsi/ppa.txt>. You should also read 978 the SCSI-HOWTO, which is available from 979 <http://www.tldp.org/docs.html#howto>. If you use this driver, 980 you will still be able to use the parallel port for other tasks, 981 such as a printer; it is safe to compile both drivers into the 982 kernel. 983 984 To compile this driver as a module, choose M here: the 985 module will be called imm. 986 987config SCSI_IZIP_EPP16 988 bool "ppa/imm option - Use slow (but safe) EPP-16" 989 depends on SCSI_PPA || SCSI_IMM 990 ---help--- 991 EPP (Enhanced Parallel Port) is a standard for parallel ports which 992 allows them to act as expansion buses that can handle up to 64 993 peripheral devices. 994 995 Some parallel port chipsets are slower than their motherboard, and 996 so we have to control the state of the chipset's FIFO queue every 997 now and then to avoid data loss. This will be done if you say Y 998 here. 999 1000 Generally, saying Y is the safe option and slows things down a bit. 1001 1002config SCSI_IZIP_SLOW_CTR 1003 bool "ppa/imm option - Assume slow parport control register" 1004 depends on SCSI_PPA || SCSI_IMM 1005 help 1006 Some parallel ports are known to have excessive delays between 1007 changing the parallel port control register and good data being 1008 available on the parallel port data/status register. This option 1009 forces a small delay (1.0 usec to be exact) after changing the 1010 control register to let things settle out. Enabling this option may 1011 result in a big drop in performance but some very old parallel ports 1012 (found in 386 vintage machines) will not work properly. 1013 1014 Generally, saying N is fine. 1015 1016config SCSI_MVSAS 1017 tristate "Marvell 88SE6440 SAS/SATA support" 1018 depends on PCI && SCSI 1019 select SCSI_SAS_LIBSAS 1020 help 1021 This driver supports Marvell SAS/SATA PCI devices. 1022 1023 To compiler this driver as a module, choose M here: the module 1024 will be called mvsas. 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 help 1357 This lpfc driver supports the Emulex LightPulse 1358 Family of Fibre Channel PCI host adapters. 1359 1360config SCSI_SIM710 1361 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)" 1362 depends on (EISA || MCA) && SCSI 1363 select SCSI_SPI_ATTRS 1364 ---help--- 1365 This driver for NCR53c710 based SCSI host adapters. 1366 1367 It currently supports Compaq EISA cards and NCR MCA cards 1368 1369config SCSI_SYM53C416 1370 tristate "Symbios 53c416 SCSI support" 1371 depends on ISA && SCSI 1372 ---help--- 1373 This is support for the sym53c416 SCSI host adapter, the SCSI 1374 adapter that comes with some HP scanners. This driver requires that 1375 the sym53c416 is configured first using some sort of PnP 1376 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you 1377 are using isapnp then you need to compile this driver as a module 1378 and then load it using insmod after isapnp has run. The parameters 1379 of the configured card(s) should be passed to the driver. The format 1380 is: 1381 1382 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>] 1383 1384 To compile this driver as a module, choose M here: the 1385 module will be called sym53c416. 1386 1387config SCSI_DC395x 1388 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)" 1389 depends on PCI && SCSI && EXPERIMENTAL 1390 ---help--- 1391 This driver supports PCI SCSI host adapters based on the ASIC 1392 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants. 1393 1394 This driver works, but is still in experimental status. So better 1395 have a bootable disk and a backup in case of emergency. 1396 1397 Documentation can be found in <file:Documentation/scsi/dc395x.txt>. 1398 1399 To compile this driver as a module, choose M here: the 1400 module will be called dc395x. 1401 1402config SCSI_DC390T 1403 tristate "Tekram DC390(T) and Am53/79C974 SCSI support" 1404 depends on PCI && SCSI 1405 ---help--- 1406 This driver supports PCI SCSI host adapters based on the Am53C974A 1407 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard 1408 PCscsi/PCnet (Am53/79C974) solutions. 1409 1410 Documentation can be found in <file:Documentation/scsi/tmscsim.txt>. 1411 1412 Note that this driver does NOT support Tekram DC390W/U/F, which are 1413 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those. 1414 1415 To compile this driver as a module, choose M here: the 1416 module will be called tmscsim. 1417 1418config SCSI_T128 1419 tristate "Trantor T128/T128F/T228 SCSI support" 1420 depends on ISA && SCSI 1421 select SCSI_SPI_ATTRS 1422 select CHECK_SIGNATURE 1423 ---help--- 1424 This is support for a SCSI host adapter. It is explained in section 1425 3.11 of the SCSI-HOWTO, available from 1426 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 1427 of the box, you may have to change some settings in 1428 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by 1429 Adaptec, and some former Trantor products are being sold under the 1430 Adaptec name. 1431 1432 To compile this driver as a module, choose M here: the 1433 module will be called t128. 1434 1435config SCSI_U14_34F 1436 tristate "UltraStor 14F/34F support" 1437 depends on ISA && SCSI && ISA_DMA_API 1438 ---help--- 1439 This is support for the UltraStor 14F and 34F SCSI-2 host adapters. 1440 The source at <file:drivers/scsi/u14-34f.c> contains some 1441 information about this hardware. If the driver doesn't work out of 1442 the box, you may have to change some settings in 1443 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from 1444 <http://www.tldp.org/docs.html#howto>. Note that there is also 1445 another driver for the same hardware: "UltraStor SCSI support", 1446 below. You should say Y to both only if you want 24F support as 1447 well. 1448 1449 To compile this driver as a module, choose M here: the 1450 module will be called u14-34f. 1451 1452config SCSI_U14_34F_TAGGED_QUEUE 1453 bool "enable tagged command queueing" 1454 depends on SCSI_U14_34F 1455 help 1456 This is a feature of SCSI-2 which improves performance: the host 1457 adapter can send several SCSI commands to a device's queue even if 1458 previous commands haven't finished yet. 1459 This is equivalent to the "u14-34f=tc:y" boot option. 1460 1461config SCSI_U14_34F_LINKED_COMMANDS 1462 bool "enable elevator sorting" 1463 depends on SCSI_U14_34F 1464 help 1465 This option enables elevator sorting for all probed SCSI disks and 1466 CD-ROMs. It definitely reduces the average seek distance when doing 1467 random seeks, but this does not necessarily result in a noticeable 1468 performance improvement: your mileage may vary... 1469 This is equivalent to the "u14-34f=lc:y" boot option. 1470 1471config SCSI_U14_34F_MAX_TAGS 1472 int "maximum number of queued commands" 1473 depends on SCSI_U14_34F 1474 default "8" 1475 help 1476 This specifies how many SCSI commands can be maximally queued for 1477 each probed SCSI device. You should reduce the default value of 8 1478 only if you have disks with buggy or limited tagged command support. 1479 Minimum is 2 and maximum is 14. This value is also the window size 1480 used by the elevator sorting option above. The effective value used 1481 by the driver for each probed SCSI device is reported at boot time. 1482 This is equivalent to the "u14-34f=mq:8" boot option. 1483 1484config SCSI_ULTRASTOR 1485 tristate "UltraStor SCSI support" 1486 depends on X86 && ISA && SCSI 1487 ---help--- 1488 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host 1489 adapter family. This driver is explained in section 3.12 of the 1490 SCSI-HOWTO, available from 1491 <http://www.tldp.org/docs.html#howto>. If it doesn't work out 1492 of the box, you may have to change some settings in 1493 <file:drivers/scsi/ultrastor.h>. 1494 1495 Note that there is also another driver for the same hardware: 1496 "UltraStor 14F/34F support", above. 1497 1498 To compile this driver as a module, choose M here: the 1499 module will be called ultrastor. 1500 1501config SCSI_NSP32 1502 tristate "Workbit NinjaSCSI-32Bi/UDE support" 1503 depends on PCI && SCSI && !64BIT 1504 help 1505 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus 1506 SCSI host adapter. Please read the SCSI-HOWTO, available from 1507 <http://www.tldp.org/docs.html#howto>. 1508 1509 To compile this driver as a module, choose M here: the 1510 module will be called nsp32. 1511 1512config SCSI_DEBUG 1513 tristate "SCSI debugging host simulator" 1514 depends on SCSI 1515 help 1516 This is a host adapter simulator that can simulate multiple hosts 1517 each with multiple dummy SCSI devices (disks). It defaults to one 1518 host adapter with one dummy SCSI disk. Each dummy disk uses kernel 1519 RAM as storage (i.e. it is a ramdisk). To save space when multiple 1520 dummy disks are simulated, they share the same kernel RAM for 1521 their storage. See <http://www.torque.net/sg/sdebug.html> for more 1522 information. This driver is primarily of use to those testing the 1523 SCSI and block subsystems. If unsure, say N. 1524 1525config SCSI_MESH 1526 tristate "MESH (Power Mac internal SCSI) support" 1527 depends on PPC32 && PPC_PMAC && SCSI 1528 help 1529 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced 1530 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the 1531 other Power Macintoshes do). Say Y to include support for this SCSI 1532 adaptor. 1533 1534 To compile this driver as a module, choose M here: the 1535 module will be called mesh. 1536 1537config SCSI_MESH_SYNC_RATE 1538 int "maximum synchronous transfer rate (MB/s) (0 = async)" 1539 depends on SCSI_MESH 1540 default "5" 1541 help 1542 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor 1543 drives a bus which is entirely internal to the machine (such as the 1544 7500, 7600, 8500, etc.), the MESH is capable of synchronous 1545 operation at up to 10 MB/s. On machines where the SCSI bus 1546 controlled by the MESH can have external devices connected, it is 1547 usually rated at 5 MB/s. 5 is a safe value here unless you know the 1548 MESH SCSI bus is internal only; in that case you can say 10. Say 0 1549 to disable synchronous operation. 1550 1551config SCSI_MESH_RESET_DELAY_MS 1552 int "initial bus reset delay (ms) (0 = no reset)" 1553 depends on SCSI_MESH 1554 default "4000" 1555 1556config SCSI_MAC53C94 1557 tristate "53C94 (Power Mac external SCSI) support" 1558 depends on PPC32 && PPC_PMAC && SCSI 1559 help 1560 On Power Macintoshes (and clones) with two SCSI buses, the external 1561 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older 1562 machines which only have one SCSI bus, such as the 7200, also use 1563 the 53C94. Say Y to include support for the 53C94. 1564 1565 To compile this driver as a module, choose M here: the 1566 module will be called mac53c94. 1567 1568source "drivers/scsi/arm/Kconfig" 1569 1570config JAZZ_ESP 1571 bool "MIPS JAZZ FAS216 SCSI support" 1572 depends on MACH_JAZZ && SCSI 1573 select SCSI_SPI_ATTRS 1574 help 1575 This is the driver for the onboard SCSI host adapter of MIPS Magnum 1576 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM 1577 systems. 1578 1579config A3000_SCSI 1580 tristate "A3000 WD33C93A support" 1581 depends on AMIGA && SCSI 1582 help 1583 If you have an Amiga 3000 and have SCSI devices connected to the 1584 built-in SCSI controller, say Y. Otherwise, say N. 1585 1586 To compile this driver as a module, choose M here: the 1587 module will be called a3000. 1588 1589config A2091_SCSI 1590 tristate "A2091/A590 WD33C93A support" 1591 depends on ZORRO && SCSI 1592 help 1593 If you have a Commodore A2091 SCSI controller, say Y. Otherwise, 1594 say N. 1595 1596 To compile this driver as a module, choose M here: the 1597 module will be called a2091. 1598 1599config GVP11_SCSI 1600 tristate "GVP Series II WD33C93A support" 1601 depends on ZORRO && SCSI 1602 ---help--- 1603 If you have a Great Valley Products Series II SCSI controller, 1604 answer Y. Also say Y if you have a later model of GVP SCSI 1605 controller (such as the GVP A4008 or a Combo board). Otherwise, 1606 answer N. This driver does NOT work for the T-Rex series of 1607 accelerators from TekMagic and GVP-M. 1608 1609 To compile this driver as a module, choose M here: the 1610 module will be called gvp11. 1611 1612config SCSI_A4000T 1613 tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)" 1614 depends on AMIGA && SCSI && EXPERIMENTAL 1615 select SCSI_SPI_ATTRS 1616 help 1617 If you have an Amiga 4000T and have SCSI devices connected to the 1618 built-in SCSI controller, say Y. Otherwise, say N. 1619 1620 To compile this driver as a module, choose M here: the 1621 module will be called a4000t. 1622 1623config SCSI_ZORRO7XX 1624 tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)" 1625 depends on ZORRO && SCSI && EXPERIMENTAL 1626 select SCSI_SPI_ATTRS 1627 help 1628 Support for various NCR53c710-based SCSI controllers on Zorro 1629 expansion boards for the Amiga. 1630 This includes: 1631 - the Amiga 4091 Zorro III SCSI-2 controller, 1632 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller 1633 (info at 1634 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>), 1635 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+ 1636 accelerator card for the Amiga 1200, 1637 - the SCSI controller on the GVP Turbo 040/060 accelerator. 1638 1639config ATARI_SCSI 1640 tristate "Atari native SCSI support" 1641 depends on ATARI && SCSI 1642 select SCSI_SPI_ATTRS 1643 select NVRAM 1644 ---help--- 1645 If you have an Atari with built-in NCR5380 SCSI controller (TT, 1646 Falcon, ...) say Y to get it supported. Of course also, if you have 1647 a compatible SCSI controller (e.g. for Medusa). 1648 1649 To compile this driver as a module, choose M here: the 1650 module will be called atari_scsi. 1651 1652 This driver supports both styles of NCR integration into the 1653 system: the TT style (separate DMA), and the Falcon style (via 1654 ST-DMA, replacing ACSI). It does NOT support other schemes, like 1655 in the Hades (without DMA). 1656 1657config ATARI_SCSI_TOSHIBA_DELAY 1658 bool "Long delays for Toshiba CD-ROMs" 1659 depends on ATARI_SCSI 1660 help 1661 This option increases the delay after a SCSI arbitration to 1662 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to 1663 use a Toshiba CD-ROM drive; otherwise, the option is not needed and 1664 would impact performance a bit, so say N. 1665 1666config ATARI_SCSI_RESET_BOOT 1667 bool "Reset SCSI-devices at boottime" 1668 depends on ATARI_SCSI 1669 help 1670 Reset the devices on your Atari whenever it boots. This makes the 1671 boot process fractionally longer but may assist recovery from errors 1672 that leave the devices with SCSI operations partway completed. 1673 1674config MAC_SCSI 1675 bool "Macintosh NCR5380 SCSI" 1676 depends on MAC && SCSI=y 1677 select SCSI_SPI_ATTRS 1678 help 1679 This is the NCR 5380 SCSI controller included on most of the 68030 1680 based Macintoshes. If you have one of these say Y and read the 1681 SCSI-HOWTO, available from 1682 <http://www.tldp.org/docs.html#howto>. 1683 1684config SCSI_MAC_ESP 1685 tristate "Macintosh NCR53c9[46] SCSI" 1686 depends on MAC && SCSI 1687 select SCSI_SPI_ATTRS 1688 help 1689 This is the NCR 53c9x SCSI controller found on most of the 68040 1690 based Macintoshes. 1691 1692 To compile this driver as a module, choose M here: the module 1693 will be called mac_esp. 1694 1695config MVME147_SCSI 1696 bool "WD33C93 SCSI driver for MVME147" 1697 depends on MVME147 && SCSI=y 1698 select SCSI_SPI_ATTRS 1699 help 1700 Support for the on-board SCSI controller on the Motorola MVME147 1701 single-board computer. 1702 1703config MVME16x_SCSI 1704 tristate "NCR53C710 SCSI driver for MVME16x" 1705 depends on MVME16x && SCSI 1706 select SCSI_SPI_ATTRS 1707 help 1708 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710 1709 SCSI controller chip. Almost everyone using one of these boards 1710 will want to say Y to this question. 1711 1712config BVME6000_SCSI 1713 tristate "NCR53C710 SCSI driver for BVME6000" 1714 depends on BVME6000 && SCSI 1715 select SCSI_SPI_ATTRS 1716 help 1717 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710 1718 SCSI controller chip. Almost everyone using one of these boards 1719 will want to say Y to this question. 1720 1721config SUN3_SCSI 1722 tristate "Sun3 NCR5380 SCSI" 1723 depends on SUN3 && SCSI 1724 select SCSI_SPI_ATTRS 1725 help 1726 This option will enable support for the OBIO (onboard io) NCR5380 1727 SCSI controller found in the Sun 3/50 and 3/60, as well as for 1728 "Sun3" type VME scsi controllers also based on the NCR5380. 1729 General Linux information on the Sun 3 series (now discontinued) 1730 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>. 1731 1732config SUN3X_ESP 1733 bool "Sun3x ESP SCSI" 1734 depends on SUN3X && SCSI=y 1735 select SCSI_SPI_ATTRS 1736 help 1737 The ESP was an on-board SCSI controller used on Sun 3/80 1738 machines. Say Y here to compile in support for it. 1739 1740config SCSI_SUNESP 1741 tristate "Sparc ESP Scsi Driver" 1742 depends on SBUS && SCSI 1743 select SCSI_SPI_ATTRS 1744 help 1745 This is the driver for the Sun ESP SCSI host adapter. The ESP 1746 chipset is present in most SPARC SBUS-based computers and 1747 supports the Emulex family of ESP SCSI chips (esp100, esp100A, 1748 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip. 1749 1750 To compile this driver as a module, choose M here: the 1751 module will be called sun_esp. 1752 1753config ZFCP 1754 tristate "FCP host bus adapter driver for IBM eServer zSeries" 1755 depends on S390 && QDIO && SCSI 1756 select SCSI_FC_ATTRS 1757 help 1758 If you want to access SCSI devices attached to your IBM eServer 1759 zSeries by means of Fibre Channel interfaces say Y. 1760 For details please refer to the documentation provided by IBM at 1761 <http://oss.software.ibm.com/developerworks/opensource/linux390> 1762 1763 This driver is also available as a module. This module will be 1764 called zfcp. If you want to compile it as a module, say M here 1765 and read <file:Documentation/kbuild/modules.txt>. 1766 1767config SCSI_SRP 1768 tristate "SCSI RDMA Protocol helper library" 1769 depends on SCSI && PCI 1770 select SCSI_TGT 1771 help 1772 If you wish to use SRP target drivers, say Y. 1773 1774 To compile this driver as a module, choose M here: the 1775 module will be called libsrp. 1776 1777endif # SCSI_LOWLEVEL 1778 1779source "drivers/scsi/pcmcia/Kconfig" 1780 1781source "drivers/scsi/device_handler/Kconfig" 1782 1783endmenu 1784