Kconfig 62.1 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
menu "SCSI device support"

config SCSI
	tristate "SCSI device support"
	---help---
	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
	  any other SCSI device under Linux, say Y and make sure that you know
	  the name of your SCSI host adapter (the card inside your computer
	  that "speaks" the SCSI protocol, also called SCSI controller),
	  because you will be asked for it.

	  You also need to say Y here if you have a device which speaks
	  the SCSI protocol.  Examples of this include the parallel port
	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
	  Channel, FireWire storage and the IDE-SCSI emulation driver.

17 18 19 20 21 22
	  To compile this driver as a module, choose M here and read
	  <file:Documentation/scsi/scsi.txt>.
	  The module will be called scsi_mod.

	  However, do not compile this as a module if your root file system
	  (the one containing the directory /) is located on a SCSI device.
23

24 25
config SCSI_PROC_FS
	bool "legacy /proc/scsi/ support"
26
	depends on SCSI && PROC_FS
27 28 29 30 31 32 33 34
	default y
	---help---
	  This option enables support for the various files in
	  /proc/scsi.  In Linux 2.6 this has been superceeded by
	  files in sysfs but many legacy applications rely on this.

	  If unusure say Y.

35 36 37 38 39 40 41
comment "SCSI support type (disk, tape, CD-ROM)"
	depends on SCSI

config BLK_DEV_SD
	tristate "SCSI disk support"
	depends on SCSI
	---help---
42 43 44 45
	  If you want to use SCSI hard disks, Fibre Channel disks,
	  USB storage or the SCSI or parallel port version of
	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
46
	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
47 48
	  CD-ROMs.

49 50 51 52 53 54 55 56
	  To compile this driver as a module, choose M here and read
	  <file:Documentation/scsi/scsi.txt>.
	  The module will be called sd_mod.

	  Do not compile this driver as a module if your root file system
	  (the one containing the directory /) is located on a SCSI disk.
	  In this case, do not compile the driver for your SCSI host adapter
	  (below) as a module either.
57 58 59 60 61 62 63

config CHR_DEV_ST
	tristate "SCSI tape support"
	depends on SCSI
	---help---
	  If you want to use a SCSI tape drive under Linux, say Y and read the
	  SCSI-HOWTO, available from
64
	  <http://www.tldp.org/docs.html#howto>, and
65 66
	  <file:Documentation/scsi/st.txt> in the kernel source.  This is NOT
	  for SCSI CD-ROMs.
67

68 69
	  To compile this driver as a module, choose M here and read
	  <file:Documentation/scsi/scsi.txt>. The module will be called st.
70 71 72 73 74 75 76 77 78 79 80 81 82

config CHR_DEV_OSST
	tristate "SCSI OnStream SC-x0 tape support"
	depends on SCSI
	---help---
	  The OnStream SC-x0 SCSI tape drives can not be driven by the
	  standard st driver, but instead need this special osst driver and
	  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
	  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
	  as well.  Note that there is also a second generation of OnStream
	  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
	  tapes (QIC-157) and can be driven by the standard driver st.
	  For more information, you may have a look at the SCSI-HOWTO
83
	  <http://www.tldp.org/docs.html#howto>  and
84
	  <file:Documentation/scsi/osst.txt>  in the kernel source.
85 86 87 88 89
	  More info on the OnStream driver may be found on
	  <http://linux1.onstream.nl/test/>
	  Please also have a look at the standard st docu, as most of it
	  applies to osst as well.

90 91
	  To compile this driver as a module, choose M here and read
	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.
92 93 94 95 96

config BLK_DEV_SR
	tristate "SCSI CDROM support"
	depends on SCSI
	---help---
97 98 99 100
	  If you want to use a SCSI or FireWire CD-ROM under Linux,
	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
	  Y or M to "ISO 9660 CD-ROM file system support" later.
101

102
	  To compile this driver as a module, choose M here and read
103
	  <file:Documentation/scsi/scsi.txt>.
104
	  The module will be called sr_mod.
105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132

config BLK_DEV_SR_VENDOR
	bool "Enable vendor-specific extensions (for SCSI CDROM)"
	depends on BLK_DEV_SR
	help
	  This enables the usage of vendor specific SCSI commands. This is
	  required to support multisession CDs with old NEC/TOSHIBA cdrom
	  drives (and HP Writers). If you have such a drive and get the first
	  session only, try saying Y here; everybody else says N.

config CHR_DEV_SG
	tristate "SCSI generic support"
	depends on SCSI
	---help---
	  If you want to use SCSI scanners, synthesizers or CD-writers or just
	  about anything having "SCSI" in its name other than hard disks,
	  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
	  directly, so you need some additional software which knows how to
	  talk to these devices using the SCSI protocol:

	  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
	  writer software look at Cdrtools
	  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
	  and for burning a "disk at once": CDRDAO
	  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
	  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
	  For other devices, it's possible that you'll have to write the
	  driver software yourself. Please read the file
133
	  <file:Documentation/scsi/scsi-generic.txt> for more information.
134

135
	  To compile this driver as a module, choose M here and read
136
	  <file:Documentation/scsi/scsi.txt>. The module will be called sg.
137

138
	  If unsure, say N.
139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157

comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
	depends on SCSI

