Kconfig 69 KB

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