| blob | ef2199915c2a76dca15974e1640acb9058764709 |
1 #
2 # IDE ATA ATAPI Block device driver configuration
3 #
4 # Andre Hedrick <andre@linux-ide.org>
5 #
7 # Select HAVE_IDE if IDE is supported
8 config HAVE_IDE
9 def_bool n
11 menuconfig IDE
12 tristate "ATA/ATAPI/MFM/RLL support"
13 depends on HAVE_IDE
14 depends on BLOCK
15 ---help---
16 If you say Y here, your kernel will be able to manage low cost mass
17 storage units such as ATA/(E)IDE and ATAPI units. The most common
18 cases are IDE hard drives and ATAPI CD-ROM drives.
20 If your system is pure SCSI and doesn't use these interfaces, you
21 can say N here.
23 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
24 for mass storage units such as hard disks. It was designed by
25 Western Digital and Compaq Computer in 1984. It was then named
26 ST506. Quite a number of disks use the IDE interface.
28 AT Attachment (ATA) is the superset of the IDE specifications.
29 ST506 was also called ATA-1.
31 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
32 ATA-3. It provides support for larger disks (up to 8.4GB by means of
33 the LBA standard), more disks (4 instead of 2) and for other mass
34 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
35 ATA-4 and provides faster (and more CPU friendly) transfer modes
36 than previous PIO (Programmed processor Input/Output) from previous
37 ATA/IDE standards by means of fast DMA controllers.
39 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
40 CD-ROM drives, similar in many respects to the SCSI protocol.
42 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
43 designed in order to prevent data corruption and disk crash by
44 detecting pre hardware failure conditions (heat, access time, and
45 the like...). Disks built since June 1995 may follow this standard.
46 The kernel itself doesn't manage this; however there are quite a
47 number of user programs such as smart that can query the status of
48 SMART parameters from disk drives.
50 To compile this driver as a module, choose M here: the
51 module will be called ide.
53 <<<<<<< HEAD:drivers/ide/Kconfig
54 For further information, please read <file:Documentation/ide.txt>.
55 =======
56 For further information, please read <file:Documentation/ide/ide.txt>.
57 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
59 If unsure, say Y.
61 if IDE
63 config IDE_MAX_HWIFS
64 int "Max IDE interfaces"
65 depends on ALPHA || SUPERH || IA64 || EMBEDDED
66 range 1 10
67 default 4
68 help
69 This is the maximum number of IDE hardware interfaces that will
70 be supported by the driver. Make sure it is at least as high as
71 the number of IDE interfaces in your system.
73 config BLK_DEV_IDE
74 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
75 ---help---
76 If you say Y here, you will use the full-featured IDE driver to
77 control up to ten ATA/IDE interfaces, each being able to serve a
78 "master" and a "slave" device, for a total of up to twenty ATA/IDE
79 disk/cdrom/tape/floppy drives.
81 Useful information about large (>540 MB) IDE disks, multiple
82 interfaces, what to do if ATA/IDE devices are not automatically
83 detected, sound card ATA/IDE ports, module support, and other
84 <<<<<<< HEAD:drivers/ide/Kconfig
85 topics, is contained in <file:Documentation/ide.txt>. For detailed
86 =======
87 topics, is contained in <file:Documentation/ide/ide.txt>. For detailed
88 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
89 information about hard drives, consult the Disk-HOWTO and the
90 Multi-Disk-HOWTO, available from
91 <http://www.tldp.org/docs.html#howto>.
93 To fine-tune ATA/IDE drive/interface parameters for improved
94 performance, look for the hdparm package at
95 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
97 To compile this driver as a module, choose M here and read
98 <<<<<<< HEAD:drivers/ide/Kconfig
99 <file:Documentation/ide.txt>. The module will be called ide-mod.
100 =======
101 <file:Documentation/ide/ide.txt>. The module will be called ide-mod.
102 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
103 Do not compile this driver as a module if your root file system (the
104 one containing the directory /) is located on an IDE device.
106 If you have one or more IDE drives, say Y or M here. If your system
107 has no IDE drives, or if memory requirements are really tight, you
108 could say N here, and select the "Old hard disk driver" below
109 instead to save about 13 KB of memory in the kernel.
111 if BLK_DEV_IDE
113 <<<<<<< HEAD:drivers/ide/Kconfig
114 comment "Please see Documentation/ide.txt for help/info on IDE drives"
115 =======
116 comment "Please see Documentation/ide/ide.txt for help/info on IDE drives"
117 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
119 config BLK_DEV_IDE_SATA
120 bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
121 default n
122 ---help---
123 There are two drivers for Serial ATA controllers.
125 The main driver, "libata", uses the SCSI subsystem
126 and supports most modern SATA controllers. In order to use it
127 you may take a look at "Serial ATA (prod) and Parallel ATA
128 (experimental) drivers".
130 The IDE driver (which you are currently configuring) supports
131 a few first-generation SATA controllers.
133 In order to eliminate conflicts between the two subsystems,
134 this config option enables the IDE driver's SATA support.
135 Normally this is disabled, as it is preferred that libata
136 supports SATA controllers, and this (IDE) driver supports
137 PATA controllers.
139 If unsure, say N.
141 config BLK_DEV_HD_IDE
142 bool "Use old disk-only driver on primary interface"
143 depends on (X86 || SH_MPC1211)
144 ---help---
145 There are two drivers for MFM/RLL/IDE disks. Most people use just
146 the new enhanced driver by itself. This option however installs the
147 old hard disk driver to control the primary IDE/disk interface in
148 the system, leaving the new enhanced IDE driver to take care of only
149 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
150 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
151 IDE interface. Choosing this option may be useful for older systems
152 which have MFM/RLL/ESDI controller+drives at the primary port
153 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
154 addresses.
156 Normally, just say N here; you will then use the new driver for all
157 4 interfaces.
159 config BLK_DEV_IDEDISK
160 tristate "Include IDE/ATA-2 DISK support"
161 ---help---
162 This will include enhanced support for MFM/RLL/IDE hard disks. If
163 you have a MFM/RLL/IDE disk, and there is no special reason to use
164 the old hard disk driver instead, say Y. If you have an SCSI-only
165 system, you can say N here.
167 To compile this driver as a module, choose M here: the
168 module will be called ide-disk.
169 Do not compile this driver as a module if your root file system
170 (the one containing the directory /) is located on the IDE disk.
172 If unsure, say Y.
174 config IDEDISK_MULTI_MODE
175 bool "Use multiple sector mode for Programmed Input/Output by default"
176 help
177 This setting is irrelevant for most IDE disks, with direct memory
178 access, to which multiple sector mode does not apply. Multiple sector
179 mode is a feature of most modern IDE hard drives, permitting the
180 transfer of multiple sectors per Programmed Input/Output interrupt,
181 rather than the usual one sector per interrupt. When this feature is
182 enabled, it can reduce operating system overhead for disk Programmed
183 Input/Output. On some systems, it also can increase the data
184 throughput of Programmed Input/Output. Some drives, however, seemed
185 to run slower with multiple sector mode enabled. Some drives claimed
186 to support multiple sector mode, but lost data at some settings.
187 Under rare circumstances, such failures could result in massive
188 filesystem corruption.
190 If you get the following error, try to say Y here:
192 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
193 hda: set_multmode: error=0x04 { DriveStatusError }
195 If in doubt, say N.
197 config BLK_DEV_IDECS
198 tristate "PCMCIA IDE support"
199 depends on PCMCIA
200 help
201 Support for Compact Flash cards, outboard IDE disks, tape drives,
202 and CD-ROM drives connected through a PCMCIA card.
204 config BLK_DEV_DELKIN
205 tristate "Cardbus IDE support (Delkin/ASKA/Workbit)"
206 depends on CARDBUS && PCI
207 help
208 Support for Delkin, ASKA, and Workbit Cardbus CompactFlash
209 Adapters. This may also work for similar SD and XD adapters.
211 config BLK_DEV_IDECD
212 tristate "Include IDE/ATAPI CDROM support"
213 ---help---
214 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
215 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
216 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
217 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
218 double(2X) or better speed drives.
220 If you say Y here, the CD-ROM drive will be identified at boot time
221 along with other IDE devices, as "hdb" or "hdc", or something
222 similar (check the boot messages with dmesg). If this is your only
223 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
224 to say Y or M to "ISO 9660 CD-ROM file system support".
226 To compile this driver as a module, choose M here: the
227 module will be called ide-cd.
229 config BLK_DEV_IDECD_VERBOSE_ERRORS
230 bool "Verbose error logging for IDE/ATAPI CDROM driver" if EMBEDDED
231 depends on BLK_DEV_IDECD
232 default y
233 help
234 Turn this on to have the driver print out the meanings of the
235 ATAPI error codes. This will use up additional 8kB of kernel-space
236 memory, though.
238 config BLK_DEV_IDETAPE
239 tristate "Include IDE/ATAPI TAPE support"
240 help
241 If you have an IDE tape drive using the ATAPI protocol, say Y.
242 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
243 similar to the SCSI protocol. If you have an SCSI tape drive
244 however, you can say N here.
246 You should also say Y if you have an OnStream DI-30 tape drive; this
247 will not work with the SCSI protocol, until there is support for the
248 SC-30 and SC-50 versions.
250 If you say Y here, the tape drive will be identified at boot time
251 along with other IDE devices, as "hdb" or "hdc", or something
252 similar, and will be mapped to a character device such as "ht0"
253 (check the boot messages with dmesg). Be sure to consult the
254 <<<<<<< HEAD:drivers/ide/Kconfig
255 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
256 for usage information.
257 =======
258 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide/ide.txt>
259 files for usage information.
260 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
262 To compile this driver as a module, choose M here: the
263 module will be called ide-tape.
265 config BLK_DEV_IDEFLOPPY
266 tristate "Include IDE/ATAPI FLOPPY support"
267 ---help---
268 If you have an IDE floppy drive which uses the ATAPI protocol,
269 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
270 drives, similar to the SCSI protocol.
272 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
273 this driver. For information about jumper settings and the question
274 of when a ZIP drive uses a partition table, see
275 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
276 (ATAPI PD-CD/CDR drives are not supported by this driver; support
277 for PD-CD/CDR drives is available if you answer Y to
278 "SCSI emulation support", below).
280 If you say Y here, the FLOPPY drive will be identified along with
281 other IDE devices, as "hdb" or "hdc", or something similar (check
282 the boot messages with dmesg).
284 To compile this driver as a module, choose M here: the
285 module will be called ide-floppy.
287 config BLK_DEV_IDESCSI
288 tristate "SCSI emulation support"
289 depends on SCSI
290 ---help---
291 WARNING: ide-scsi is no longer needed for cd writing applications!
292 The 2.6 kernel supports direct writing to ide-cd, which eliminates
293 the need for ide-scsi + the entire scsi stack just for writing a
294 cd. The new method is more efficient in every way.
296 This will provide SCSI host adapter emulation for IDE ATAPI devices,
297 and will allow you to use a SCSI device driver instead of a native
298 ATAPI driver.
300 This is useful if you have an ATAPI device for which no native
301 driver has been written (for example, an ATAPI PD-CD drive);
302 you can then use this emulation together with an appropriate SCSI
303 device driver. In order to do this, say Y here and to "SCSI support"
304 and "SCSI generic support", below. You must then provide the kernel
305 command line "hdx=ide-scsi" (try "man bootparam" or see the
306 documentation of your boot loader (lilo or loadlin) about how to
307 pass options to the kernel at boot time) for devices if you want the
308 native EIDE sub-drivers to skip over the native support, so that
309 this SCSI emulation can be used instead.
311 Note that this option does NOT allow you to attach SCSI devices to a
312 box that doesn't have a SCSI host adapter installed.
314 If both this SCSI emulation and native ATAPI support are compiled
315 into the kernel, the native support will be used.
317 config BLK_DEV_IDEACPI
318 bool "IDE ACPI support"
319 depends on ACPI
320 ---help---
321 Implement ACPI support for generic IDE devices. On modern
322 machines ACPI support is required to properly handle ACPI S3 states.
324 config IDE_TASK_IOCTL
325 bool "IDE Taskfile Access"
326 help
327 This is a direct raw access to the media. It is a complex but
328 elegant solution to test and validate the domain of the hardware and
329 perform below the driver data recovery if needed. This is the most
330 basic form of media-forensics.
332 If you are unsure, say N here.
334 config IDE_PROC_FS
335 bool "legacy /proc/ide/ support"
336 depends on IDE && PROC_FS
337 default y
338 help
339 This option enables support for the various files in
340 /proc/ide. In Linux 2.6 this has been superseded by
341 files in sysfs but many legacy applications rely on this.
343 If unsure say Y.
345 comment "IDE chipset support/bugfixes"
347 config IDE_GENERIC
348 tristate "generic/default IDE chipset support"
349 help
350 If unsure, say N.
352 config BLK_DEV_PLATFORM
353 tristate "Platform driver for IDE interfaces"
354 help
355 This is the platform IDE driver, used mostly for Memory Mapped
356 IDE devices, like Compact Flashes running in True IDE mode.
358 If unsure, say N.
360 config BLK_DEV_CMD640
361 tristate "CMD640 chipset bugfix/support"
362 depends on X86
363 ---help---
364 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
365 Pentium motherboards, usually in combination with a "Neptune" or
366 "SiS" chipset. Unfortunately, it has a number of rather nasty
367 design flaws that can cause severe data corruption under many common
368 conditions. Say Y here to include code which tries to automatically
369 detect and correct the problems under Linux. This option also
370 enables access to the secondary IDE ports in some CMD640 based
371 systems.
373 This driver will work automatically in PCI based systems (most new
374 systems have PCI slots). But if your system uses VESA local bus
375 (VLB) instead of PCI, you must also supply a kernel boot parameter
376 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
377 bootparam" or see the documentation of your boot loader about how to
378 pass options to the kernel.)
380 The CMD640 chip is also used on add-in cards by Acculogic, and on
381 the "CSA-6400E PCI to IDE controller" that some people have. For
382 <<<<<<< HEAD:drivers/ide/Kconfig
383 details, read <file:Documentation/ide.txt>.
384 =======
385 details, read <file:Documentation/ide/ide.txt>.
386 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
388 config BLK_DEV_CMD640_ENHANCED
389 bool "CMD640 enhanced support"
390 depends on BLK_DEV_CMD640
391 help
392 This option includes support for setting/autotuning PIO modes and
393 prefetch on CMD640 IDE interfaces. For details, read
394 <<<<<<< HEAD:drivers/ide/Kconfig
395 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
396 =======
397 <file:Documentation/ide/ide.txt>. If you have a CMD640 IDE interface
398 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
399 and your BIOS does not already do this for you, then say Y here.
400 Otherwise say N.
402 config BLK_DEV_IDEPNP
403 tristate "PNP EIDE support"
404 depends on PNP
405 help
406 If you have a PnP (Plug and Play) compatible EIDE card and
407 would like the kernel to automatically detect and activate
408 it, say Y here.
410 config BLK_DEV_IDEDMA_SFF
411 bool
413 if PCI
415 comment "PCI IDE chipsets support"
417 config BLK_DEV_IDEPCI
418 bool
420 config IDEPCI_PCIBUS_ORDER
421 bool "Probe IDE PCI devices in the PCI bus order (DEPRECATED)"
422 depends on BLK_DEV_IDE=y && BLK_DEV_IDEPCI
423 default y
424 help
425 Probe IDE PCI devices in the order in which they appear on the
426 PCI bus (i.e. 00:1f.1 PCI device before 02:01.0 PCI device)
427 instead of the order in which IDE PCI host drivers are loaded.
429 Please note that this method of assuring stable naming of
430 IDE devices is unreliable and use other means for achieving
431 it (i.e. udev).
433 If in doubt, say N.
435 # TODO: split it on per host driver config options (or module parameters)
436 config BLK_DEV_OFFBOARD
437 bool "Boot off-board chipsets first support (DEPRECATED)"
438 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)
439 help
440 Normally, IDE controllers built into the motherboard (on-board
441 controllers) are assigned to ide0 and ide1 while those on add-in PCI
442 cards (off-board controllers) are relegated to ide2 and ide3.
443 Answering Y here will allow you to reverse the situation, with
444 off-board controllers on ide0/1 and on-board controllers on ide2/3.
445 This can improve the usability of some boot managers such as lilo
446 when booting from a drive on an off-board controller.
448 If you say Y here, and you actually want to reverse the device scan
449 order as explained above, you also need to issue the kernel command
450 line option "ide=reverse". (Try "man bootparam" or see the
451 documentation of your boot loader (lilo or loadlin) about how to
452 pass options to the kernel at boot time.)
454 Note that, if you do this, the order of the hd* devices will be
455 rearranged which may require modification of fstab and other files.
457 Please also note that this method of assuring stable naming of
458 IDE devices is unreliable and use other means for achieving it
459 (i.e. udev).
461 If in doubt, say N.
463 config BLK_DEV_GENERIC
464 tristate "Generic PCI IDE Chipset Support"
465 select BLK_DEV_IDEPCI
466 help
467 This option provides generic support for various PCI IDE Chipsets
468 which otherwise might not be supported.
470 config BLK_DEV_OPTI621
471 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
472 depends on EXPERIMENTAL
473 select BLK_DEV_IDEPCI
474 help
475 This is a driver for the OPTi 82C621 EIDE controller.
476 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
478 config BLK_DEV_RZ1000
479 tristate "RZ1000 chipset bugfix/support"
480 depends on X86
481 select BLK_DEV_IDEPCI
482 help
483 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
484 Pentium motherboards, usually along with the "Neptune" chipset.
485 Unfortunately, it has a rather nasty design flaw that can cause
486 severe data corruption under many conditions. Say Y here to include
487 code which automatically detects and corrects the problem under
488 Linux. This may slow disk throughput by a few percent, but at least
489 things will operate 100% reliably.
491 config BLK_DEV_IDEDMA_PCI
492 bool
493 select BLK_DEV_IDEPCI
494 select BLK_DEV_IDEDMA_SFF
496 config BLK_DEV_AEC62XX
497 tristate "AEC62XX chipset support"
498 select BLK_DEV_IDEDMA_PCI
499 help
500 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
501 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
502 speeds and to configure the chip to optimum performance.
504 config BLK_DEV_ALI15X3
505 tristate "ALI M15x3 chipset support"
506 select BLK_DEV_IDEDMA_PCI
507 help
508 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
509 onboard chipsets. It also tests for Simplex mode and enables
510 normal dual channel support.
512 If you say Y here, you also need to say Y to "Use DMA by default
513 when available", above. Please read the comments at the top of
514 <file:drivers/ide/pci/alim15x3.c>.
516 If unsure, say N.
518 config WDC_ALI15X3
519 bool "ALI M15x3 WDC support (DANGEROUS)"
520 depends on BLK_DEV_ALI15X3
521 ---help---
522 This allows for UltraDMA support for WDC drives that ignore CRC
523 checking. You are a fool for enabling this option, but there have
524 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
525 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
526 SERIOUS WARNING.
528 Using this option can allow WDC drives to run at ATA-4/5 transfer
529 rates with only an ATA-2 support structure.
531 SAY N!
533 config BLK_DEV_AMD74XX
534 tristate "AMD and nVidia IDE support"
535 depends on !ARM
536 select BLK_DEV_IDEDMA_PCI
537 help
538 This driver adds explicit support for AMD-7xx and AMD-8111 chips
539 and also for the nVidia nForce chip. This allows the kernel to
540 change PIO, DMA and UDMA speeds and to configure the chip to
541 optimum performance.
543 config BLK_DEV_ATIIXP
544 tristate "ATI IXP chipset IDE support"
545 depends on X86
546 select BLK_DEV_IDEDMA_PCI
547 help
548 This driver adds explicit support for ATI IXP chipset.
549 This allows the kernel to change PIO, DMA and UDMA speeds
550 and to configure the chip to optimum performance.
552 Say Y here if you have an ATI IXP chipset IDE controller.
554 config BLK_DEV_CMD64X
555 tristate "CMD64{3|6|8|9} chipset support"
556 select BLK_DEV_IDEDMA_PCI
557 help
558 Say Y here if you have an IDE controller which uses any of these
559 chipsets: CMD643, CMD646, or CMD648.
561 config BLK_DEV_TRIFLEX
562 tristate "Compaq Triflex IDE support"
563 select BLK_DEV_IDEDMA_PCI
564 help
565 Say Y here if you have a Compaq Triflex IDE controller, such
566 as those commonly found on Compaq Pentium-Pro systems
568 config BLK_DEV_CY82C693
569 tristate "CY82C693 chipset support"
570 select BLK_DEV_IDEDMA_PCI
571 help
572 This driver adds detection and support for the CY82C693 chipset
573 used on Digital's PC-Alpha 164SX boards.
575 If you say Y here, you need to say Y to "Use DMA by default
576 when available" as well.
578 config BLK_DEV_CS5520
579 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
580 depends on EXPERIMENTAL
581 select BLK_DEV_IDEDMA_PCI
582 help
583 Include support for PIO tuning and virtual DMA on the Cyrix MediaGX
584 5510/5520 chipset. This will automatically be detected and
585 configured if found.
587 It is safe to say Y to this question.
589 config BLK_DEV_CS5530
590 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
591 select BLK_DEV_IDEDMA_PCI
592 help
593 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
594 will automatically be detected and configured if found.
596 It is safe to say Y to this question.
598 config BLK_DEV_CS5535
599 tristate "AMD CS5535 chipset support"
600 depends on X86 && !X86_64
601 select BLK_DEV_IDEDMA_PCI
602 help
603 Include support for UDMA on the NSC/AMD CS5535 companion chipset.
604 This will automatically be detected and configured if found.
606 It is safe to say Y to this question.
608 config BLK_DEV_HPT34X
609 tristate "HPT34X chipset support"
610 select BLK_DEV_IDEDMA_PCI
611 help
612 This driver adds up to 4 more EIDE devices sharing a single
613 interrupt. The HPT343 chipset in its current form is a non-bootable
614 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
615 PCI UDMA controllers. This driver requires dynamic tuning of the
616 chipset during the ide-probe at boot time. It is reported to support
617 DVD II drives, by the manufacturer.
619 config HPT34X_AUTODMA
620 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
621 depends on BLK_DEV_HPT34X && EXPERIMENTAL
622 help
623 This is a dangerous thing to attempt currently! Please read the
624 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
625 here, then say Y to "Use DMA by default when available" as well.
627 If unsure, say N.
629 config BLK_DEV_HPT366
630 tristate "HPT36X/37X chipset support"
631 select BLK_DEV_IDEDMA_PCI
632 help
633 HPT366 is an Ultra DMA chipset for ATA-66.
634 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
635 HPT370 is an Ultra DMA chipset for ATA-100.
636 HPT372 is an Ultra DMA chipset for ATA-100.
637 HPT374 is an Ultra DMA chipset for ATA-100.
639 This driver adds up to 4 more EIDE devices sharing a single
640 interrupt.
642 The HPT366 chipset in its current form is bootable. One solution
643 for this problem are special LILO commands for redirecting the
644 reference to device 0x80. The other solution is to say Y to "Boot
645 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
646 your mother board has the chipset natively mounted. Regardless one
647 should use the fore mentioned option and call at LILO or include
648 "ide=reverse" in LILO's append-line.
650 This driver requires dynamic tuning of the chipset during the
651 ide-probe at boot. It is reported to support DVD II drives, by the
652 manufacturer.
654 config BLK_DEV_JMICRON
655 tristate "JMicron JMB36x support"
656 select BLK_DEV_IDEDMA_PCI
657 help
658 Basic support for the JMicron ATA controllers. For full support
659 use the libata drivers.
661 config BLK_DEV_SC1200
662 tristate "National SCx200 chipset support"
663 select BLK_DEV_IDEDMA_PCI
664 help
665 This driver adds support for the on-board IDE controller on the
666 National SCx200 series of embedded x86 "Geode" systems.
668 config BLK_DEV_PIIX
669 tristate "Intel PIIXn chipsets support"
670 select BLK_DEV_IDEDMA_PCI
671 help
672 This driver adds explicit support for Intel PIIX and ICH chips
673 and also for the Efar Victory66 (slc90e66) chip. This allows
674 the kernel to change PIO, DMA and UDMA speeds and to configure
675 the chip to optimum performance.
677 config BLK_DEV_IT8213
678 tristate "IT8213 IDE support"
679 select BLK_DEV_IDEDMA_PCI
680 help
681 This driver adds support for the ITE 8213 IDE controller.
683 config BLK_DEV_IT821X
684 tristate "IT821X IDE support"
685 select BLK_DEV_IDEDMA_PCI
686 help
687 This driver adds support for the ITE 8211 IDE controller and the
688 IT 8212 IDE RAID controller in both RAID and pass-through mode.
690 config BLK_DEV_NS87415
691 tristate "NS87415 chipset support"
692 select BLK_DEV_IDEDMA_PCI
693 help
694 This driver adds detection and support for the NS87415 chip
695 (used mainly on SPARC64 and PA-RISC machines).
697 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
699 config BLK_DEV_PDC202XX_OLD
700 tristate "PROMISE PDC202{46|62|65|67} support"
701 select BLK_DEV_IDEDMA_PCI
702 help
703 Promise Ultra33 or PDC20246
704 Promise Ultra66 or PDC20262
705 Promise Ultra100 or PDC20265/PDC20267/PDC20268
707 This driver adds up to 4 more EIDE devices sharing a single
708 interrupt. This add-on card is a bootable PCI UDMA controller. Since
709 multiple cards can be installed and there are BIOS ROM problems that
710 happen if the BIOS revisions of all installed cards (three-max) do
711 not match, the driver attempts to do dynamic tuning of the chipset
712 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
713 for more than one card. This card may require that you say Y to
714 "Special UDMA Feature".
716 If you say Y here, you need to say Y to "Use DMA by default when
717 available" as well.
719 Please read the comments at the top of
720 <file:drivers/ide/pci/pdc202xx_old.c>.
722 If unsure, say N.
724 config BLK_DEV_PDC202XX_NEW
725 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
726 select BLK_DEV_IDEDMA_PCI
728 config BLK_DEV_SVWKS
729 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
730 select BLK_DEV_IDEDMA_PCI
731 help
732 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
733 chipsets.
735 config BLK_DEV_SGIIOC4
736 tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support"
737 depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4
738 select BLK_DEV_IDEDMA_PCI
739 help
740 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
741 chipset, which has one channel and can support two devices.
742 Please say Y here if you have an Altix System from SGI.
744 config BLK_DEV_SIIMAGE
745 tristate "Silicon Image chipset support"
746 select BLK_DEV_IDEDMA_PCI
747 help
748 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
749 3112 (Serial ATA) chips.
751 config BLK_DEV_SIS5513
752 tristate "SiS5513 chipset support"
753 depends on X86
754 select BLK_DEV_IDEDMA_PCI
755 help
756 This driver ensures (U)DMA support for SIS5513 chipset family based
757 mainboards.
759 The following chipsets are supported:
760 ATA16: SiS5511, SiS5513
761 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
762 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
763 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
764 SiS745, SiS750
766 If you say Y here, you need to say Y to "Use DMA by default when
767 available" as well.
769 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
771 config BLK_DEV_SL82C105
772 tristate "Winbond SL82c105 support"
773 depends on (PPC || ARM)
774 select BLK_DEV_IDEDMA_PCI
775 help
776 If you have a Winbond SL82c105 IDE controller, say Y here to enable
777 special configuration for this chip. This is common on various CHRP
778 motherboards, but could be used elsewhere. If in doubt, say Y.
780 config BLK_DEV_SLC90E66
781 tristate "SLC90E66 chipset support"
782 select BLK_DEV_IDEDMA_PCI
783 help
784 This driver ensures (U)DMA support for Victory66 SouthBridges for
785 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
786 The nice thing about it is that you can mix Ultra/DMA/PIO devices
787 and it will handle timing cycles. Since this is an improved
788 look-a-like to the PIIX4 it should be a nice addition.
790 If you say Y here, you need to say Y to "Use DMA by default when
791 available" as well.
793 Please read the comments at the top of
794 <file:drivers/ide/pci/slc90e66.c>.
796 config BLK_DEV_TRM290
797 tristate "Tekram TRM290 chipset support"
798 select BLK_DEV_IDEDMA_PCI
799 help
800 This driver adds support for bus master DMA transfers
801 using the Tekram TRM290 PCI IDE chip. Volunteers are
802 needed for further tweaking and development.
803 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
805 config BLK_DEV_VIA82CXXX
806 tristate "VIA82CXXX chipset support"
807 select BLK_DEV_IDEDMA_PCI
808 help
809 This driver adds explicit support for VIA BusMastering IDE chips.
810 This allows the kernel to change PIO, DMA and UDMA speeds and to
811 configure the chip to optimum performance.
813 config BLK_DEV_TC86C001
814 tristate "Toshiba TC86C001 support"
815 select BLK_DEV_IDEDMA_PCI
816 help
817 This driver adds support for Toshiba TC86C001 GOKU-S chip.
819 config BLK_DEV_CELLEB
820 tristate "Toshiba's Cell Reference Set IDE support"
821 depends on PPC_CELLEB
822 select BLK_DEV_IDEDMA_PCI
823 help
824 This driver provides support for the on-board IDE controller on
825 Toshiba Cell Reference Board.
826 If unsure, say Y.
828 endif
830 config BLK_DEV_IDE_PMAC
831 tristate "PowerMac on-board IDE support"
832 depends on PPC_PMAC && IDE=y && BLK_DEV_IDE=y
833 help
834 This driver provides support for the on-board IDE controller on
835 most of the recent Apple Power Macintoshes and PowerBooks.
836 If unsure, say Y.
838 config BLK_DEV_IDE_PMAC_ATA100FIRST
839 bool "Probe on-board ATA/100 (Kauai) first"
840 depends on BLK_DEV_IDE_PMAC
841 help
842 This option will cause the ATA/100 controller found in UniNorth2
843 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
844 to be probed before the ATA/66 and ATA/33 controllers. Without
845 these, those machine used to have the hard disk on hdc and the
846 CD-ROM on hda. This option changes this to more natural hda for
847 hard disk and hdc for CD-ROM.
849 config BLK_DEV_IDEDMA_PMAC
850 bool "PowerMac IDE DMA support"
851 depends on BLK_DEV_IDE_PMAC
852 select BLK_DEV_IDEDMA_PCI
853 help
854 This option allows the driver for the on-board IDE controller on
855 Power Macintoshes and PowerBooks to use DMA (direct memory access)
856 to transfer data to and from memory. Saying Y is safe and improves
857 performance.
859 config BLK_DEV_IDE_SWARM
860 tristate "IDE for Sibyte evaluation boards"
861 depends on SIBYTE_SB1xxx_SOC
863 config BLK_DEV_IDE_AU1XXX
864 bool "IDE for AMD Alchemy Au1200"
865 depends on SOC_AU1200
866 choice
867 prompt "IDE Mode for AMD Alchemy Au1200"
868 default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA
869 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
871 config BLK_DEV_IDE_AU1XXX_PIO_DBDMA
872 bool "PIO+DbDMA IDE for AMD Alchemy Au1200"
874 config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
875 bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200"
876 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
877 endchoice
879 config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ
880 int "Maximum transfer size (KB) per request (up to 128)"
881 default "128"
882 depends on BLK_DEV_IDE_AU1XXX
884 config IDE_ARM
885 tristate "ARM IDE support"
886 depends on ARM && (ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
887 default y
889 config BLK_DEV_IDE_ICSIDE
890 tristate "ICS IDE interface support"
891 depends on ARM && ARCH_ACORN
892 help
893 On Acorn systems, say Y here if you wish to use the ICS IDE
894 interface card. This is not required for ICS partition support.
895 If you are unsure, say N to this.
897 config BLK_DEV_IDEDMA_ICS
898 bool "ICS DMA support"
899 depends on BLK_DEV_IDE_ICSIDE
900 help
901 Say Y here if you want to add DMA (Direct Memory Access) support to
902 the ICS IDE driver.
904 config BLK_DEV_IDE_RAPIDE
905 tristate "RapIDE interface support"
906 depends on ARM && ARCH_ACORN
907 help
908 Say Y here if you want to support the Yellowstone RapIDE controller
909 manufactured for use with Acorn computers.
911 config BLK_DEV_IDE_BAST
912 tristate "Simtec BAST / Thorcom VR1000 IDE support"
913 depends on ARM && (ARCH_BAST || MACH_VR1000)
914 help
915 Say Y here if you want to support the onboard IDE channels on the
916 Simtec BAST or the Thorcom VR1000
918 config ETRAX_IDE
919 tristate "ETRAX IDE support"
920 depends on CRIS && BROKEN
921 select BLK_DEV_IDEDMA
922 help
923 Enables the ETRAX IDE driver.
925 You can't use parallel ports or SCSI ports at the same time.
927 config ETRAX_IDE_DELAY
928 int "Delay for drives to regain consciousness"
929 depends on ETRAX_IDE && ETRAX_ARCH_V10
930 default 15
931 help
932 Number of seconds to wait for IDE drives to spin up after an IDE
933 reset.
935 choice
936 prompt "IDE reset pin"
937 depends on ETRAX_IDE && ETRAX_ARCH_V10
938 default ETRAX_IDE_PB7_RESET
940 config ETRAX_IDE_PB7_RESET
941 bool "Port_PB_Bit_7"
942 help
943 IDE reset on pin 7 on port B
945 config ETRAX_IDE_G27_RESET
946 bool "Port_G_Bit_27"
947 help
948 IDE reset on pin 27 on port G
950 endchoice
952 config IDE_H8300
953 tristate "H8300 IDE support"
954 depends on H8300
955 default y
956 help
957 Enables the H8300 IDE driver.
959 config BLK_DEV_GAYLE
960 tristate "Amiga Gayle IDE interface support"
961 depends on AMIGA
962 help
963 This is the IDE driver for the Amiga Gayle IDE interface. It supports
964 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
965 This includes on-board IDE interfaces on some Amiga models (A600,
966 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
967 bus (M-Tech E-Matrix 530 expansion card).
968 Say Y if you have an Amiga with a Gayle IDE interface and want to use
969 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
970 it.
971 Note that you also have to enable Zorro bus support if you want to
972 use Gayle IDE interfaces on the Zorro expansion bus.
974 config BLK_DEV_IDEDOUBLER
975 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
976 depends on BLK_DEV_GAYLE && EXPERIMENTAL
977 ---help---
978 This driver provides support for the so-called `IDE doublers' (made
979 by various manufacturers, e.g. Eyetech) that can be connected to
980 the on-board IDE interface of some Amiga models. Using such an IDE
981 doubler, you can connect up to four instead of two IDE devices to
982 the Amiga's on-board IDE interface.
984 Note that the normal Amiga Gayle IDE driver may not work correctly
985 if you have an IDE doubler and don't enable this driver!
987 Say Y if you have an IDE doubler. The driver is enabled at kernel
988 runtime using the "ide=doubler" kernel boot parameter.
990 config BLK_DEV_BUDDHA
991 tristate "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
992 depends on ZORRO && EXPERIMENTAL
993 help
994 This is the IDE driver for the IDE interfaces on the Buddha, Catweasel
995 and X-Surf expansion boards. It supports up to two interfaces on the
996 Buddha, three on the Catweasel and two on the X-Surf.
998 Say Y if you have a Buddha or Catweasel expansion board and want to
999 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
1000 to one of its IDE interfaces.
1002 config BLK_DEV_FALCON_IDE
1003 tristate "Falcon IDE interface support"
1004 depends on ATARI
1005 help
1006 This is the IDE driver for the on-board IDE interface on the Atari
1007 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
1008 disks, CD-ROM drives, etc.) that are connected to the on-board IDE
1009 interface.
1011 config BLK_DEV_MAC_IDE
1012 tristate "Macintosh Quadra/Powerbook IDE interface support"
1013 depends on MAC
1014 help
1015 This is the IDE driver for the on-board IDE interface on some m68k
1016 Macintosh models. It supports both the `Quadra style' (used in
1017 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
1018 (used in the Powerbook 150 and 190 models) IDE interface.
1020 Say Y if you have such an Macintosh model and want to use IDE
1021 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1022 on-board IDE interface.
1024 config BLK_DEV_Q40IDE
1025 tristate "Q40/Q60 IDE interface support"
1026 depends on Q40
1027 help
1028 Enable the on-board IDE controller in the Q40/Q60. This should
1029 normally be on; disable it only if you are running a custom hard
1030 drive subsystem through an expansion card.
1032 config BLK_DEV_PALMCHIP_BK3710
1033 tristate "Palmchip bk3710 IDE controller support"
1034 depends on ARCH_DAVINCI
1035 select BLK_DEV_IDEDMA_SFF
1036 help
1037 Say Y here if you want to support the onchip IDE controller on the
1038 TI DaVinci SoC
1041 config BLK_DEV_MPC8xx_IDE
1042 tristate "MPC8xx IDE support"
1043 depends on 8xx && (LWMON || IVMS8 || IVML24 || TQM8xxL) && IDE=y && BLK_DEV_IDE=y && !PPC_MERGE
1044 help
1045 This option provides support for IDE on Motorola MPC8xx Systems.
1046 Please see 'Type of MPC8xx IDE interface' for details.
1048 If unsure, say N.
1050 choice
1051 prompt "Type of MPC8xx IDE interface"
1052 depends on BLK_DEV_MPC8xx_IDE
1053 default IDE_8xx_PCCARD
1055 config IDE_8xx_PCCARD
1056 bool "8xx_PCCARD"
1057 ---help---
1058 Select how the IDE devices are connected to the MPC8xx system:
1060 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
1061 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
1062 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
1063 systems)
1065 8xx_DIRECT is used for directly connected IDE devices using the 8xx
1066 internal PCMCIA interface (example: IVMS8 systems)
1068 EXT_DIRECT is used for IDE devices directly connected to the 8xx
1069 bus using some glue logic, but _not_ the 8xx internal
1070 PCMCIA interface (example: IDIF860 systems)
1072 config IDE_8xx_DIRECT
1073 bool "8xx_DIRECT"
1075 config IDE_EXT_DIRECT
1076 bool "EXT_DIRECT"
1078 endchoice
1080 # no isa -> no vlb
1081 if ISA
1083 comment "Other IDE chipsets support"
1084 comment "Note: most of these also require special kernel boot parameters"
1086 config BLK_DEV_4DRIVES
1087 bool "Generic 4 drives/port support"
1088 help
1089 Certain older chipsets, including the Tekram 690CD, use a single set
1090 of I/O ports at 0x1f0 to control up to four drives, instead of the
1091 customary two drives per port. Support for this can be enabled at
1092 runtime using the "ide0=four" kernel boot parameter if you say Y
1093 here.
1095 config BLK_DEV_ALI14XX
1096 tristate "ALI M14xx support"
1097 help
1098 This driver is enabled at runtime using the "ali14xx.probe" kernel
1099 boot parameter. It enables support for the secondary IDE interface
1100 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1101 <<<<<<< HEAD:drivers/ide/Kconfig
1102 I/O speeds to be set as well. See the files
1103 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c>
1104 for more info.
1105 =======
1106 I/O speeds to be set as well.
1107 See the files <file:Documentation/ide/ide.txt> and
1108 <file:drivers/ide/legacy/ali14xx.c> for more info.
1109 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
1111 config BLK_DEV_DTC2278
1112 tristate "DTC-2278 support"
1113 help
1114 This driver is enabled at runtime using the "dtc2278.probe" kernel
1115 boot parameter. It enables support for the secondary IDE interface
1116 of the DTC-2278 card, and permits faster I/O speeds to be set as
1117 <<<<<<< HEAD:drivers/ide/Kconfig
1118 well. See the <file:Documentation/ide.txt> and
1119 =======
1120 well. See the <file:Documentation/ide/ide.txt> and
1121 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
1122 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1124 config BLK_DEV_HT6560B
1125 tristate "Holtek HT6560B support"
1126 help
1127 This driver is enabled at runtime using the "ht6560b.probe" kernel
1128 boot parameter. It enables support for the secondary IDE interface
1129 of the Holtek card, and permits faster I/O speeds to be set as well.
1130 <<<<<<< HEAD:drivers/ide/Kconfig
1131 See the <file:Documentation/ide.txt> and
1132 =======
1133 See the <file:Documentation/ide/ide.txt> and
1134 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
1135 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1137 config BLK_DEV_QD65XX
1138 tristate "QDI QD65xx support"
1139 help
1140 This driver is enabled at runtime using the "qd65xx.probe" kernel
1141 boot parameter. It permits faster I/O speeds to be set. See the
1142 <<<<<<< HEAD:drivers/ide/Kconfig
1143 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c>
1144 =======
1145 <file:Documentation/ide/ide.txt> and <file:drivers/ide/legacy/qd65xx.c>
1146 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
1147 for more info.
1149 config BLK_DEV_UMC8672
1150 tristate "UMC-8672 support"
1151 help
1152 This driver is enabled at runtime using the "umc8672.probe" kernel
1153 boot parameter. It enables support for the secondary IDE interface
1154 of the UMC-8672, and permits faster I/O speeds to be set as well.
1155 <<<<<<< HEAD:drivers/ide/Kconfig
1156 See the files <file:Documentation/ide.txt> and
1157 =======
1158 See the files <file:Documentation/ide/ide.txt> and
1159 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/ide/Kconfig
1160 <file:drivers/ide/legacy/umc8672.c> for more info.
1162 endif
1164 config BLK_DEV_IDEDMA
1165 def_bool BLK_DEV_IDEDMA_SFF || BLK_DEV_IDEDMA_PMAC || \
1166 BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
1168 config IDE_ARCH_OBSOLETE_INIT
1169 def_bool ALPHA || (ARM && !ARCH_L7200) || BLACKFIN || X86 || IA64 || M32R || MIPS || PARISC || PPC || (SUPERH64 && BLK_DEV_IDEPCI) || SPARC
1171 endif
1173 config BLK_DEV_HD_ONLY
1174 bool "Old hard disk (MFM/RLL/IDE) driver"
1175 depends on BLK_DEV_IDE=n
1176 help
1177 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1178 the newer enhanced driver, but this old one is still around for two
1179 reasons. Some older systems have strange timing problems and seem to
1180 work only with the old driver (which itself does not work with some
1181 newer systems). The other reason is that the old driver is smaller,
1182 since it lacks the enhanced functionality of the new one. This makes
1183 it a good choice for systems with very tight memory restrictions, or
1184 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1185 driver can save 13 KB or so of kernel memory.
1187 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1188 instead of this one. For more detailed information, read the
1189 Disk-HOWTO, available from
1190 <http://www.tldp.org/docs.html#howto>.
1192 config BLK_DEV_HD
1193 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY
1195 endif # IDE