config SCSI_MULTI_LUN
	bool "Probe all LUNs on each SCSI device"
	depends on SCSI
	help
	  If you have a SCSI device that supports more than one LUN (Logical
	  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
	  can say Y here to force the SCSI driver to probe for multiple LUNs.
	  A SCSI device with multiple LUNs acts logically like multiple SCSI
	  devices. The vast majority of SCSI devices have only one LUN, and
	  so most people can say N here and should in fact do so, because it
	  is safer.

config SCSI_REPORT_LUNS
	bool "Build with SCSI REPORT LUNS support"
	depends on SCSI
Jeff Garzik's avatar
Jeff Garzik committed
158
	default y
159
	help
160 161 162 163 164
	  If you want support for SCSI REPORT LUNS, say Y here.
	  The REPORT LUNS command is useful for devices (such as disk arrays)
	  with large numbers of LUNs where the LUN values are not contiguous
	  (sparse LUN).  REPORT LUNS scanning is done only for SCSI-3 devices.
	  Most users can safely answer N here.
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198

config SCSI_CONSTANTS
	bool "Verbose SCSI error reporting (kernel size +=12K)"
	depends on SCSI
	help
	  The error messages regarding your SCSI hardware will be easier to
	  understand if you say Y here; it will enlarge your kernel by about
	  12 KB. If in doubt, say Y.

config SCSI_LOGGING
	bool "SCSI logging facility"
	depends on SCSI
	---help---
	  This turns on a logging facility that can be used to debug a number
	  of SCSI related problems.

	  If you say Y here, no logging output will appear by default, but you
	  can enable logging by saying Y to "/proc file system support" and
	  "Sysctl support" below and executing the command

	  echo "scsi log token [level]" > /proc/scsi/scsi

	  at boot time after the /proc file system has been mounted.

	  There are a number of things that can be used for 'token' (you can
	  find them in the source: <file:drivers/scsi/scsi.c>), and this
	  allows you to select the types of information you want, and the
	  level allows you to select the level of verbosity.

	  If you say N here, it may be harder to track down some types of SCSI
	  problems. If you say Y here your kernel will be somewhat larger, but
	  there should be no noticeable performance impact as long as you have
	  logging turned off.

199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217
menu "SCSI Transport Attributes"
	depends on SCSI

config SCSI_SPI_ATTRS
	tristate "Parallel SCSI (SPI) Transport Attributes"
	depends on SCSI
	help
	  If you wish to export transport-specific information about
	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.

config SCSI_FC_ATTRS
	tristate "FiberChannel Transport Attributes"
	depends on SCSI
	help
	  If you wish to export transport-specific information about
	  each attached FiberChannel device to sysfs, say Y.
	  Otherwise, say N.

endmenu
218 219 220 221 222 223 224

menu "SCSI low-level drivers"
	depends on SCSI!=n

config SGIWD93_SCSI
	tristate "SGI WD93C93 SCSI Driver"
	depends on SGI_IP22 && SCSI
225 226 227
  	help
	  If you have a Western Digital WD93 SCSI controller on
	  an SGI MIPS system, say Y.  Otherwise, say N.
228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254

config SCSI_DECNCR
	tristate "DEC NCR53C94 Scsi Driver"
	depends on DECSTATION && TC && SCSI
	help
	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.

config SCSI_DECSII
	tristate "DEC SII Scsi Driver"
	depends on DECSTATION && SCSI

config BLK_DEV_3W_XXXX_RAID
	tristate "3ware Hardware ATA-RAID support"
	depends on PCI && SCSI
	help
	  3ware is the only hardware ATA-Raid product in Linux to date.
	  This card is 2,4, or 8 channel master mode support only.
	  SCSI support required!!!

	  <http://www.3ware.com/>

	  Please read the comments at the top of
	  <file:drivers/scsi/3w-xxxx.c>.

config SCSI_7000FASST
	tristate "7000FASST SCSI support"
255
	depends on ISA && SCSI
256 257 258 259 260
	help
	  This driver supports the Western Digital 7000 SCSI host adapter
	  family.  Some information is in the source:
	  <file:drivers/scsi/wd7000.c>.

261 262
	  To compile this driver as a module, choose M here: the
	  module will be called wd7000.
263 264 265

config SCSI_ACARD
	tristate "ACARD SCSI support"
266
	depends on PCI && SCSI
267 268 269
	help
	  This driver supports the ACARD 870U/W SCSI host adapter.

270 271
	  To compile this driver as a module, choose M here: the
	  module will be called atp870u.
272 273 274

config SCSI_AHA152X
	tristate "Adaptec AHA152X/2825 support"
275
	depends on ISA && SCSI && !64BIT
276 277 278 279 280 281
	---help---
	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
	  must be manually specified in this case.

	  It is explained in section 3.3 of the SCSI-HOWTO, available from
282
	  <http://www.tldp.org/docs.html#howto>. You might also want to
283
	  read the file <file:Documentation/scsi/aha152x.txt>.
284

285 286
	  To compile this driver as a module, choose M here: the
	  module will be called aha152x.
287 288 289 290 291 292 293

config SCSI_AHA1542
	tristate "Adaptec AHA1542 support"
	depends on ISA && SCSI
	---help---
	  This is support for a SCSI host adapter.  It is explained in section
	  3.4 of the SCSI-HOWTO, available from
294
	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
295 296 297 298
	  purchased by Adaptec, and some former Trantor products are being
	  sold under the Adaptec name.  If it doesn't work out of the box, you
	  may have to change some settings in <file:drivers/scsi/aha1542.h>.

299 300
	  To compile this driver as a module, choose M here: the
	  module will be called aha1542.
301 302 303 304 305 306 307

config SCSI_AHA1740
	tristate "Adaptec AHA1740 support"
	depends on EISA && SCSI
	---help---
	  This is support for a SCSI host adapter.  It is explained in section
	  3.5 of the SCSI-HOWTO, available from
308
	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
309 310 311
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/aha1740.h>.

312 313
	  To compile this driver as a module, choose M here: the
	  module will be called aha1740.
314 315 316 317 318

config SCSI_AACRAID
	tristate "Adaptec AACRAID support (EXPERIMENTAL)"
	depends on EXPERIMENTAL && SCSI && PCI

319
source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
320 321

config SCSI_AIC7XXX_OLD
322
	tristate "Adaptec AIC7xxx support (old driver)"
323
	depends on SCSI
324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352
	help
	  WARNING This driver is an older aic7xxx driver and is no longer
	  under active development.  Adaptec, Inc. is writing a new driver to
	  take the place of this one, and it is recommended that whenever
	  possible, people should use the new Adaptec written driver instead
	  of this one.  This driver will eventually be phased out entirely.

	  This is support for the various aic7xxx based Adaptec SCSI
	  controllers. These include the 274x EISA cards; 284x VLB cards;
	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
	  motherboard based SCSI controllers from Adaptec. It does not support
	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
	  support them. It does not support the 2920 cards from Adaptec that
	  use the Future Domain SCSI controller chip. For those cards, you
	  need the "Future Domain 16xx SCSI support" driver.

	  In general, if the controller is based on an Adaptec SCSI controller
	  chip from the aic777x series or the aic78xx series, this driver
	  should work. The only exception is the 7810 which is specifically
	  not supported (that's the RAID controller chip on the AAA-13x
	  cards).

	  Note that the AHA2920 SCSI host adapter is *not* supported by this
	  driver; choose "Future Domain 16xx SCSI support" instead if you have
	  one of those.

	  Information on the configuration options for this controller can be
	  found by checking the help file for each of the available
	  configuration options. You should read
353
	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
354
	  contacting the maintainer with any questions.  The SCSI-HOWTO,
355
	  available from <http://www.tldp.org/docs.html#howto>, can also
356 357
	  be of great help.

358 359
	  To compile this driver as a module, choose M here: the
	  module will be called aic7xxx_old.
360

361
source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
362 363 364 365

# All the I2O code and drivers do not seem to be 64bit safe.
config SCSI_DPT_I2O
	tristate "Adaptec I2O RAID support "
Matthew Wilcox's avatar
Matthew Wilcox committed
366
	depends on !64BIT && SCSI && BROKEN
367 368 369
	help
	  This driver supports all of Adaptec's I2O based RAID controllers as 
	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
370
	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
371

372 373
	  To compile this driver as a module, choose M here: the
	  module will be called dpt_i2o.
374 375 376

config SCSI_ADVANSYS
	tristate "AdvanSys SCSI support"
377
	depends on (ISA || EISA || PCI) && SCSI
378 379 380 381 382
	help
	  This is a driver for all SCSI host adapters manufactured by
	  AdvanSys. It is documented in the kernel source in
	  <file:drivers/scsi/advansys.c>.

383 384
	  To compile this driver as a module, choose M here: the
	  module will be called advansys.
385 386 387

config SCSI_IN2000
	tristate "Always IN2000 SCSI support"
388
	depends on ISA && SCSI
389 390
	help
	  This is support for an ISA bus SCSI host adapter.  You'll find more
391
	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
392 393 394
	  out of the box, you may have to change the jumpers for IRQ or
	  address selection.

395 396
	  To compile this driver as a module, choose M here: the
	  module will be called in2000.
397 398 399

config SCSI_MEGARAID
	tristate "AMI MegaRAID support"
400
	depends on PCI && SCSI
401 402 403 404
	help
	  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
	  and 467 SCSI host adapters.

405 406
	  To compile this driver as a module, choose M here: the
	  module will be called megaraid.
407

408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459
config SCSI_SATA
	bool "Serial ATA (SATA) support"
	depends on SCSI && EXPERIMENTAL
	help
	  This driver family supports Serial ATA host controllers
	  and devices.

	  If unsure, say N.

config SCSI_SATA_SVW
	tristate "ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL)"
	depends on SCSI_SATA && PCI && EXPERIMENTAL
	help
	  This option enables support for Broadcom/Serverworks/Apple K2
	  SATA support.

	  If unsure, say N.

config SCSI_ATA_PIIX
	tristate "Intel PIIX/ICH SATA support"
	depends on SCSI_SATA && PCI
	help
	  This option enables support for ICH5 Serial ATA.
	  If PATA support was enabled previously, this enables
	  support for select Intel PIIX/ICH PATA host controllers.

	  If unsure, say N.

config SCSI_SATA_PROMISE
	tristate "Promise SATA support"
	depends on SCSI_SATA && PCI && EXPERIMENTAL
	help
	  This option enables support for Promise Serial ATA.

	  If unsure, say N.

config SCSI_SATA_SIL
	tristate "Silicon Image SATA support"
	depends on SCSI_SATA && PCI && BROKEN
	help
	  This option enables support for Silicon Image Serial ATA.

	  If unsure, say N.

config SCSI_SATA_VIA
	tristate "VIA SATA support"
	depends on SCSI_SATA && PCI && EXPERIMENTAL
	help
	  This option enables support for VIA Serial ATA.

	  If unsure, say N.

460 461
config SCSI_BUSLOGIC
	tristate "BusLogic SCSI support"
462
	depends on (PCI || ISA || MCA) && SCSI
463 464 465
	---help---
	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
	  Adapters. Consult the SCSI-HOWTO, available from
466
	  <http://www.tldp.org/docs.html#howto>, and the files
467 468
	  <file:Documentation/scsi/BusLogic.txt> and
	  <file:Documentation/scsi/FlashPoint.txt> for more information. If this
469 470 471
	  driver does not work correctly without modification, please contact
	  the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.

472 473
	  To compile this driver as a module, choose M here: the
	  module will be called BusLogic.
474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492

config SCSI_OMIT_FLASHPOINT
	bool "Omit FlashPoint support"
	depends on SCSI_BUSLOGIC
	help
	  This option allows you to omit the FlashPoint support from the
	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
	  substantial, so users of MultiMaster Host Adapters may wish to omit
	  it.

config SCSI_CPQFCTS
	tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
	depends on PCI && SCSI
	help
	  Say Y here to compile in support for the Compaq StorageWorks Fibre
	  Channel 64-bit/66Mhz Host Bus Adapter.

config SCSI_DMX3191D
	tristate "DMX3191D SCSI support"
493
	depends on PCI && SCSI
494 495 496
	help
	  This is support for Domex DMX3191D SCSI Host Adapters.

497 498
	  To compile this driver as a module, choose M here: the
	  module will be called dmx3191d.
499 500 501

config SCSI_DTC3280
	tristate "DTC3180/3280 SCSI support"
502
	depends on ISA && SCSI
503 504 505
	help
	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
	  the SCSI-HOWTO, available from
506
	  <http://www.tldp.org/docs.html#howto>, and the file
507
	  <file:Documentation/scsi/dtc3x80.txt>.
508

509 510
	  To compile this driver as a module, choose M here: the
	  module will be called dtc.
511 512 513

config SCSI_EATA
	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
514
	depends on (ISA || EISA || PCI) && SCSI
515 516 517
	---help---
	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
	  ISA and all EISA I/O addresses are probed looking for the "EATA"
518 519
	  signature. The addresses of all the PCI SCSI controllers reported
          by the PCI subsystem are probed as well.
520 521 522

	  You want to read the start of <file:drivers/scsi/eata.c> and the
	  SCSI-HOWTO, available from
523
	  <http://www.tldp.org/docs.html#howto>.
524

525 526
	  To compile this driver as a module, choose M here: the
	  module will be called eata.
527 528 529 530 531 532 533

config SCSI_EATA_TAGGED_QUEUE
	bool "enable tagged command queueing"
	depends on SCSI_EATA
	help
	  This is a feature of SCSI-2 which improves performance: the host
	  adapter can send several SCSI commands to a device's queue even if
534 535
	  previous commands haven't finished yet.
	  This is equivalent to the "eata=tc:y" boot option.
536 537 538 539 540 541 542 543 544

config SCSI_EATA_LINKED_COMMANDS
	bool "enable elevator sorting"
	depends on SCSI_EATA
	help
	  This option enables elevator sorting for all probed SCSI disks and
	  CD-ROMs. It definitely reduces the average seek distance when doing
	  random seeks, but this does not necessarily result in a noticeable
	  performance improvement: your mileage may vary...
545
	  This is equivalent to the "eata=lc:y" boot option.
546 547 548 549 550 551 552 553 554 555 556 557

config SCSI_EATA_MAX_TAGS
	int "maximum number of queued commands"
	depends on SCSI_EATA
	default "16"
	help
	  This specifies how many SCSI commands can be maximally queued for
	  each probed SCSI device. You should reduce the default value of 16
	  only if you have disks with buggy or limited tagged command support.
	  Minimum is 2 and maximum is 62. This value is also the window size
	  used by the elevator sorting option above. The effective value used
	  by the driver for each probed SCSI device is reported at boot time.
558
	  This is equivalent to the "eata=mq:8" boot option.
559 560 561 562 563 564 565 566 567 568

config SCSI_EATA_PIO
	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
	depends on SCSI
	---help---
	  This driver supports all EATA-PIO protocol compliant SCSI Host
	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
	  host adapters could also use this driver but are discouraged from
	  doing so, since this driver only supports hard disks and lacks
	  numerous features.  You might want to have a look at the SCSI-HOWTO,
569
	  available from <http://www.tldp.org/docs.html#howto>.
570

571 572
	  To compile this driver as a module, choose M here: the
	  module will be called eata_pio.
573 574 575

config SCSI_FUTURE_DOMAIN
	tristate "Future Domain 16xx SCSI/AHA-2920A support"
576
	depends on (ISA || PCI) && SCSI
577 578 579 580 581 582
	---help---
	  This is support for Future Domain's 16-bit SCSI host adapters
	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
	  other adapters based on the Future Domain chipsets (Quantum
	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
	  It is explained in section 3.7 of the SCSI-HOWTO, available from
583
	  <http://www.tldp.org/docs.html#howto>.
584 585 586 587 588 589

	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
	  controller support"). This Future Domain driver works with the older
	  Adaptec AHA-2920A boards with a Future Domain chip on them.

590 591
	  To compile this driver as a module, choose M here: the
	  module will be called fdomain.
592 593 594 595 596 597 598 599 600 601 602

config SCSI_FD_MCS
	tristate "Future Domain MCS-600/700 SCSI support"
	depends on MCA && SCSI
	---help---
	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
	  is identical to the MCS 700 and hence also supported by this driver.
	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
	  It supports multiple adapters in the same system.

603 604
	  To compile this driver as a module, choose M here: the
	  module will be called fd_mcs.
605 606 607

config SCSI_GDTH
	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
608
	depends on (ISA || EISA || PCI) && SCSI
609 610 611 612
	---help---
	  Formerly called GDT SCSI Disk Array Controller Support.

	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
Achim Leubner's avatar
Achim Leubner committed
613
	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
614 615 616
	  in the kernel source in <file:drivers/scsi/gdth.c> and
	  <file:drivers/scsi/gdth.h.>

617 618
	  To compile this driver as a module, choose M here: the
	  module will be called gdth.
619 620 621

config SCSI_GENERIC_NCR5380
	tristate "Generic NCR5380/53c400 SCSI PIO support"
622
	depends on ISA && SCSI
623 624 625 626 627 628 629 630 631
	---help---
	  This is a driver for the old NCR 53c80 series of SCSI controllers
	  on boards using PIO. Most boards such as the Trantor T130 fit this
	  category, along with a large number of ISA 8bit controllers shipped
	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
	  you should select the specific driver for that card rather than
	  generic 5380 support.

	  It is explained in section 3.8 of the SCSI-HOWTO, available from
632
	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
633 634 635
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/g_NCR5380.h>.

636 637
	  To compile this driver as a module, choose M here: the
	  module will be called g_NCR5380.
638 639 640

config SCSI_GENERIC_NCR5380_MMIO
	tristate "Generic NCR5380/53c400 SCSI MMIO support"
641
	depends on ISA && SCSI
642 643 644 645
	---help---
	  This is a driver for the old NCR 53c80 series of SCSI controllers
	  on boards using memory mapped I/O. 
	  It is explained in section 3.8 of the SCSI-HOWTO, available from
646
	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
647 648 649
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/g_NCR5380.h>.

650 651
	  To compile this driver as a module, choose M here: the
	  module will be called g_NCR5380_mmio.
652 653 654 655 656 657 658 659 660 661

config SCSI_GENERIC_NCR53C400
	bool "Enable NCR53c400 extensions"
	depends on SCSI_GENERIC_NCR5380
	help
	  This enables certain optimizations for the NCR53c400 SCSI cards.
	  You might as well try it out.  Note that this driver will only probe
	  for the Trantor T130B in its default configuration; you might have
	  to pass a command line option to the kernel at boot time if it does
	  not detect your card.  See the file
662
	  <file:Documentation/scsi/g_NCR5380.txt> for details.
663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682

config SCSI_IBMMCA
	tristate "IBMMCA SCSI support"
	depends on MCA && SCSI
	---help---
	  This is support for the IBM SCSI adapter found in many of the PS/2
	  series computers.  These machines have an MCA bus, so you need to
	  answer Y to "MCA support" as well and read
	  <file:Documentation/mca.txt>.

	  If the adapter isn't found during boot (a common problem for models
	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
	  if that doesn't work check your reference diskette).  Owners of
	  model 95 with a LED-matrix-display can in addition activate some
	  activity info like under OS/2, but more informative, by setting
	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
	  bootparam" or see the documentation of your boot loader about how to
	  pass options to the kernel.

683 684
	  To compile this driver as a module, choose M here: the
	  module will be called ibmmca.
685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735

config IBMMCA_SCSI_ORDER_STANDARD
	bool "Standard SCSI-order"
	depends on SCSI_IBMMCA
	---help---
	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
	  are assigned to the drive letters, starting with the lowest SCSI-id
	  (physical number -- pun) to be drive C:, as seen from DOS and
	  similar operating systems. When looking into papers describing the
	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
	  The SCSI-standard follows a hardware-hierarchy which says that id 7
	  has the highest priority and id 0 the lowest. Therefore, the host
	  adapters are still today everywhere placed as SCSI-id 7 by default.
	  In the SCSI-standard, the drive letters express the priority of the
	  disk. C: should be the hard disk, or a partition on it, with the
	  highest priority. This must therefore be the disk with the highest
	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
	  original definition of the SCSI-standard as also industrial- and
	  process-control-machines, like VME-CPUs running under realtime-OSes
	  (e.g. LynxOS, OS9) do.

	  If you like to run Linux on your MCA-machine with the same
	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
	  machine, which is in addition conformant to the SCSI-standard, you
	  must say Y here. This is also necessary for MCA-Linux users who want
	  to keep downward compatibility to older releases of the
	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
	  June 1997).

	  If you like to have the lowest SCSI-id assigned as drive C:, as
	  modern SCSI-BIOSes do, which does not conform to the standard, but
	  is widespread and common in the PC-world of today, you must say N
	  here. If unsure, say Y.

config IBMMCA_SCSI_DEV_RESET
	bool "Reset SCSI-devices at boottime"
	depends on SCSI_IBMMCA
	---help---
	  By default, SCSI-devices are reset when the machine is powered on.
	  However, some devices exist, like special-control-devices,
	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
	  not reset when switched on. If you say Y here, each device connected
	  to your SCSI-bus will be issued a reset-command after it has been
	  probed, while the kernel is booting. This may cause problems with
	  more modern devices, like hard disks, which do not appreciate these
	  reset commands, and can cause your system to hang. So say Y only if
	  you know that one of your older devices needs it; N is the safe
	  answer.

config SCSI_IPS
	tristate "IBM ServeRAID support"
736
	depends on PCI && SCSI
737 738 739 740 741
	---help---
	  This is support for the IBM ServeRAID hardware RAID controllers.
	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
	  for more information.  If this driver does not work correctly
	  without modification please contact the author by email at
742
	  ipslinux@adaptec.com.
743

744 745
	  To compile this driver as a module, choose M here: the
	  module will be called ips.
746 747 748

config SCSI_INITIO
	tristate "Initio 9100U(W) support"
749
	depends on PCI && SCSI && BROKEN
750 751 752
	help
	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
	  read the SCSI-HOWTO, available from
753
	  <http://www.tldp.org/docs.html#howto>.
754

755 756
	  To compile this driver as a module, choose M here: the
	  module will be called initio.
757 758 759

config SCSI_INIA100
	tristate "Initio INI-A100U2W support"
760
	depends on PCI && SCSI
761 762 763
	help
	  This is support for the Initio INI-A100U2W SCSI host adapter.
	  Please read the SCSI-HOWTO, available from
764
	  <http://www.tldp.org/docs.html#howto>.
765

766 767
	  To compile this driver as a module, choose M here: the
	  module will be called a100u2w.
768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785

config SCSI_PPA
	tristate "IOMEGA parallel port (ppa - older drives)"
	depends on SCSI && PARPORT
	---help---
	  This driver supports older versions of IOMEGA's parallel port ZIP
	  drive (a 100 MB removable media device).

	  Note that you can say N here if you have the SCSI version of the ZIP
	  drive: it will be supported automatically if you said Y to the
	  generic "SCSI disk support", above.

	  If you have the ZIP Plus drive or a more recent parallel port ZIP
	  drive (if the supplied cable with the drive is labeled "AutoDetect")
	  then you should say N here and Y to "IOMEGA parallel port (imm -
	  newer drives)", below.

	  For more information about this driver and how to use it you should
