Kconfig 40 KB

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