Kconfig 40 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091
  1. #
  2. # IDE ATA ATAPI Block device driver configuration
  3. #
  4. # Andre Hedrick <andre@linux-ide.org>
  5. #
  6. if BLOCK
  7. menu "ATA/ATAPI/MFM/RLL support"
  8. config IDE
  9. tristate "ATA/ATAPI/MFM/RLL support"
  10. ---help---
  11. If you say Y here, your kernel will be able to manage low cost mass
  12. storage units such as ATA/(E)IDE and ATAPI units. The most common
  13. cases are IDE hard drives and ATAPI CD-ROM drives.
  14. If your system is pure SCSI and doesn't use these interfaces, you
  15. can say N here.
  16. Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
  17. for mass storage units such as hard disks. It was designed by
  18. Western Digital and Compaq Computer in 1984. It was then named
  19. ST506. Quite a number of disks use the IDE interface.
  20. AT Attachment (ATA) is the superset of the IDE specifications.
  21. ST506 was also called ATA-1.
  22. Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
  23. ATA-3. It provides support for larger disks (up to 8.4GB by means of
  24. the LBA standard), more disks (4 instead of 2) and for other mass
  25. storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
  26. ATA-4 and provides faster (and more CPU friendly) transfer modes
  27. than previous PIO (Programmed processor Input/Output) from previous
  28. ATA/IDE standards by means of fast DMA controllers.
  29. ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
  30. CD-ROM drives, similar in many respects to the SCSI protocol.
  31. SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
  32. designed in order to prevent data corruption and disk crash by
  33. detecting pre hardware failure conditions (heat, access time, and
  34. the like...). Disks built since June 1995 may follow this standard.
  35. The kernel itself doesn't manage this; however there are quite a
  36. number of user programs such as smart that can query the status of
  37. SMART parameters from disk drives.
  38. To compile this driver as a module, choose M here: the
  39. module will be called ide.
  40. For further information, please read <file:Documentation/ide.txt>.
  41. If unsure, say Y.
  42. if IDE
  43. config IDE_MAX_HWIFS
  44. int "Max IDE interfaces"
  45. depends on ALPHA || SUPERH || IA64 || EMBEDDED
  46. range 1 10
  47. default 4
  48. help
  49. This is the maximum number of IDE hardware interfaces that will
  50. be supported by the driver. Make sure it is at least as high as
  51. the number of IDE interfaces in your system.
  52. config BLK_DEV_IDE
  53. tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
  54. ---help---
  55. If you say Y here, you will use the full-featured IDE driver to
  56. control up to ten ATA/IDE interfaces, each being able to serve a
  57. "master" and a "slave" device, for a total of up to twenty ATA/IDE
  58. disk/cdrom/tape/floppy drives.
  59. Useful information about large (>540 MB) IDE disks, multiple
  60. interfaces, what to do if ATA/IDE devices are not automatically
  61. detected, sound card ATA/IDE ports, module support, and other
  62. topics, is contained in <file:Documentation/ide.txt>. For detailed
  63. information about hard drives, consult the Disk-HOWTO and the
  64. Multi-Disk-HOWTO, available from
  65. <http://www.tldp.org/docs.html#howto>.
  66. To fine-tune ATA/IDE drive/interface parameters for improved
  67. performance, look for the hdparm package at
  68. <ftp://ibiblio.org/pub/Linux/system/hardware/>.
  69. To compile this driver as a module, choose M here and read
  70. <file:Documentation/ide.txt>. The module will be called ide-mod.
  71. Do not compile this driver as a module if your root file system (the
  72. one containing the directory /) is located on an IDE device.
  73. If you have one or more IDE drives, say Y or M here. If your system
  74. has no IDE drives, or if memory requirements are really tight, you
  75. could say N here, and select the "Old hard disk driver" below
  76. instead to save about 13 KB of memory in the kernel.
  77. if BLK_DEV_IDE
  78. comment "Please see Documentation/ide.txt for help/info on IDE drives"
  79. config BLK_DEV_IDE_SATA
  80. bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
  81. default n
  82. ---help---
  83. There are two drivers for Serial ATA controllers.
  84. The main driver, "libata", uses the SCSI subsystem
  85. and supports most modern SATA controllers. In order to use it
  86. you may take a look at "Serial ATA (prod) and Parallel ATA
  87. (experimental) drivers".
  88. The IDE driver (which you are currently configuring) supports
  89. a few first-generation SATA controllers.
  90. In order to eliminate conflicts between the two subsystems,
  91. this config option enables the IDE driver's SATA support.
  92. Normally this is disabled, as it is preferred that libata
  93. supports SATA controllers, and this (IDE) driver supports
  94. PATA controllers.
  95. If unsure, say N.
  96. config BLK_DEV_HD_IDE
  97. bool "Use old disk-only driver on primary interface"
  98. depends on (X86 || SH_MPC1211)
  99. ---help---
  100. There are two drivers for MFM/RLL/IDE disks. Most people use just
  101. the new enhanced driver by itself. This option however installs the
  102. old hard disk driver to control the primary IDE/disk interface in
  103. the system, leaving the new enhanced IDE driver to take care of only
  104. the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
  105. having an IDE/ATAPI CD-ROM or tape drive connected to the primary
  106. IDE interface. Choosing this option may be useful for older systems
  107. which have MFM/RLL/ESDI controller+drives at the primary port
  108. address (0x1f0), along with IDE drives at the secondary/3rd/4th port
  109. addresses.
  110. Normally, just say N here; you will then use the new driver for all
  111. 4 interfaces.
  112. config BLK_DEV_IDEDISK
  113. tristate "Include IDE/ATA-2 DISK support"
  114. ---help---
  115. This will include enhanced support for MFM/RLL/IDE hard disks. If
  116. you have a MFM/RLL/IDE disk, and there is no special reason to use
  117. the old hard disk driver instead, say Y. If you have an SCSI-only
  118. system, you can say N here.
  119. To compile this driver as a module, choose M here: the
  120. module will be called ide-disk.
  121. Do not compile this driver as a module if your root file system
  122. (the one containing the directory /) is located on the IDE disk.
  123. If unsure, say Y.
  124. config IDEDISK_MULTI_MODE
  125. bool "Use multi-mode by default"
  126. help
  127. If you get this error, try to say Y here:
  128. hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
  129. hda: set_multmode: error=0x04 { DriveStatusError }
  130. If in doubt, say N.
  131. config BLK_DEV_IDECS
  132. tristate "PCMCIA IDE support"
  133. depends on PCMCIA
  134. help
  135. Support for Compact Flash cards, outboard IDE disks, tape drives,
  136. and CD-ROM drives connected through a PCMCIA card.
  137. config BLK_DEV_DELKIN
  138. tristate "Cardbus IDE support (Delkin/ASKA/Workbit)"
  139. depends on CARDBUS && PCI
  140. help
  141. Support for Delkin, ASKA, and Workbit Cardbus CompactFlash
  142. Adapters. This may also work for similar SD and XD adapters.
  143. config BLK_DEV_IDECD
  144. tristate "Include IDE/ATAPI CDROM support"
  145. ---help---
  146. If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
  147. a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
  148. SCSI protocol. Most new CD-ROM drives use ATAPI, including the
  149. NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
  150. double(2X) or better speed drives.
  151. If you say Y here, the CD-ROM drive will be identified at boot time
  152. along with other IDE devices, as "hdb" or "hdc", or something
  153. similar (check the boot messages with dmesg). If this is your only
  154. CD-ROM drive, you can say N to all other CD-ROM options, but be sure
  155. to say Y or M to "ISO 9660 CD-ROM file system support".
  156. Note that older versions of LILO (LInux LOader) cannot properly deal
  157. with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
  158. <http://lilo.go.dyndns.org/>.
  159. To compile this driver as a module, choose M here: the
  160. module will be called ide-cd.
  161. config BLK_DEV_IDETAPE
  162. tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
  163. depends on EXPERIMENTAL
  164. help
  165. If you have an IDE tape drive using the ATAPI protocol, say Y.
  166. ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
  167. similar to the SCSI protocol. If you have an SCSI tape drive
  168. however, you can say N here.
  169. You should also say Y if you have an OnStream DI-30 tape drive; this
  170. will not work with the SCSI protocol, until there is support for the
  171. SC-30 and SC-50 versions.
  172. If you say Y here, the tape drive will be identified at boot time
  173. along with other IDE devices, as "hdb" or "hdc", or something
  174. similar, and will be mapped to a character device such as "ht0"
  175. (check the boot messages with dmesg). Be sure to consult the
  176. <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
  177. for usage information.
  178. To compile this driver as a module, choose M here: the
  179. module will be called ide-tape.
  180. config BLK_DEV_IDEFLOPPY
  181. tristate "Include IDE/ATAPI FLOPPY support"
  182. ---help---
  183. If you have an IDE floppy drive which uses the ATAPI protocol,
  184. answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
  185. drives, similar to the SCSI protocol.
  186. The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
  187. this driver. For information about jumper settings and the question
  188. of when a ZIP drive uses a partition table, see
  189. <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
  190. (ATAPI PD-CD/CDR drives are not supported by this driver; support
  191. for PD-CD/CDR drives is available if you answer Y to
  192. "SCSI emulation support", below).
  193. If you say Y here, the FLOPPY drive will be identified along with
  194. other IDE devices, as "hdb" or "hdc", or something similar (check
  195. the boot messages with dmesg).
  196. To compile this driver as a module, choose M here: the
  197. module will be called ide-floppy.
  198. config BLK_DEV_IDESCSI
  199. tristate "SCSI emulation support"
  200. depends on SCSI
  201. ---help---
  202. WARNING: ide-scsi is no longer needed for cd writing applications!
  203. The 2.6 kernel supports direct writing to ide-cd, which eliminates
  204. the need for ide-scsi + the entire scsi stack just for writing a
  205. cd. The new method is more efficient in every way.
  206. This will provide SCSI host adapter emulation for IDE ATAPI devices,
  207. and will allow you to use a SCSI device driver instead of a native
  208. ATAPI driver.
  209. This is useful if you have an ATAPI device for which no native
  210. driver has been written (for example, an ATAPI PD-CD drive);
  211. you can then use this emulation together with an appropriate SCSI
  212. device driver. In order to do this, say Y here and to "SCSI support"
  213. and "SCSI generic support", below. You must then provide the kernel
  214. command line "hdx=ide-scsi" (try "man bootparam" or see the
  215. documentation of your boot loader (lilo or loadlin) about how to
  216. pass options to the kernel at boot time) for devices if you want the
  217. native EIDE sub-drivers to skip over the native support, so that
  218. this SCSI emulation can be used instead.
  219. Note that this option does NOT allow you to attach SCSI devices to a
  220. box that doesn't have a SCSI host adapter installed.
  221. If both this SCSI emulation and native ATAPI support are compiled
  222. into the kernel, the native support will be used.
  223. config BLK_DEV_IDEACPI
  224. bool "IDE ACPI support"
  225. depends on ACPI
  226. ---help---
  227. Implement ACPI support for generic IDE devices. On modern
  228. machines ACPI support is required to properly handle ACPI S3 states.
  229. config IDE_TASK_IOCTL
  230. bool "IDE Taskfile Access"
  231. help
  232. This is a direct raw access to the media. It is a complex but
  233. elegant solution to test and validate the domain of the hardware and
  234. perform below the driver data recovery if needed. This is the most
  235. basic form of media-forensics.
  236. If you are unsure, say N here.
  237. comment "IDE chipset support/bugfixes"
  238. config IDE_GENERIC
  239. tristate "generic/default IDE chipset support"
  240. default y
  241. help
  242. If unsure, say Y.
  243. config BLK_DEV_CMD640
  244. bool "CMD640 chipset bugfix/support"
  245. depends on X86
  246. ---help---
  247. The CMD-Technologies CMD640 IDE chip is used on many common 486 and
  248. Pentium motherboards, usually in combination with a "Neptune" or
  249. "SiS" chipset. Unfortunately, it has a number of rather nasty
  250. design flaws that can cause severe data corruption under many common
  251. conditions. Say Y here to include code which tries to automatically
  252. detect and correct the problems under Linux. This option also
  253. enables access to the secondary IDE ports in some CMD640 based
  254. systems.
  255. This driver will work automatically in PCI based systems (most new
  256. systems have PCI slots). But if your system uses VESA local bus
  257. (VLB) instead of PCI, you must also supply a kernel boot parameter
  258. to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
  259. bootparam" or see the documentation of your boot loader about how to
  260. pass options to the kernel.)
  261. The CMD640 chip is also used on add-in cards by Acculogic, and on
  262. the "CSA-6400E PCI to IDE controller" that some people have. For
  263. details, read <file:Documentation/ide.txt>.
  264. config BLK_DEV_CMD640_ENHANCED
  265. bool "CMD640 enhanced support"
  266. depends on BLK_DEV_CMD640
  267. help
  268. This option includes support for setting/autotuning PIO modes and
  269. prefetch on CMD640 IDE interfaces. For details, read
  270. <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
  271. and your BIOS does not already do this for you, then say Y here.
  272. Otherwise say N.
  273. config BLK_DEV_IDEPNP
  274. bool "PNP EIDE support"
  275. depends on PNP
  276. help
  277. If you have a PnP (Plug and Play) compatible EIDE card and
  278. would like the kernel to automatically detect and activate
  279. it, say Y here.
  280. config BLK_DEV_IDEPCI
  281. bool "PCI IDE chipset support" if PCI
  282. default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
  283. help
  284. Say Y here for PCI systems which use IDE drive(s).
  285. This option helps the IDE driver to automatically detect and
  286. configure all PCI-based IDE interfaces in your system.
  287. config IDEPCI_SHARE_IRQ
  288. bool "Sharing PCI IDE interrupts support"
  289. depends on PCI && BLK_DEV_IDEPCI
  290. help
  291. Some ATA/IDE chipsets have hardware support which allows for
  292. sharing a single IRQ with other cards. To enable support for
  293. this in the ATA/IDE driver, say Y here.
  294. It is safe to say Y to this question, in most cases.
  295. If unsure, say N.
  296. config BLK_DEV_OFFBOARD
  297. bool "Boot off-board chipsets first support"
  298. depends on PCI && BLK_DEV_IDEPCI
  299. help
  300. Normally, IDE controllers built into the motherboard (on-board
  301. controllers) are assigned to ide0 and ide1 while those on add-in PCI
  302. cards (off-board controllers) are relegated to ide2 and ide3.
  303. Answering Y here will allow you to reverse the situation, with
  304. off-board controllers on ide0/1 and on-board controllers on ide2/3.
  305. This can improve the usability of some boot managers such as lilo
  306. when booting from a drive on an off-board controller.
  307. If you say Y here, and you actually want to reverse the device scan
  308. order as explained above, you also need to issue the kernel command
  309. line option "ide=reverse". (Try "man bootparam" or see the
  310. documentation of your boot loader (lilo or loadlin) about how to
  311. pass options to the kernel at boot time.)
  312. Note that, if you do this, the order of the hd* devices will be
  313. rearranged which may require modification of fstab and other files.
  314. If in doubt, say N.
  315. config BLK_DEV_GENERIC
  316. tristate "Generic PCI IDE Chipset Support"
  317. depends on BLK_DEV_IDEPCI
  318. help
  319. This option provides generic support for various PCI IDE Chipsets
  320. which otherwise might not be supported.
  321. config BLK_DEV_OPTI621
  322. tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
  323. depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
  324. help
  325. This is a driver for the OPTi 82C621 EIDE controller.
  326. Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
  327. config BLK_DEV_RZ1000
  328. tristate "RZ1000 chipset bugfix/support"
  329. depends on PCI && BLK_DEV_IDEPCI && X86
  330. help
  331. The PC-Technologies RZ1000 IDE chip is used on many common 486 and
  332. Pentium motherboards, usually along with the "Neptune" chipset.
  333. Unfortunately, it has a rather nasty design flaw that can cause
  334. severe data corruption under many conditions. Say Y here to include
  335. code which automatically detects and corrects the problem under
  336. Linux. This may slow disk throughput by a few percent, but at least
  337. things will operate 100% reliably.
  338. config BLK_DEV_IDEDMA_PCI
  339. bool "Generic PCI bus-master DMA support"
  340. depends on PCI && BLK_DEV_IDEPCI
  341. ---help---
  342. If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
  343. is capable of bus-master DMA operation (most Pentium PCI systems),
  344. you will want to say Y here to reduce CPU overhead. You can then use
  345. the "hdparm" utility to enable DMA for drives for which it was not
  346. enabled automatically. By default, DMA is not enabled automatically
  347. for these drives, but you can change that by saying Y to the
  348. following question "Use DMA by default when available". You can get
  349. the latest version of the hdparm utility from
  350. <ftp://ibiblio.org/pub/Linux/system/hardware/>.
  351. Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
  352. and the file <file:Documentation/ide.txt> for more information.
  353. It is safe to say Y to this question.
  354. if BLK_DEV_IDEDMA_PCI
  355. config BLK_DEV_IDEDMA_FORCED
  356. bool "Force enable legacy 2.0.X HOSTS to use DMA"
  357. help
  358. This is an old piece of lost code from Linux 2.0 Kernels.
  359. Generally say N here.
  360. config IDEDMA_ONLYDISK
  361. bool "Enable DMA only for disks "
  362. help
  363. This is used if you know your ATAPI Devices are going to fail DMA
  364. Transfers.
  365. Generally say N here.
  366. config BLK_DEV_AEC62XX
  367. tristate "AEC62XX chipset support"
  368. help
  369. This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
  370. IDE controllers. This allows the kernel to change PIO, DMA and UDMA
  371. speeds and to configure the chip to optimum performance.
  372. config BLK_DEV_ALI15X3
  373. tristate "ALI M15x3 chipset support"
  374. help
  375. This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
  376. onboard chipsets. It also tests for Simplex mode and enables
  377. normal dual channel support.
  378. If you say Y here, you also need to say Y to "Use DMA by default
  379. when available", above. Please read the comments at the top of
  380. <file:drivers/ide/pci/alim15x3.c>.
  381. If unsure, say N.
  382. config WDC_ALI15X3
  383. bool "ALI M15x3 WDC support (DANGEROUS)"
  384. depends on BLK_DEV_ALI15X3
  385. ---help---
  386. This allows for UltraDMA support for WDC drives that ignore CRC
  387. checking. You are a fool for enabling this option, but there have
  388. been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
  389. YOU ENABLE THIS! No one will listen, just laugh for ignoring this
  390. SERIOUS WARNING.
  391. Using this option can allow WDC drives to run at ATA-4/5 transfer
  392. rates with only an ATA-2 support structure.
  393. SAY N!
  394. config BLK_DEV_AMD74XX
  395. tristate "AMD and nVidia IDE support"
  396. help
  397. This driver adds explicit support for AMD-7xx and AMD-8111 chips
  398. and also for the nVidia nForce chip. This allows the kernel to
  399. change PIO, DMA and UDMA speeds and to configure the chip to
  400. optimum performance.
  401. config BLK_DEV_ATIIXP
  402. tristate "ATI IXP chipset IDE support"
  403. depends on X86
  404. help
  405. This driver adds explicit support for ATI IXP chipset.
  406. This allows the kernel to change PIO, DMA and UDMA speeds
  407. and to configure the chip to optimum performance.
  408. Say Y here if you have an ATI IXP chipset IDE controller.
  409. config BLK_DEV_CMD64X
  410. tristate "CMD64{3|6|8|9} chipset support"
  411. help
  412. Say Y here if you have an IDE controller which uses any of these
  413. chipsets: CMD643, CMD646, or CMD648.
  414. config BLK_DEV_TRIFLEX
  415. tristate "Compaq Triflex IDE support"
  416. help
  417. Say Y here if you have a Compaq Triflex IDE controller, such
  418. as those commonly found on Compaq Pentium-Pro systems
  419. config BLK_DEV_CY82C693
  420. tristate "CY82C693 chipset support"
  421. help
  422. This driver adds detection and support for the CY82C693 chipset
  423. used on Digital's PC-Alpha 164SX boards.
  424. If you say Y here, you need to say Y to "Use DMA by default
  425. when available" as well.
  426. config BLK_DEV_CS5520
  427. tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
  428. depends on EXPERIMENTAL
  429. help
  430. Include support for PIO tuning and virtual DMA on the Cyrix MediaGX
  431. 5510/5520 chipset. This will automatically be detected and
  432. configured if found.
  433. It is safe to say Y to this question.
  434. config BLK_DEV_CS5530
  435. tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
  436. help
  437. Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
  438. will automatically be detected and configured if found.
  439. It is safe to say Y to this question.
  440. config BLK_DEV_CS5535
  441. tristate "AMD CS5535 chipset support"
  442. depends on X86 && !X86_64
  443. help
  444. Include support for UDMA on the NSC/AMD CS5535 companion chipset.
  445. This will automatically be detected and configured if found.
  446. It is safe to say Y to this question.
  447. config BLK_DEV_HPT34X
  448. tristate "HPT34X chipset support"
  449. help
  450. This driver adds up to 4 more EIDE devices sharing a single
  451. interrupt. The HPT343 chipset in its current form is a non-bootable
  452. controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
  453. PCI UDMA controllers. This driver requires dynamic tuning of the
  454. chipset during the ide-probe at boot time. It is reported to support
  455. DVD II drives, by the manufacturer.
  456. config HPT34X_AUTODMA
  457. bool "HPT34X AUTODMA support (EXPERIMENTAL)"
  458. depends on BLK_DEV_HPT34X && EXPERIMENTAL
  459. help
  460. This is a dangerous thing to attempt currently! Please read the
  461. comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
  462. here, then say Y to "Use DMA by default when available" as well.
  463. If unsure, say N.
  464. config BLK_DEV_HPT366
  465. tristate "HPT36X/37X chipset support"
  466. ---help---
  467. HPT366 is an Ultra DMA chipset for ATA-66.
  468. HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
  469. HPT370 is an Ultra DMA chipset for ATA-100.
  470. HPT372 is an Ultra DMA chipset for ATA-100.
  471. HPT374 is an Ultra DMA chipset for ATA-100.
  472. This driver adds up to 4 more EIDE devices sharing a single
  473. interrupt.
  474. The HPT366 chipset in its current form is bootable. One solution
  475. for this problem are special LILO commands for redirecting the
  476. reference to device 0x80. The other solution is to say Y to "Boot
  477. off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
  478. your mother board has the chipset natively mounted. Regardless one
  479. should use the fore mentioned option and call at LILO or include
  480. "ide=reverse" in LILO's append-line.
  481. This driver requires dynamic tuning of the chipset during the
  482. ide-probe at boot. It is reported to support DVD II drives, by the
  483. manufacturer.
  484. config BLK_DEV_JMICRON
  485. tristate "JMicron JMB36x support"
  486. help
  487. Basic support for the JMicron ATA controllers. For full support
  488. use the libata drivers.
  489. config BLK_DEV_SC1200
  490. tristate "National SCx200 chipset support"
  491. help
  492. This driver adds support for the built in IDE on the National
  493. SCx200 series of embedded x86 "Geode" systems
  494. config BLK_DEV_PIIX
  495. tristate "Intel PIIXn chipsets support"
  496. help
  497. This driver adds explicit support for Intel PIIX and ICH chips
  498. and also for the Efar Victory66 (slc90e66) chip. This allows
  499. the kernel to change PIO, DMA and UDMA speeds and to configure
  500. the chip to optimum performance.
  501. config BLK_DEV_IT8213
  502. tristate "IT8213 IDE support"
  503. help
  504. This driver adds support for the ITE 8213 IDE controller.
  505. config BLK_DEV_IT821X
  506. tristate "IT821X IDE support"
  507. help
  508. This driver adds support for the ITE 8211 IDE controller and the
  509. IT 8212 IDE RAID controller in both RAID and pass-through mode.
  510. config BLK_DEV_NS87415
  511. tristate "NS87415 chipset support"
  512. help
  513. This driver adds detection and support for the NS87415 chip
  514. (used mainly on SPARC64 and PA-RISC machines).
  515. Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
  516. config BLK_DEV_PDC202XX_OLD
  517. tristate "PROMISE PDC202{46|62|65|67} support"
  518. help
  519. Promise Ultra33 or PDC20246
  520. Promise Ultra66 or PDC20262
  521. Promise Ultra100 or PDC20265/PDC20267/PDC20268
  522. This driver adds up to 4 more EIDE devices sharing a single
  523. interrupt. This add-on card is a bootable PCI UDMA controller. Since
  524. multiple cards can be installed and there are BIOS ROM problems that
  525. happen if the BIOS revisions of all installed cards (three-max) do
  526. not match, the driver attempts to do dynamic tuning of the chipset
  527. at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
  528. for more than one card. This card may require that you say Y to
  529. "Special UDMA Feature".
  530. If you say Y here, you need to say Y to "Use DMA by default when
  531. available" as well.
  532. Please read the comments at the top of
  533. <file:drivers/ide/pci/pdc202xx_old.c>.
  534. If unsure, say N.
  535. config PDC202XX_BURST
  536. bool "Special UDMA Feature"
  537. depends on BLK_DEV_PDC202XX_OLD
  538. help
  539. This option causes the pdc202xx driver to enable UDMA modes on the
  540. PDC202xx even when the PDC202xx BIOS has not done so.
  541. It was originally designed for the PDC20246/Ultra33, whose BIOS will
  542. only setup UDMA on the first two PDC20246 cards. It has also been
  543. used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
  544. when the PDC20265 BIOS has been disabled (for faster boot up).
  545. Please read the comments at the top of
  546. <file:drivers/ide/pci/pdc202xx_old.c>.
  547. If unsure, say N.
  548. config BLK_DEV_PDC202XX_NEW
  549. tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
  550. config BLK_DEV_SVWKS
  551. tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
  552. help
  553. This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
  554. chipsets.
  555. config BLK_DEV_SGIIOC4
  556. tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support"
  557. depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4
  558. select IDEPCI_SHARE_IRQ
  559. help
  560. This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
  561. chipset, which has one channel and can support two devices.
  562. Please say Y here if you have an Altix System from SGI.
  563. config BLK_DEV_SIIMAGE
  564. tristate "Silicon Image chipset support"
  565. help
  566. This driver adds PIO/(U)DMA support for the SI CMD680 and SII
  567. 3112 (Serial ATA) chips.
  568. config BLK_DEV_SIS5513
  569. tristate "SiS5513 chipset support"
  570. depends on X86
  571. ---help---
  572. This driver ensures (U)DMA support for SIS5513 chipset family based
  573. mainboards.
  574. The following chipsets are supported:
  575. ATA16: SiS5511, SiS5513
  576. ATA33: SiS5591, SiS5597, SiS5598, SiS5600
  577. ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
  578. ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
  579. SiS745, SiS750
  580. If you say Y here, you need to say Y to "Use DMA by default when
  581. available" as well.
  582. Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
  583. config BLK_DEV_SL82C105
  584. tristate "Winbond SL82c105 support"
  585. depends on (PPC || ARM)
  586. help
  587. If you have a Winbond SL82c105 IDE controller, say Y here to enable
  588. special configuration for this chip. This is common on various CHRP
  589. motherboards, but could be used elsewhere. If in doubt, say Y.
  590. config BLK_DEV_SLC90E66
  591. tristate "SLC90E66 chipset support"
  592. help
  593. This driver ensures (U)DMA support for Victory66 SouthBridges for
  594. SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
  595. The nice thing about it is that you can mix Ultra/DMA/PIO devices
  596. and it will handle timing cycles. Since this is an improved
  597. look-a-like to the PIIX4 it should be a nice addition.
  598. If you say Y here, you need to say Y to "Use DMA by default when
  599. available" as well.
  600. Please read the comments at the top of
  601. <file:drivers/ide/pci/slc90e66.c>.
  602. config BLK_DEV_TRM290
  603. tristate "Tekram TRM290 chipset support"
  604. help
  605. This driver adds support for bus master DMA transfers
  606. using the Tekram TRM290 PCI IDE chip. Volunteers are
  607. needed for further tweaking and development.
  608. Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
  609. config BLK_DEV_VIA82CXXX
  610. tristate "VIA82CXXX chipset support"
  611. help
  612. This driver adds explicit support for VIA BusMastering IDE chips.
  613. This allows the kernel to change PIO, DMA and UDMA speeds and to
  614. configure the chip to optimum performance.
  615. config BLK_DEV_TC86C001
  616. tristate "Toshiba TC86C001 support"
  617. help
  618. This driver adds support for Toshiba TC86C001 GOKU-S chip.
  619. config BLK_DEV_CELLEB
  620. tristate "Toshiba's Cell Reference Set IDE support"
  621. depends on PPC_CELLEB
  622. help
  623. This driver provides support for the built-in IDE controller on
  624. Toshiba Cell Reference Board.
  625. If unsure, say Y.
  626. endif
  627. config BLK_DEV_IDE_PMAC
  628. bool "Builtin PowerMac IDE support"
  629. depends on PPC_PMAC && IDE=y
  630. help
  631. This driver provides support for the built-in IDE controller on
  632. most of the recent Apple Power Macintoshes and PowerBooks.
  633. If unsure, say Y.
  634. config BLK_DEV_IDE_PMAC_ATA100FIRST
  635. bool "Probe internal ATA/100 (Kauai) first"
  636. depends on BLK_DEV_IDE_PMAC
  637. help
  638. This option will cause the ATA/100 controller found in UniNorth2
  639. based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
  640. to be probed before the ATA/66 and ATA/33 controllers. Without
  641. these, those machine used to have the hard disk on hdc and the
  642. CD-ROM on hda. This option changes this to more natural hda for
  643. hard disk and hdc for CD-ROM.
  644. config BLK_DEV_IDEDMA_PMAC
  645. bool "PowerMac IDE DMA support"
  646. depends on BLK_DEV_IDE_PMAC
  647. select BLK_DEV_IDEDMA_PCI
  648. help
  649. This option allows the driver for the built-in IDE controller on
  650. Power Macintoshes and PowerBooks to use DMA (direct memory access)
  651. to transfer data to and from memory. Saying Y is safe and improves
  652. performance.
  653. config BLK_DEV_IDE_SWARM
  654. tristate "IDE for Sibyte evaluation boards"
  655. depends on SIBYTE_SB1xxx_SOC
  656. config BLK_DEV_IDE_AU1XXX
  657. bool "IDE for AMD Alchemy Au1200"
  658. depends on SOC_AU1200
  659. choice
  660. prompt "IDE Mode for AMD Alchemy Au1200"
  661. default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA
  662. depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
  663. config BLK_DEV_IDE_AU1XXX_PIO_DBDMA
  664. bool "PIO+DbDMA IDE for AMD Alchemy Au1200"
  665. config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
  666. bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200"
  667. depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
  668. endchoice
  669. config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ
  670. int "Maximum transfer size (KB) per request (up to 128)"
  671. default "128"
  672. depends on BLK_DEV_IDE_AU1XXX
  673. config IDE_ARM
  674. def_bool ARM && (ARCH_A5K || ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
  675. config BLK_DEV_IDE_ICSIDE
  676. tristate "ICS IDE interface support"
  677. depends on ARM && ARCH_ACORN
  678. help
  679. On Acorn systems, say Y here if you wish to use the ICS IDE
  680. interface card. This is not required for ICS partition support.
  681. If you are unsure, say N to this.
  682. config BLK_DEV_IDEDMA_ICS
  683. bool "ICS DMA support"
  684. depends on BLK_DEV_IDE_ICSIDE
  685. help
  686. Say Y here if you want to add DMA (Direct Memory Access) support to
  687. the ICS IDE driver.
  688. config BLK_DEV_IDE_RAPIDE
  689. tristate "RapIDE interface support"
  690. depends on ARM && ARCH_ACORN
  691. help
  692. Say Y here if you want to support the Yellowstone RapIDE controller
  693. manufactured for use with Acorn computers.
  694. config BLK_DEV_IDE_BAST
  695. tristate "Simtec BAST / Thorcom VR1000 IDE support"
  696. depends on ARM && (ARCH_BAST || MACH_VR1000)
  697. help
  698. Say Y here if you want to support the onboard IDE channels on the
  699. Simtec BAST or the Thorcom VR1000
  700. config BLK_DEV_GAYLE
  701. bool "Amiga Gayle IDE interface support"
  702. depends on AMIGA
  703. help
  704. This is the IDE driver for the Amiga Gayle IDE interface. It supports
  705. both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
  706. This includes builtin IDE interfaces on some Amiga models (A600,
  707. A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
  708. bus (M-Tech E-Matrix 530 expansion card).
  709. Say Y if you have an Amiga with a Gayle IDE interface and want to use
  710. IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
  711. it.
  712. Note that you also have to enable Zorro bus support if you want to
  713. use Gayle IDE interfaces on the Zorro expansion bus.
  714. config BLK_DEV_IDEDOUBLER
  715. bool "Amiga IDE Doubler support (EXPERIMENTAL)"
  716. depends on BLK_DEV_GAYLE && EXPERIMENTAL
  717. ---help---
  718. This driver provides support for the so-called `IDE doublers' (made
  719. by various manufacturers, e.g. Eyetech) that can be connected to the
  720. builtin IDE interface of some Amiga models. Using such an IDE
  721. doubler, you can connect up to four instead of two IDE devices on
  722. the Amiga's builtin IDE interface.
  723. Note that the normal Amiga Gayle IDE driver may not work correctly
  724. if you have an IDE doubler and don't enable this driver!
  725. Say Y if you have an IDE doubler. The driver is enabled at kernel
  726. runtime using the "ide=doubler" kernel boot parameter.
  727. config BLK_DEV_BUDDHA
  728. bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
  729. depends on ZORRO && EXPERIMENTAL
  730. help
  731. This is the IDE driver for the IDE interfaces on the Buddha,
  732. Catweasel and X-Surf expansion boards. It supports up to two interfaces
  733. on the Buddha, three on the Catweasel and two on the X-Surf.
  734. Say Y if you have a Buddha or Catweasel expansion board and want to
  735. use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
  736. to one of its IDE interfaces.
  737. config BLK_DEV_FALCON_IDE
  738. bool "Falcon IDE interface support"
  739. depends on ATARI
  740. help
  741. This is the IDE driver for the builtin IDE interface on the Atari
  742. Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
  743. disks, CD-ROM drives, etc.) that are connected to the builtin IDE
  744. interface.
  745. config BLK_DEV_MAC_IDE
  746. bool "Macintosh Quadra/Powerbook IDE interface support"
  747. depends on MAC
  748. help
  749. This is the IDE driver for the builtin IDE interface on some m68k
  750. Macintosh models. It supports both the `Quadra style' (used in
  751. Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
  752. (used in the Powerbook 150 and 190 models) IDE interface.
  753. Say Y if you have such an Macintosh model and want to use IDE
  754. devices (hard disks, CD-ROM drives, etc.) that are connected to the
  755. builtin IDE interface.
  756. config BLK_DEV_Q40IDE
  757. bool "Q40/Q60 IDE interface support"
  758. depends on Q40
  759. help
  760. Enable the on-board IDE controller in the Q40/Q60. This should
  761. normally be on; disable it only if you are running a custom hard
  762. drive subsystem through an expansion card.
  763. config BLK_DEV_MPC8xx_IDE
  764. bool "MPC8xx IDE support"
  765. depends on 8xx && IDE=y && BLK_DEV_IDE=y
  766. help
  767. This option provides support for IDE on Motorola MPC8xx Systems.
  768. Please see 'Type of MPC8xx IDE interface' for details.
  769. If unsure, say N.
  770. choice
  771. prompt "Type of MPC8xx IDE interface"
  772. depends on BLK_DEV_MPC8xx_IDE
  773. default IDE_8xx_PCCARD
  774. config IDE_8xx_PCCARD
  775. bool "8xx_PCCARD"
  776. ---help---
  777. Select how the IDE devices are connected to the MPC8xx system:
  778. 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
  779. with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
  780. ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
  781. systems)
  782. 8xx_DIRECT is used for directly connected IDE devices using the 8xx
  783. internal PCMCIA interface (example: IVMS8 systems)
  784. EXT_DIRECT is used for IDE devices directly connected to the 8xx
  785. bus using some glue logic, but _not_ the 8xx internal
  786. PCMCIA interface (example: IDIF860 systems)
  787. config IDE_8xx_DIRECT
  788. bool "8xx_DIRECT"
  789. config IDE_EXT_DIRECT
  790. bool "EXT_DIRECT"
  791. endchoice
  792. # no isa -> no vlb
  793. config IDE_CHIPSETS
  794. bool "Other IDE chipset support"
  795. depends on ISA
  796. ---help---
  797. Say Y here if you want to include enhanced support for various IDE
  798. interface chipsets used on motherboards and add-on cards. You can
  799. then pick your particular IDE chip from among the following options.
  800. This enhanced support may be necessary for Linux to be able to
  801. access the 3rd/4th drives in some systems. It may also enable
  802. setting of higher speed I/O rates to improve system performance with
  803. these chipsets. Most of these also require special kernel boot
  804. parameters to actually turn on the support at runtime; you can find
  805. a list of these in the file <file:Documentation/ide.txt>.
  806. People with SCSI-only systems can say N here.
  807. if IDE_CHIPSETS
  808. comment "Note: most of these also require special kernel boot parameters"
  809. config BLK_DEV_4DRIVES
  810. bool "Generic 4 drives/port support"
  811. help
  812. Certain older chipsets, including the Tekram 690CD, use a single set
  813. of I/O ports at 0x1f0 to control up to four drives, instead of the
  814. customary two drives per port. Support for this can be enabled at
  815. runtime using the "ide0=four" kernel boot parameter if you say Y
  816. here.
  817. config BLK_DEV_ALI14XX
  818. tristate "ALI M14xx support"
  819. help
  820. This driver is enabled at runtime using the "ali14xx.probe" kernel
  821. boot parameter. It enables support for the secondary IDE interface
  822. of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
  823. I/O speeds to be set as well. See the files
  824. <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
  825. more info.
  826. config BLK_DEV_DTC2278
  827. tristate "DTC-2278 support"
  828. help
  829. This driver is enabled at runtime using the "dtc2278.probe" kernel
  830. boot parameter. It enables support for the secondary IDE interface
  831. of the DTC-2278 card, and permits faster I/O speeds to be set as
  832. well. See the <file:Documentation/ide.txt> and
  833. <file:drivers/ide/legacy/dtc2278.c> files for more info.
  834. config BLK_DEV_HT6560B
  835. tristate "Holtek HT6560B support"
  836. help
  837. This driver is enabled at runtime using the "ht6560b.probe" kernel
  838. boot parameter. It enables support for the secondary IDE interface
  839. of the Holtek card, and permits faster I/O speeds to be set as well.
  840. See the <file:Documentation/ide.txt> and
  841. <file:drivers/ide/legacy/ht6560b.c> files for more info.
  842. config BLK_DEV_QD65XX
  843. tristate "QDI QD65xx support"
  844. help
  845. This driver is enabled at runtime using the "qd65xx.probe" kernel
  846. boot parameter. It permits faster I/O speeds to be set. See the
  847. <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
  848. more info.
  849. config BLK_DEV_UMC8672
  850. tristate "UMC-8672 support"
  851. help
  852. This driver is enabled at runtime using the "umc8672.probe" kernel
  853. boot parameter. It enables support for the secondary IDE interface
  854. of the UMC-8672, and permits faster I/O speeds to be set as well.
  855. See the files <file:Documentation/ide.txt> and
  856. <file:drivers/ide/legacy/umc8672.c> for more info.
  857. endif
  858. config BLK_DEV_IDEDMA
  859. def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
  860. config IDEDMA_IVB
  861. bool "IGNORE word93 Validation BITS"
  862. depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
  863. ---help---
  864. There are unclear terms in ATA-4 and ATA-5 standards how certain
  865. hardware (an 80c ribbon) should be detected. Different interpretations
  866. of the standards have been released in hardware. This causes problems:
  867. for example, a host with Ultra Mode 4 (or higher) will not run
  868. in that mode with an 80c ribbon.
  869. If you are experiencing compatibility or performance problems, you
  870. MAY try to answer Y here. However, it does not necessarily solve
  871. any of your problems, it could even cause more of them.
  872. It is normally safe to answer Y; however, the default is N.
  873. endif
  874. config BLK_DEV_HD_ONLY
  875. bool "Old hard disk (MFM/RLL/IDE) driver"
  876. depends on BLK_DEV_IDE=n
  877. help
  878. There are two drivers for MFM/RLL/IDE hard disks. Most people use
  879. the newer enhanced driver, but this old one is still around for two
  880. reasons. Some older systems have strange timing problems and seem to
  881. work only with the old driver (which itself does not work with some
  882. newer systems). The other reason is that the old driver is smaller,
  883. since it lacks the enhanced functionality of the new one. This makes
  884. it a good choice for systems with very tight memory restrictions, or
  885. for systems with only older MFM/RLL/ESDI drives. Choosing the old
  886. driver can save 13 KB or so of kernel memory.
  887. If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
  888. instead of this one. For more detailed information, read the
  889. Disk-HOWTO, available from
  890. <http://www.tldp.org/docs.html#howto>.
  891. config BLK_DEV_HD
  892. def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY
  893. endif
  894. endmenu
  895. endif