786
	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
787
	  the SCSI-HOWTO, which is available from
788
	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
789 790 791 792
	  you will still be able to use the parallel port for other tasks,
	  such as a printer; it is safe to compile both drivers into the
	  kernel.

793 794
	  To compile this driver as a module, choose M here: the
	  module will be called ppa.
795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812

config SCSI_IMM
	tristate "IOMEGA parallel port (imm - newer drives)"
	depends on SCSI && PARPORT
	---help---
	  This driver supports newer versions of IOMEGA's parallel port ZIP
	  drive (a 100 MB removable media device).

	  Note that you can say N here if you have the SCSI version of the ZIP
	  drive: it will be supported automatically if you said Y to the
	  generic "SCSI disk support", above.

	  If you have the ZIP Plus drive or a more recent parallel port ZIP
	  drive (if the supplied cable with the drive is labeled "AutoDetect")
	  then you should say Y here; if you have an older ZIP drive, say N
	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.

	  For more information about this driver and how to use it you should
813
	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
814
	  the SCSI-HOWTO, which is available from
815
	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
816 817 818 819
	  you will still be able to use the parallel port for other tasks,
	  such as a printer; it is safe to compile both drivers into the
	  kernel.

820 821
	  To compile this driver as a module, choose M here: the
	  module will be called imm.
