Kconfig 35 KB

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