822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853

config SCSI_IZIP_EPP16
	bool "ppa/imm option - Use slow (but safe) EPP-16"
	depends on PARPORT && (SCSI_PPA || SCSI_IMM)
	---help---
	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
	  allows them to act as expansion buses that can handle up to 64
	  peripheral devices.

	  Some parallel port chipsets are slower than their motherboard, and
	  so we have to control the state of the chipset's FIFO queue every
	  now and then to avoid data loss. This will be done if you say Y
	  here.

	  Generally, saying Y is the safe option and slows things down a bit.

config SCSI_IZIP_SLOW_CTR
	bool "ppa/imm option - Assume slow parport control register"
	depends on PARPORT && (SCSI_PPA || SCSI_IMM)
	help
	  Some parallel ports are known to have excessive delays between
	  changing the parallel port control register and good data being
	  available on the parallel port data/status register. This option
	  forces a small delay (1.0 usec to be exact) after changing the
	  control register to let things settle out. Enabling this option may
	  result in a big drop in performance but some very old parallel ports
	  (found in 386 vintage machines) will not work properly.

	  Generally, saying N is fine.

config SCSI_NCR53C406A
	tristate "NCR53c406a SCSI support"
854
	depends on ISA && SCSI
855 856 857 858
	help
	  This is support for the NCR53c406a SCSI host adapter.  For user
	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
	  in the kernel source.  Also read the SCSI-HOWTO, available from
859
	  <http://www.tldp.org/docs.html#howto>.
860

861 862
	  To compile this driver as a module, choose M here: the
	  module will be called NCR53c406.
863 864 865 866

config SCSI_NCR_D700
	tristate "NCR Dual 700 MCA SCSI support"
	depends on MCA && SCSI
867
	select SCSI_SPI_ATTRS
868 869 870 871 872 873 874 875 876 877 878 879 880 881
	help
	  This is a driver for the MicroChannel Dual 700 card produced by
	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
	  tries to negotiate sync and uses tag command queueing.

	  Unless you have an NCR manufactured machine, the chances are that
	  you do not have this SCSI card, so say N.

config 53C700_IO_MAPPED
	bool
	depends on SCSI_NCR_D700
	default y

config SCSI_LASI700
882 883
	tristate "HP Lasi SCSI support for 53c700/710"
	depends on GSC && SCSI
884
	select SCSI_SPI_ATTRS
885
	help
886 887 888
	  This is a driver for the SCSI controller in the Lasi chip found in
	  many PA-RISC workstations & servers.  If you do not know whether you
	  have a Lasi chip, it is safe to say "Y" here.
889 890 891 892 893 894 895 896 897 898 899 900 901 902 903

config 53C700_MEM_MAPPED
	bool
	depends on SCSI_LASI700
	default y

config 53C700_LE_ON_BE
	bool
	depends on SCSI_LASI700
	default y

config SCSI_SYM53C8XX_2
	tristate "SYM53C8XX Version 2 SCSI support"
	depends on PCI && SCSI
	---help---
904 905 906 907 908
	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
	  controllers; you need to use the Fusion MPT driver for that.
909

910
	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
911 912 913 914 915 916 917
	  information.

config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
	int "DMA addressing mode"
	depends on SCSI_SYM53C8XX_2
	default "1"
	---help---
James Bottomley's avatar
James Bottomley committed
918 919
	  This option only applies to PCI-SCSI chips that are PCI DAC
	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
920

James Bottomley's avatar
James Bottomley committed
921 922 923 924 925
	  When set to 0, the driver will program the chip to only perform
	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
	  to addresses up to 1TB.  When set to 2, the driver supports the
	  full 64-bit DMA address range, but can only address 16 segments
	  of 4 GB each.  This limits the total addressable range to 64 GB.
926

James Bottomley's avatar
James Bottomley committed
927 928 929
	  Most machines with less than 4GB of memory should use a setting
	  of 0 for best performance.  If your machine has 4GB of memory
	  or more, you should set this option to 1 (the default).
930

James Bottomley's avatar
James Bottomley committed
931 932 933 934
	  The still experimental value 2 (64 bit DMA addressing with 16
	  x 4GB segments limitation) can be used on systems that require
	  PCI address bits past bit 39 to be set for the addressing of
	  memory using PCI DAC cycles.
935 936 937 938 939 940

config SCSI_SYM53C8XX_DEFAULT_TAGS
	int "default tagged command queue depth"
	depends on SCSI_SYM53C8XX_2
	default "16"
	help
James Bottomley's avatar
James Bottomley committed
941 942 943 944 945
	  This is the default value of the command queue depth the
	  driver will announce to the generic SCSI layer for devices
	  that support tagged command queueing. This value can be changed
	  from the boot command line.  This is a soft limit that cannot
	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
946 947 948 949 950 951 952 953 954 955 956 957

config SCSI_SYM53C8XX_MAX_TAGS
	int "maximum number of queued commands"
	depends on SCSI_SYM53C8XX_2
	default "64"
	help
	  This option allows you to specify the maximum number of commands
	  that can be queued to any device, when tagged command queuing is
	  possible. The driver supports up to 256 queued commands per device.
	  This value is used as a compiled-in hard limit.

config SCSI_SYM53C8XX_IOMAPPED
James Bottomley's avatar
James Bottomley committed
958
	bool "use port IO"
959 960
	depends on SCSI_SYM53C8XX_2
	help
James Bottomley's avatar
James Bottomley committed
961 962 963
	  If you say Y here, the driver will use port IO to access
	  the card.  This is significantly slower then using memory
	  mapped IO.  Most people should answer N.
964

965 966 967 968 969 970 971 972 973 974
config SCSI_ZALON
	tristate "Zalon SCSI support"
	depends on GSC && SCSI
	help
	  The Zalon is a GSC/HSC bus interface chip that sits between the
	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
	  C110, J200, J210 and some D, K & R-class machines.  It's also
	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
	  Say Y here if you have one of these machines or cards.

975 976 977 978 979 980 981
config SCSI_NCR_Q720
	tristate "NCR Quad 720 MCA SCSI support"
	depends on MCA && SCSI
	help
	  This is a driver for the MicroChannel Quad 720 card produced by
	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
	  tries to negotiate sync and uses tag command queueing.
982

983 984
	  Unless you have an NCR manufactured machine, the chances are that
	  you do not have this SCSI card, so say N.
985 986

config SCSI_NCR53C8XX_DEFAULT_TAGS
987
	int "  default tagged command queue depth"
Matthew Wilcox's avatar
Matthew Wilcox committed
988
	depends on SCSI_ZALON || SCSI_NCR_Q720
989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012
	default "8"
	---help---
	  "Tagged command queuing" is a feature of SCSI-2 which improves
	  performance: the host adapter can send several SCSI commands to a
	  device's queue even if previous commands haven't finished yet.
	  Because the device is intelligent, it can optimize its operations
	  (like head positioning) based on its own request queue. Some SCSI
	  devices don't implement this properly; if you want to disable this
	  feature, enter 0 or 1 here (it doesn't matter which).

	  The default value is 8 and should be supported by most hard disks.
	  This value can be overridden from the boot command line using the
	  'tags' option as follows (example):
	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
	  4, set queue depth to 16 for target 2 and target 3 on controller 0
	  and set queue depth to 10 for target 0 / lun 2 on controller 1.

	  The normal answer therefore is to go with the default 8 and to use
	  a boot command line option for devices that need to use a different
	  command queue depth.

	  There is no safe option other than using good SCSI devices.

config SCSI_NCR53C8XX_MAX_TAGS
1013
	int "  maximum number of queued commands"
Matthew Wilcox's avatar
Matthew Wilcox committed
1014
	depends on SCSI_ZALON || SCSI_NCR_Q720
1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029
	default "32"
	---help---
	  This option allows you to specify the maximum number of commands
	  that can be queued to any device, when tagged command queuing is
	  possible. The default value is 32. Minimum is 2, maximum is 64.
	  Modern hard disks are able to support 64 tags and even more, but
	  do not seem to be faster when more than 32 tags are being used.

	  So, the normal answer here is to go with the default value 32 unless
	  you are using very large hard disks with large cache (>= 1 MB) that
	  are able to take advantage of more than 32 tagged commands.

	  There is no safe option and the default answer is recommended.

config SCSI_NCR53C8XX_SYNC
1030
	int "  synchronous transfers frequency in MHz"
Matthew Wilcox's avatar
Matthew Wilcox committed
1031
	depends on SCSI_ZALON || SCSI_NCR_Q720
1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063
	default "20"
	---help---
	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
	  are respectively the maximum data transfer rates in mega-transfers
	  per second for each class.  For example, a FAST-20 Wide 16 device is
	  able to transfer data at 20 million 16 bit packets per second for a
	  total rate of 40 MB/s.

	  You may specify 0 if you want to only use asynchronous data
	  transfers. This is the safest and slowest option. Otherwise, specify
	  a value between 5 and 80, depending on the capability of your SCSI
	  controller.  The higher the number, the faster the data transfer.
	  Note that 80 should normally be ok since the driver decreases the
	  value automatically according to the controller's capabilities.

	  Your answer to this question is ignored for controllers with NVRAM,
	  since the driver will get this information from the user set-up.  It
	  also can be overridden using a boot setup option, as follows
	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
	  for FAST-20 synchronous data transfer (20 mega-transfers per
	  second).

	  The normal answer therefore is not to go with the default but to
	  select the maximum value 80 allowing the driver to use the maximum
	  value supported by each controller. If this causes problems with
	  your SCSI devices, you should come back and decrease the value.

	  There is no safe option other than using good cabling, right
	  terminations and SCSI conformant devices.

config SCSI_NCR53C8XX_PROFILE
1064
	bool "  enable profiling"
Matthew Wilcox's avatar
Matthew Wilcox committed
1065
	depends on SCSI_ZALON || SCSI_NCR_Q720
1066 1067 1068 1069 1070 1071 1072 1073 1074
	help
	  This option allows you to enable profiling information gathering.
	  These statistics are not very accurate due to the low frequency
	  of the kernel clock (100 Hz on i386) and have performance impact
	  on systems that use very fast devices.

	  The normal answer therefore is N.

config SCSI_NCR53C8XX_NO_DISCONNECT
1075
	bool "  not allow targets to disconnect"
Matthew Wilcox's avatar
Matthew Wilcox committed
1076
	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1077 1078 1079 1080 1081 1082 1083 1084 1085
	help
	  This option is only provided for safety if you suspect some SCSI
	  device of yours to not support properly the target-disconnect
	  feature. In that case, you would say Y here. In general however, to
	  not allow targets to disconnect is not reasonable if there is more
	  than 1 device on a SCSI bus. The normal answer therefore is N.

config SCSI_MCA_53C9X
	tristate "NCR MCA 53C9x SCSI support"
1086
	depends on MCA && SCSI && BROKEN_ON_SMP
1087 1088 1089 1090 1091
	help
	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
	  controller based on the NCR 53C94.  This driver will allow use of
	  the controller on the 3550, and very possibly others.

1092 1093
	  To compile this driver as a module, choose M here: the
	  module will be called mca_53c9x.
1094 1095 1096

config SCSI_PAS16
	tristate "PAS16 SCSI support"
1097
	depends on ISA && SCSI
1098 1099 1100
	---help---
	  This is support for a SCSI host adapter.  It is explained in section
	  3.10 of the SCSI-HOWTO, available from
1101
	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1102 1103 1104
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/pas16.h>.

1105 1106
	  To compile this driver as a module, choose M here: the
	  module will be called pas16.
1107 1108 1109

config SCSI_PCI2000
	tristate "PCI2000 support"
1110
	depends on PCI && SCSI && BROKEN
1111 1112 1113
	help
	  This is support for the PCI2000I EIDE interface card which acts as a
	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
1114
	  <http://www.tldp.org/docs.html#howto>.
1115

1116 1117
	  To compile this driver as a module, choose M here: the
	  module will be called pci2000.
1118 1119 1120

config SCSI_PCI2220I
	tristate "PCI2220i support"
1121
	depends on PCI && SCSI && BROKEN
1122 1123 1124
	help
	  This is support for the PCI2220i EIDE interface card which acts as a
	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
1125
	  <http://www.tldp.org/docs.html#howto>.
1126

1127 1128
	  To compile this driver as a module, choose M here: the
	  module will be called pci2220i.
1129 1130 1131

config SCSI_PSI240I
	tristate "PSI240i support"
1132
	depends on ISA && SCSI
1133 1134 1135
	help
	  This is support for the PSI240i EIDE interface card which acts as a
	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
1136
	  <http://www.tldp.org/docs.html#howto>.
1137

1138 1139
	  To compile this driver as a module, choose M here: the
	  module will be called psi240i.
1140 1141 1142

config SCSI_QLOGIC_FAS
	tristate "Qlogic FAS SCSI support"
1143
	depends on ISA && SCSI
1144 1145 1146 1147 1148 1149 1150 1151 1152 1153
	---help---
	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
	  FastSCSI! cards as well as any other card based on the FASXX chip
	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).

	  This driver does NOT support the PCI versions of these cards. The
	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
	  SCSI support"), below.

	  Information about this driver is contained in
1154
	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
1155
	  SCSI-HOWTO, available from
1156
	  <http://www.tldp.org/docs.html#howto>.
1157

1158 1159
	  To compile this driver as a module, choose M here: the
	  module will be called qlogicfas.
1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171

config SCSI_QLOGIC_ISP
	tristate "Qlogic ISP SCSI support"
	depends on PCI && SCSI
	---help---
	  This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
	  IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card.  (This latter
	  card is supported by the "AM53/79C974 PCI SCSI" driver.)

	  If you say Y here, make sure to choose "BIOS" at the question "PCI
	  access mode".

1172
	  Please read the file <file:Documentation/scsi/qlogicisp.txt>.  You
1173
	  should also read the SCSI-HOWTO, available from
1174
	  <http://www.tldp.org/docs.html#howto>.
1175

1176 1177
	  To compile this driver as a module, choose M here: the
	  module will be called qlogicisp.
1178

1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195
config SCSI_QLOGIC_FC
	tristate "Qlogic ISP FC SCSI support"
	depends on PCI && SCSI
	help
	  This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.

	  To compile this driver as a module, choose M here: the
	  module will be called qlogicfc.

config SCSI_QLOGIC_FC_FIRMWARE
	bool "Include loadable firmware in driver"
	depends on SCSI_QLOGIC_FC
  	help
	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
	  expanded LUN addressing and FcTape (FCP-2) support, in the
	  qlogicfc driver. This is required on some platforms.

1196 1197 1198 1199 1200 1201
config SCSI_QLOGIC_1280
	tristate "Qlogic QLA 1280 SCSI support"
	depends on PCI && SCSI
	help
	  Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.

1202 1203
	  To compile this driver as a module, choose M here: the
	  module will be called qla1280.
1204

1205 1206 1207 1208 1209 1210 1211 1212 1213
config SCSI_QLOGICPTI
	tristate "PTI Qlogic, ISP Driver"
	depends on SBUS && SCSI
	help
	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
	  controllers are known under Solaris as qpti and in the openprom as
	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
	  driven by a different driver.

1214 1215
	  To compile this driver as a module, choose M here: the
	  module will be called qlogicpti.
1216

James Bottomley's avatar
James Bottomley committed
1217 1218
source "drivers/scsi/qla2xxx/Kconfig"

1219 1220
config SCSI_SEAGATE
	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
1221
	depends on X86 && ISA && SCSI && BROKEN
1222 1223 1224
	---help---
	  These are 8-bit SCSI controllers; the ST-01 is also supported by
	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
1225
	  available from <http://www.tldp.org/docs.html#howto>.  If it
1226 1227 1228
	  doesn't work out of the box, you may have to change some settings in
	  <file:drivers/scsi/seagate.h>.

1229 1230
	  To compile this driver as a module, choose M here: the
	  module will be called seagate.
1231

1232
# definitely looks not 64bit safe:
1233 1234
config SCSI_SIM710
	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1235
	depends on (EISA || MCA) && SCSI
1236
	select SCSI_SPI_ATTRS
1237
	---help---
1238
	  This driver for NCR53c710 based SCSI host adapters.
1239

1240
	  It currently supports Compaq EISA cards and NCR MCA cards
1241

1242 1243 1244 1245
config 53C700_IO_MAPPED
	bool
	depends on SCSI_SIM710
	default y
1246 1247 1248

config SCSI_SYM53C416
	tristate "Symbios 53c416 SCSI support"
1249
	depends on ISA && SCSI
1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261
	---help---
	  This is support for the sym53c416 SCSI host adapter, the SCSI
	  adapter that comes with some HP scanners. This driver requires that
	  the sym53c416 is configured first using some sort of PnP
	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
	  are using isapnp then you need to compile this driver as a module
	  and then load it using insmod after isapnp has run. The parameters
	  of the configured card(s) should be passed to the driver. The format
	  is:

	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]

1262 1263
	  To compile this driver as a module, choose M here: the
	  module will be called sym53c416.
1264

Oliver Neukum's avatar
Oliver Neukum committed
1265 1266
config SCSI_DC395x
	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
1267
	depends on PCI && SCSI && EXPERIMENTAL
Oliver Neukum's avatar
Oliver Neukum committed
1268 1269 1270 1271 1272 1273 1274 1275 1276
	---help---
	  This driver supports PCI SCSI host adapters based on the ASIC
	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.

	  This driver works, but is still in experimental status. So better
	  have a bootable disk and a backup in case of emergency.

	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.

1277 1278
	  To compile this driver as a module, choose M here: the
	  module will be called dc395x.
Oliver Neukum's avatar
Oliver Neukum committed
1279

1280 1281
config SCSI_DC390T
	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
James Bottomley's avatar
James Bottomley committed
1282
	depends on PCI && SCSI
1283 1284 1285 1286 1287
	---help---
	  This driver supports PCI SCSI host adapters based on the Am53C974A
	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
	  PCscsi/PCnet (Am53/79C974) solutions.

1288
	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
1289 1290 1291 1292

	  Note that this driver does NOT support Tekram DC390W/U/F, which are
	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.

1293 1294
	  To compile this driver as a module, choose M here: the
	  module will be called tmscsim.
1295 1296 1297

config SCSI_T128
	tristate "Trantor T128/T128F/T228 SCSI support"
1298
	depends on ISA && SCSI
1299 1300 1301
	---help---
	  This is support for a SCSI host adapter. It is explained in section
	  3.11 of the SCSI-HOWTO, available from
1302
	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1303 1304 1305 1306 1307
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
	  Adaptec, and some former Trantor products are being sold under the
	  Adaptec name.

1308 1309
	  To compile this driver as a module, choose M here: the
	  module will be called t128.
1310 1311 1312

config SCSI_U14_34F
	tristate "UltraStor 14F/34F support"
1313
	depends on ISA && SCSI
1314 1315 1316 1317 1318 1319
	---help---
	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
	  The source at <file:drivers/scsi/u14-34f.c> contains some
	  information about this hardware.  If the driver doesn't work out of
	  the box, you may have to change some settings in
	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
1320
	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
1321 1322 1323 1324
	  another driver for the same hardware: "UltraStor SCSI support",
	  below.  You should say Y to both only if you want 24F support as
	  well.

1325 1326
	  To compile this driver as a module, choose M here: the
	  module will be called u14-34f.
1327

1328 1329 1330 1331 1332 1333 1334 1335 1336
config SCSI_U14_34F_TAGGED_QUEUE
	bool "enable tagged command queueing"
	depends on SCSI_U14_34F
	help
	  This is a feature of SCSI-2 which improves performance: the host
	  adapter can send several SCSI commands to a device's queue even if
	  previous commands haven't finished yet.
	  This is equivalent to the "u14-34f=tc:y" boot option.

1337 1338 1339 1340 1341 1342 1343 1344
config SCSI_U14_34F_LINKED_COMMANDS
	bool "enable elevator sorting"
	depends on SCSI_U14_34F
	help
	  This option enables elevator sorting for all probed SCSI disks and
	  CD-ROMs. It definitely reduces the average seek distance when doing
	  random seeks, but this does not necessarily result in a noticeable
	  performance improvement: your mileage may vary...
1345
	  This is equivalent to the "u14-34f=lc:y" boot option.
1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357

config SCSI_U14_34F_MAX_TAGS
	int "maximum number of queued commands"
	depends on SCSI_U14_34F
	default "8"
	help
	  This specifies how many SCSI commands can be maximally queued for
	  each probed SCSI device. You should reduce the default value of 8
	  only if you have disks with buggy or limited tagged command support.
	  Minimum is 2 and maximum is 14. This value is also the window size
	  used by the elevator sorting option above. The effective value used
	  by the driver for each probed SCSI device is reported at boot time.
1358
	  This is equivalent to the "u14-34f=mq:8" boot option.
1359 1360 1361 1362 1363 1364 1365 1366

config SCSI_ULTRASTOR
	tristate "UltraStor SCSI support"
	depends on X86 && ISA && SCSI
	---help---
	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
	  adapter family.  This driver is explained in section 3.12 of the
	  SCSI-HOWTO, available from
1367
	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
1368 1369 1370 1371 1372 1373
	  of the box, you may have to change some settings in
	  <file:drivers/scsi/ultrastor.h>.

	  Note that there is also another driver for the same hardware:
	  "UltraStor 14F/34F support", above.

1374 1375
	  To compile this driver as a module, choose M here: the
	  module will be called ultrastor.
1376 1377 1378

config SCSI_NSP32
	tristate "Workbit NinjaSCSI-32Bi/UDE support"
1379
	depends on PCI && SCSI && !64BIT
1380 1381 1382
	help
	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
	  SCSI host adapter. Please read the SCSI-HOWTO, available from
1383
	  <http://www.tldp.org/docs.html#howto>.
1384

1385 1386
	  To compile this driver as a module, choose M here: the
	  module will be called nsp32.
1387 1388

config SCSI_DEBUG
1389 1390
	tristate "SCSI debugging host simulator"
	depends on SCSI
1391
	help
1392 1393 1394 1395 1396 1397 1398 1399
	  This is a host adapter simulator that can simulate multiple hosts
	  each with multiple dummy SCSI devices (disks). It defaults to one
	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
	  dummy disks are simulated, they share the same kernel RAM for 
	  their storage. See http://www.torque.net/sg/sdebug.html for more
	  information. This driver is primarily of use to those testing the
	  SCSI and block subsystems. If unsure, say N.
1400 1401 1402

config SCSI_MESH
	tristate "MESH (Power Mac internal SCSI) support"
1403
	depends on PPC_PMAC && SCSI
1404 1405 1406 1407
	help
	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
	  other Power Macintoshes do). Say Y to include support for this SCSI
1408 1409 1410 1411
	  adaptor.

	  To compile this driver as a module, choose M here: the
	  module will be called mesh.
1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433

config SCSI_MESH_SYNC_RATE
	int "maximum synchronous transfer rate (MB/s) (0 = async)"
	depends on SCSI_MESH
	default "5"
	help
	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
	  drives a bus which is entirely internal to the machine (such as the
	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
	  operation at up to 10 MB/s. On machines where the SCSI bus
	  controlled by the MESH can have external devices connected, it is
	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
	  to disable synchronous operation.

config SCSI_MESH_RESET_DELAY_MS
	int "initial bus reset delay (ms) (0 = no reset)"
	depends on SCSI_MESH
	default "4000"

config SCSI_MAC53C94
	tristate "53C94 (Power Mac external SCSI) support"
1434
	depends on PPC_PMAC && SCSI
1435 1436 1437 1438 1439 1440
	help
	  On Power Macintoshes (and clones) with two SCSI buses, the external
	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
	  machines which only have one SCSI bus, such as the 7200, also use
	  the 53C94. Say Y to include support for the 53C94.

1441 1442
	  To compile this driver as a module, choose M here: the
	  module will be called mac53c94.
1443

1444
source "drivers/scsi/arm/Kconfig"
1445 1446 1447

config JAZZ_ESP
	bool "MIPS JAZZ FAS216 SCSI support"
1448
	depends on MIPS_JAZZ && SCSI
1449 1450 1451 1452 1453 1454 1455 1456 1457 1458
	help
	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
	  systems.

config A3000_SCSI
	tristate "A3000 WD33C93A support"
	depends on AMIGA && SCSI
	help
	  If you have an Amiga 3000 and have SCSI devices connected to the
1459 1460 1461 1462
	  built-in SCSI controller, say Y. Otherwise, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called wd33c93.
1463 1464 1465

config A2091_SCSI
	tristate "A2091/A590 WD33C93A support"
1466
	depends on ZORRO && SCSI
1467 1468
	help
	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1469 1470 1471 1472
	  say N.

	  To compile this driver as a module, choose M here: the
	  module will be called wd33c93.
1473 1474 1475

config GVP11_SCSI
	tristate "GVP Series II WD33C93A support"
1476
	depends on ZORRO && SCSI
1477 1478 1479 1480 1481 1482 1483
	---help---
	  If you have a Great Valley Products Series II SCSI controller,
	  answer Y. Also say Y if you have a later model of GVP SCSI
	  controller (such as the GVP A4008 or a Combo board). Otherwise,
	  answer N. This driver does NOT work for the T-Rex series of
	  accelerators from TekMagic and GVP-M.

1484 1485
	  To compile this driver as a module, choose M here: the
	  module will be called gvp11.
1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525

config CYBERSTORM_SCSI
	tristate "CyberStorm SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
	  accelerator board and the optional Cyberstorm SCSI controller,
	  answer Y. Otherwise, say N.

config CYBERSTORMII_SCSI
	tristate "CyberStorm Mk II SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
	  answer N.

config BLZ2060_SCSI
	tristate "Blizzard 2060 SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
	  and want to use the onboard SCSI controller, say Y. Otherwise,
	  answer N.

config BLZ1230_SCSI
	tristate "Blizzard 1230IV/1260 SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
	  say N.

config FASTLANE_SCSI
	tristate "Fastlane SCSI support"
	depends on ZORRO && SCSI
	help
	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
	  one in the near future, say Y to this question. Otherwise, say N.

1526 1527 1528
config SCSI_AMIGA7XX
	bool "Amiga NCR53c710 SCSI support (EXPERIMENTAL)"
	depends on AMIGA && SCSI && EXPERIMENTAL && BROKEN
1529
	help
1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543
	  Support for various NCR53c710-based SCSI controllers on the Amiga.
	  This includes:
	    - the builtin SCSI controller on the Amiga 4000T,
	    - the Amiga 4091 Zorro III SCSI-2 controller,
	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
	      (info at
	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
	      accelerator card for the Amiga 1200,
	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
	  Note that all of the above SCSI controllers, except for the builtin
	  SCSI controller on the Amiga 4000T, reside on the Zorro expansion
	  bus, so you also have to enable Zorro bus support if you want to use
	  them.
1544 1545 1546

config OKTAGON_SCSI
	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1547
	depends on ZORRO && SCSI && EXPERIMENTAL
1548 1549 1550 1551
	help
	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
	  Y to this question.  If you're in doubt about whether you have one,
	  see the picture at
1552
	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
1553

1554 1555
config ATARI_SCSI
	tristate "Atari native SCSI support"
1556
	depends on ATARI && SCSI && BROKEN
1557 1558 1559
	---help---
	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
	  Falcon, ...) say Y to get it supported. Of course also, if you have
1560 1561 1562 1563 1564 1565 1566 1567 1568
	  a compatible SCSI controller (e.g. for Medusa).

	  To compile this driver as a module, choose M here: the
	  module will be called atari_scsi.

	  This driver supports both styles of NCR integration into the
	  system: the TT style (separate DMA), and the Falcon style (via
	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
	  in the Hades (without DMA).
1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612

config ATARI_SCSI_TOSHIBA_DELAY
	bool "Long delays for Toshiba CD-ROMs"
	depends on ATARI_SCSI
	help
	  This option increases the delay after a SCSI arbitration to
	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
	  would impact performance a bit, so say N.

config ATARI_SCSI_RESET_BOOT
	bool "Reset SCSI-devices at boottime"
	depends on ATARI_SCSI
	help
	  Reset the devices on your Atari whenever it boots.  This makes the
	  boot process fractionally longer but may assist recovery from errors
	  that leave the devices with SCSI operations partway completed.

config TT_DMA_EMUL
	bool "Hades SCSI DMA emulator"
	depends on ATARI_SCSI && HADES
	help
	  This option enables code which emulates the TT SCSI DMA chip on the
	  Hades. This increases the SCSI transfer rates at least ten times
	  compared to PIO transfers.

config MAC_SCSI
	bool "Macintosh NCR5380 SCSI"
	depends on MAC && SCSI
	help
	  This is the NCR 5380 SCSI controller included on most of the 68030
	  based Macintoshes.  If you have one of these say Y and read the
	  SCSI-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

config SCSI_MAC_ESP
	tristate "Macintosh NCR53c9[46] SCSI"
	depends on MAC && SCSI
	help
	  This is the NCR 53c9x SCSI controller found on most of the 68040
	  based Macintoshes.  If you have one of these say Y and read the
	  SCSI-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

1613 1614
	  To compile this driver as a module, choose M here: the
	  module will be called mac_esp.
1615 1616 1617 1618 1619 1620 1621 1622 1623 1624

config MVME147_SCSI
	bool "WD33C93 SCSI driver for MVME147"
	depends on MVME147 && SCSI
	help
	  Support for the on-board SCSI controller on the Motorola MVME147
	  single-board computer.

config MVME16x_SCSI
	bool "NCR53C710 SCSI driver for MVME16x"
1625
	depends on MVME16x && SCSI && BROKEN
1626 1627 1628 1629 1630 1631 1632
	help
	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
	  SCSI controller chip.  Almost everyone using one of these boards
	  will want to say Y to this question.

config BVME6000_SCSI
	bool "NCR53C710 SCSI driver for BVME6000"
1633
	depends on BVME6000 && SCSI && BROKEN
1634 1635 1636 1637 1638 1639 1640
	help
	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
	  SCSI controller chip.  Almost everyone using one of these boards
	  will want to say Y to this question.

config SCSI_NCR53C7xx_FAST
	bool "allow FAST-SCSI [10MHz]"
1641
	depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670
	help
	  This will enable 10MHz FAST-SCSI transfers with your host
	  adapter. Some systems have problems with that speed, so it's safest
	  to say N here.

config SUN3_SCSI
	tristate "Sun3 NCR5380 SCSI"
	depends on SUN3 && SCSI
	help
	  This option will enable support for the OBIO (onboard io) NCR5380
	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
	  "Sun3" type VME scsi controllers also based on the NCR5380.
	  General Linux information on the Sun 3 series (now discontinued)
	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.

config SUN3X_ESP
	bool "Sun3x ESP SCSI"
	depends on SUN3X && SCSI
	help
	  The ESP was an on-board SCSI controller used on Sun 3/80
	  machines.  Say Y here to compile in support for it.

config SCSI_SUNESP
	tristate "Sparc ESP Scsi Driver"
	depends on SBUS && SCSI
	help
	  This is the driver for the Sun ESP SCSI host adapter. The ESP
	  chipset is present in most SPARC SBUS-based computers.

1671 1672
	  To compile this driver as a module, choose M here: the
	  module will be called esp.
1673

1674 1675 1676 1677 1678 1679 1680
config SCSI_PC980155
	tristate "NEC PC-9801-55 SCSI support"
	depends on X86_PC9800 && SCSI
	help
	  If you have the NEC PC-9801-55 SCSI interface card or compatibles
	  for NEC PC-9801/PC-9821, say Y.

1681 1682 1683 1684 1685
config WD33C93_PIO
	bool
	depends on SCSI_PC980155
	default y

1686
#      bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1687 1688 1689 1690 1691

config ZFCP
	tristate "IBM z900 OpenFCP/SCSI support"
	depends on ARCH_S390 && SCSI

1692 1693 1694 1695
endmenu

source "drivers/scsi/pcmcia/Kconfig"

1696
endmenu