2 # IDE ATA ATAPI Block device driver configuration
4 # Andre Hedrick <andre@linux-ide.org>
8 tristate "ATA/ATAPI/MFM/RLL support"
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.
16 If your system is pure SCSI and doesn't use these interfaces, you
19 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
20 for mass storage units such as hard disks. It was designed by
21 Western Digital and Compaq Computer in 1984. It was then named
22 ST506. Quite a number of disks use the IDE interface.
24 AT Attachment (ATA) is the superset of the IDE specifications.
25 ST506 was also called ATA-1.
27 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
28 ATA-3. It provides support for larger disks (up to 8.4GB by means of
29 the LBA standard), more disks (4 instead of 2) and for other mass
30 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
31 ATA-4 and provides faster (and more CPU friendly) transfer modes
32 than previous PIO (Programmed processor Input/Output) from previous
33 ATA/IDE standards by means of fast DMA controllers.
35 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
36 CD-ROM drives, similar in many respects to the SCSI protocol.
38 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
39 designed in order to prevent data corruption and disk crash by
40 detecting pre hardware failure conditions (heat, access time, and
41 the like...). Disks built since June 1995 may follow this standard.
42 The kernel itself doesn't manage this; however there are quite a
43 number of user programs such as smart that can query the status of
44 SMART parameters from disk drives.
46 To compile this driver as a module, choose M here: the
47 module will be called ide.
49 For further information, please read <file:Documentation/ide.txt>.
56 int "Max IDE interfaces"
57 depends on ALPHA || SUPERH || IA64 || EMBEDDED
61 This is the maximum number of IDE hardware interfaces that will
62 be supported by the driver. Make sure it is at least as high as
63 the number of IDE interfaces in your system.
66 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
68 If you say Y here, you will use the full-featured IDE driver to
69 control up to ten ATA/IDE interfaces, each being able to serve a
70 "master" and a "slave" device, for a total of up to twenty ATA/IDE
71 disk/cdrom/tape/floppy drives.
73 Useful information about large (>540 MB) IDE disks, multiple
74 interfaces, what to do if ATA/IDE devices are not automatically
75 detected, sound card ATA/IDE ports, module support, and other
76 topics, is contained in <file:Documentation/ide.txt>. For detailed
77 information about hard drives, consult the Disk-HOWTO and the
78 Multi-Disk-HOWTO, available from
79 <http://www.tldp.org/docs.html#howto>.
81 To fine-tune ATA/IDE drive/interface parameters for improved
82 performance, look for the hdparm package at
83 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
85 To compile this driver as a module, choose M here and read
86 <file:Documentation/ide.txt>. The module will be called ide-mod.
87 Do not compile this driver as a module if your root file system (the
88 one containing the directory /) is located on an IDE device.
90 If you have one or more IDE drives, say Y or M here. If your system
91 has no IDE drives, or if memory requirements are really tight, you
92 could say N here, and select the "Old hard disk driver" below
93 instead to save about 13 KB of memory in the kernel.
97 comment "Please see Documentation/ide.txt for help/info on IDE drives"
99 config BLK_DEV_IDE_SATA
100 bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
103 There are two drivers for Serial ATA controllers.
105 The main driver, "libata", uses the SCSI subsystem
106 and supports most modern SATA controllers. In order to use it
107 you may take a look at "Serial ATA (prod) and Parallel ATA
108 (experimental) drivers".
110 The IDE driver (which you are currently configuring) supports
111 a few first-generation SATA controllers.
113 In order to eliminate conflicts between the two subsystems,
114 this config option enables the IDE driver's SATA support.
115 Normally this is disabled, as it is preferred that libata
116 supports SATA controllers, and this (IDE) driver supports
121 config BLK_DEV_HD_IDE
122 bool "Use old disk-only driver on primary interface"
123 depends on (X86 || SH_MPC1211)
125 There are two drivers for MFM/RLL/IDE disks. Most people use just
126 the new enhanced driver by itself. This option however installs the
127 old hard disk driver to control the primary IDE/disk interface in
128 the system, leaving the new enhanced IDE driver to take care of only
129 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
130 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
131 IDE interface. Choosing this option may be useful for older systems
132 which have MFM/RLL/ESDI controller+drives at the primary port
133 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
136 Normally, just say N here; you will then use the new driver for all
139 config BLK_DEV_IDEDISK
140 tristate "Include IDE/ATA-2 DISK support"
142 This will include enhanced support for MFM/RLL/IDE hard disks. If
143 you have a MFM/RLL/IDE disk, and there is no special reason to use
144 the old hard disk driver instead, say Y. If you have an SCSI-only
145 system, you can say N here.
147 To compile this driver as a module, choose M here: the
148 module will be called ide-disk.
149 Do not compile this driver as a module if your root file system
150 (the one containing the directory /) is located on the IDE disk.
154 config IDEDISK_MULTI_MODE
155 bool "Use multi-mode by default"
157 If you get this error, try to say Y here:
159 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
160 hda: set_multmode: error=0x04 { DriveStatusError }
165 tristate "PCMCIA IDE support"
168 Support for Compact Flash cards, outboard IDE disks, tape drives,
169 and CD-ROM drives connected through a PCMCIA card.
171 config BLK_DEV_DELKIN
172 tristate "Cardbus IDE support (Delkin/ASKA/Workbit)"
173 depends on CARDBUS && PCI
175 Support for Delkin, ASKA, and Workbit Cardbus CompactFlash
176 Adapters. This may also work for similar SD and XD adapters.
179 tristate "Include IDE/ATAPI CDROM support"
181 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
182 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
183 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
184 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
185 double(2X) or better speed drives.
187 If you say Y here, the CD-ROM drive will be identified at boot time
188 along with other IDE devices, as "hdb" or "hdc", or something
189 similar (check the boot messages with dmesg). If this is your only
190 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
191 to say Y or M to "ISO 9660 CD-ROM file system support".
193 Note that older versions of LILO (LInux LOader) cannot properly deal
194 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
195 <http://lilo.go.dyndns.org/>.
197 To compile this driver as a module, choose M here: the
198 module will be called ide-cd.
200 config BLK_DEV_IDETAPE
201 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
202 depends on EXPERIMENTAL
204 If you have an IDE tape drive using the ATAPI protocol, say Y.
205 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
206 similar to the SCSI protocol. If you have an SCSI tape drive
207 however, you can say N here.
209 You should also say Y if you have an OnStream DI-30 tape drive; this
210 will not work with the SCSI protocol, until there is support for the
211 SC-30 and SC-50 versions.
213 If you say Y here, the tape drive will be identified at boot time
214 along with other IDE devices, as "hdb" or "hdc", or something
215 similar, and will be mapped to a character device such as "ht0"
216 (check the boot messages with dmesg). Be sure to consult the
217 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
218 for usage information.
220 To compile this driver as a module, choose M here: the
221 module will be called ide-tape.
223 config BLK_DEV_IDEFLOPPY
224 tristate "Include IDE/ATAPI FLOPPY support"
226 If you have an IDE floppy drive which uses the ATAPI protocol,
227 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
228 drives, similar to the SCSI protocol.
230 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
231 this driver. For information about jumper settings and the question
232 of when a ZIP drive uses a partition table, see
233 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
234 (ATAPI PD-CD/CDR drives are not supported by this driver; support
235 for PD-CD/CDR drives is available if you answer Y to
236 "SCSI emulation support", below).
238 If you say Y here, the FLOPPY drive will be identified along with
239 other IDE devices, as "hdb" or "hdc", or something similar (check
240 the boot messages with dmesg).
242 To compile this driver as a module, choose M here: the
243 module will be called ide-floppy.
245 config BLK_DEV_IDESCSI
246 tristate "SCSI emulation support"
249 WARNING: ide-scsi is no longer needed for cd writing applications!
250 The 2.6 kernel supports direct writing to ide-cd, which eliminates
251 the need for ide-scsi + the entire scsi stack just for writing a
252 cd. The new method is more efficient in every way.
254 This will provide SCSI host adapter emulation for IDE ATAPI devices,
255 and will allow you to use a SCSI device driver instead of a native
258 This is useful if you have an ATAPI device for which no native
259 driver has been written (for example, an ATAPI PD-CD drive);
260 you can then use this emulation together with an appropriate SCSI
261 device driver. In order to do this, say Y here and to "SCSI support"
262 and "SCSI generic support", below. You must then provide the kernel
263 command line "hdx=ide-scsi" (try "man bootparam" or see the
264 documentation of your boot loader (lilo or loadlin) about how to
265 pass options to the kernel at boot time) for devices if you want the
266 native EIDE sub-drivers to skip over the native support, so that
267 this SCSI emulation can be used instead.
269 Note that this option does NOT allow you to attach SCSI devices to a
270 box that doesn't have a SCSI host adapter installed.
272 If both this SCSI emulation and native ATAPI support are compiled
273 into the kernel, the native support will be used.
275 config BLK_DEV_IDEACPI
276 bool "IDE ACPI support"
279 Implement ACPI support for generic IDE devices. On modern
280 machines ACPI support is required to properly handle ACPI S3 states.
282 config IDE_TASK_IOCTL
283 bool "IDE Taskfile Access"
285 This is a direct raw access to the media. It is a complex but
286 elegant solution to test and validate the domain of the hardware and
287 perform below the driver data recovery if needed. This is the most
288 basic form of media-forensics.
290 If you are unsure, say N here.
293 bool "legacy /proc/ide/ support"
294 depends on IDE && PROC_FS
297 This option enables support for the various files in
298 /proc/ide. In Linux 2.6 this has been superseded by
299 files in sysfs but many legacy applications rely on this.
303 comment "IDE chipset support/bugfixes"
306 tristate "generic/default IDE chipset support"
311 config BLK_DEV_CMD640
312 bool "CMD640 chipset bugfix/support"
315 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
316 Pentium motherboards, usually in combination with a "Neptune" or
317 "SiS" chipset. Unfortunately, it has a number of rather nasty
318 design flaws that can cause severe data corruption under many common
319 conditions. Say Y here to include code which tries to automatically
320 detect and correct the problems under Linux. This option also
321 enables access to the secondary IDE ports in some CMD640 based
324 This driver will work automatically in PCI based systems (most new
325 systems have PCI slots). But if your system uses VESA local bus
326 (VLB) instead of PCI, you must also supply a kernel boot parameter
327 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
328 bootparam" or see the documentation of your boot loader about how to
329 pass options to the kernel.)
331 The CMD640 chip is also used on add-in cards by Acculogic, and on
332 the "CSA-6400E PCI to IDE controller" that some people have. For
333 details, read <file:Documentation/ide.txt>.
335 config BLK_DEV_CMD640_ENHANCED
336 bool "CMD640 enhanced support"
337 depends on BLK_DEV_CMD640
339 This option includes support for setting/autotuning PIO modes and
340 prefetch on CMD640 IDE interfaces. For details, read
341 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
342 and your BIOS does not already do this for you, then say Y here.
345 config BLK_DEV_IDEPNP
346 bool "PNP EIDE support"
350 If you have a PnP (Plug and Play) compatible EIDE card and
351 would like the kernel to automatically detect and activate
354 config BLK_DEV_IDEPCI
355 bool "PCI IDE chipset support" if PCI
356 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
358 Say Y here for PCI systems which use IDE drive(s).
359 This option helps the IDE driver to automatically detect and
360 configure all PCI-based IDE interfaces in your system.
362 config IDEPCI_SHARE_IRQ
363 bool "Sharing PCI IDE interrupts support"
364 depends on PCI && BLK_DEV_IDEPCI
366 Some ATA/IDE chipsets have hardware support which allows for
367 sharing a single IRQ with other cards. To enable support for
368 this in the ATA/IDE driver, say Y here.
370 It is safe to say Y to this question, in most cases.
373 config IDEPCI_PCIBUS_ORDER
374 def_bool PCI && BLK_DEV_IDE=y && BLK_DEV_IDEPCI
376 config BLK_DEV_OFFBOARD
377 bool "Boot off-board chipsets first support"
378 depends on PCI && BLK_DEV_IDEPCI
380 Normally, IDE controllers built into the motherboard (on-board
381 controllers) are assigned to ide0 and ide1 while those on add-in PCI
382 cards (off-board controllers) are relegated to ide2 and ide3.
383 Answering Y here will allow you to reverse the situation, with
384 off-board controllers on ide0/1 and on-board controllers on ide2/3.
385 This can improve the usability of some boot managers such as lilo
386 when booting from a drive on an off-board controller.
388 If you say Y here, and you actually want to reverse the device scan
389 order as explained above, you also need to issue the kernel command
390 line option "ide=reverse". (Try "man bootparam" or see the
391 documentation of your boot loader (lilo or loadlin) about how to
392 pass options to the kernel at boot time.)
394 Note that, if you do this, the order of the hd* devices will be
395 rearranged which may require modification of fstab and other files.
399 config BLK_DEV_GENERIC
400 tristate "Generic PCI IDE Chipset Support"
401 depends on BLK_DEV_IDEPCI
403 This option provides generic support for various PCI IDE Chipsets
404 which otherwise might not be supported.
406 config BLK_DEV_OPTI621
407 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
408 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
410 This is a driver for the OPTi 82C621 EIDE controller.
411 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
413 config BLK_DEV_RZ1000
414 tristate "RZ1000 chipset bugfix/support"
415 depends on PCI && BLK_DEV_IDEPCI && X86
417 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
418 Pentium motherboards, usually along with the "Neptune" chipset.
419 Unfortunately, it has a rather nasty design flaw that can cause
420 severe data corruption under many conditions. Say Y here to include
421 code which automatically detects and corrects the problem under
422 Linux. This may slow disk throughput by a few percent, but at least
423 things will operate 100% reliably.
425 config BLK_DEV_IDEDMA_PCI
426 bool "Generic PCI bus-master DMA support"
427 depends on PCI && BLK_DEV_IDEPCI
429 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
430 is capable of bus-master DMA operation (most Pentium PCI systems),
431 you will want to say Y here to reduce CPU overhead. You can then use
432 the "hdparm" utility to enable DMA for drives for which it was not
433 enabled automatically. By default, DMA is not enabled automatically
434 for these drives, but you can change that by saying Y to the
435 following question "Use DMA by default when available". You can get
436 the latest version of the hdparm utility from
437 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
439 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
440 and the file <file:Documentation/ide.txt> for more information.
442 It is safe to say Y to this question.
444 if BLK_DEV_IDEDMA_PCI
446 config BLK_DEV_IDEDMA_FORCED
447 bool "Force enable legacy 2.0.X HOSTS to use DMA"
449 This is an old piece of lost code from Linux 2.0 Kernels.
451 Generally say N here.
453 config IDEDMA_ONLYDISK
454 bool "Enable DMA only for disks "
456 This is used if you know your ATAPI Devices are going to fail DMA
459 Generally say N here.
461 config BLK_DEV_AEC62XX
462 tristate "AEC62XX chipset support"
464 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
465 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
466 speeds and to configure the chip to optimum performance.
468 config BLK_DEV_ALI15X3
469 tristate "ALI M15x3 chipset support"
471 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
472 onboard chipsets. It also tests for Simplex mode and enables
473 normal dual channel support.
475 If you say Y here, you also need to say Y to "Use DMA by default
476 when available", above. Please read the comments at the top of
477 <file:drivers/ide/pci/alim15x3.c>.
482 bool "ALI M15x3 WDC support (DANGEROUS)"
483 depends on BLK_DEV_ALI15X3
485 This allows for UltraDMA support for WDC drives that ignore CRC
486 checking. You are a fool for enabling this option, but there have
487 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
488 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
491 Using this option can allow WDC drives to run at ATA-4/5 transfer
492 rates with only an ATA-2 support structure.
496 config BLK_DEV_AMD74XX
497 tristate "AMD and nVidia IDE support"
499 This driver adds explicit support for AMD-7xx and AMD-8111 chips
500 and also for the nVidia nForce chip. This allows the kernel to
501 change PIO, DMA and UDMA speeds and to configure the chip to
504 config BLK_DEV_ATIIXP
505 tristate "ATI IXP chipset IDE support"
508 This driver adds explicit support for ATI IXP chipset.
509 This allows the kernel to change PIO, DMA and UDMA speeds
510 and to configure the chip to optimum performance.
512 Say Y here if you have an ATI IXP chipset IDE controller.
514 config BLK_DEV_CMD64X
515 tristate "CMD64{3|6|8|9} chipset support"
517 Say Y here if you have an IDE controller which uses any of these
518 chipsets: CMD643, CMD646, or CMD648.
520 config BLK_DEV_TRIFLEX
521 tristate "Compaq Triflex IDE support"
523 Say Y here if you have a Compaq Triflex IDE controller, such
524 as those commonly found on Compaq Pentium-Pro systems
526 config BLK_DEV_CY82C693
527 tristate "CY82C693 chipset support"
529 This driver adds detection and support for the CY82C693 chipset
530 used on Digital's PC-Alpha 164SX boards.
532 If you say Y here, you need to say Y to "Use DMA by default
533 when available" as well.
535 config BLK_DEV_CS5520
536 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
537 depends on EXPERIMENTAL
539 Include support for PIO tuning and virtual DMA on the Cyrix MediaGX
540 5510/5520 chipset. This will automatically be detected and
543 It is safe to say Y to this question.
545 config BLK_DEV_CS5530
546 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
548 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
549 will automatically be detected and configured if found.
551 It is safe to say Y to this question.
553 config BLK_DEV_CS5535
554 tristate "AMD CS5535 chipset support"
555 depends on X86 && !X86_64
557 Include support for UDMA on the NSC/AMD CS5535 companion chipset.
558 This will automatically be detected and configured if found.
560 It is safe to say Y to this question.
562 config BLK_DEV_HPT34X
563 tristate "HPT34X chipset support"
565 This driver adds up to 4 more EIDE devices sharing a single
566 interrupt. The HPT343 chipset in its current form is a non-bootable
567 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
568 PCI UDMA controllers. This driver requires dynamic tuning of the
569 chipset during the ide-probe at boot time. It is reported to support
570 DVD II drives, by the manufacturer.
572 config HPT34X_AUTODMA
573 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
574 depends on BLK_DEV_HPT34X && EXPERIMENTAL
576 This is a dangerous thing to attempt currently! Please read the
577 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
578 here, then say Y to "Use DMA by default when available" as well.
582 config BLK_DEV_HPT366
583 tristate "HPT36X/37X chipset support"
585 HPT366 is an Ultra DMA chipset for ATA-66.
586 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
587 HPT370 is an Ultra DMA chipset for ATA-100.
588 HPT372 is an Ultra DMA chipset for ATA-100.
589 HPT374 is an Ultra DMA chipset for ATA-100.
591 This driver adds up to 4 more EIDE devices sharing a single
594 The HPT366 chipset in its current form is bootable. One solution
595 for this problem are special LILO commands for redirecting the
596 reference to device 0x80. The other solution is to say Y to "Boot
597 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
598 your mother board has the chipset natively mounted. Regardless one
599 should use the fore mentioned option and call at LILO or include
600 "ide=reverse" in LILO's append-line.
602 This driver requires dynamic tuning of the chipset during the
603 ide-probe at boot. It is reported to support DVD II drives, by the
606 config BLK_DEV_JMICRON
607 tristate "JMicron JMB36x support"
609 Basic support for the JMicron ATA controllers. For full support
610 use the libata drivers.
612 config BLK_DEV_SC1200
613 tristate "National SCx200 chipset support"
615 This driver adds support for the built in IDE on the National
616 SCx200 series of embedded x86 "Geode" systems
619 tristate "Intel PIIXn chipsets support"
621 This driver adds explicit support for Intel PIIX and ICH chips
622 and also for the Efar Victory66 (slc90e66) chip. This allows
623 the kernel to change PIO, DMA and UDMA speeds and to configure
624 the chip to optimum performance.
626 config BLK_DEV_IT8213
627 tristate "IT8213 IDE support"
629 This driver adds support for the ITE 8213 IDE controller.
631 config BLK_DEV_IT821X
632 tristate "IT821X IDE support"
634 This driver adds support for the ITE 8211 IDE controller and the
635 IT 8212 IDE RAID controller in both RAID and pass-through mode.
637 config BLK_DEV_NS87415
638 tristate "NS87415 chipset support"
640 This driver adds detection and support for the NS87415 chip
641 (used mainly on SPARC64 and PA-RISC machines).
643 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
645 config BLK_DEV_PDC202XX_OLD
646 tristate "PROMISE PDC202{46|62|65|67} support"
648 Promise Ultra33 or PDC20246
649 Promise Ultra66 or PDC20262
650 Promise Ultra100 or PDC20265/PDC20267/PDC20268
652 This driver adds up to 4 more EIDE devices sharing a single
653 interrupt. This add-on card is a bootable PCI UDMA controller. Since
654 multiple cards can be installed and there are BIOS ROM problems that
655 happen if the BIOS revisions of all installed cards (three-max) do
656 not match, the driver attempts to do dynamic tuning of the chipset
657 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
658 for more than one card. This card may require that you say Y to
659 "Special UDMA Feature".
661 If you say Y here, you need to say Y to "Use DMA by default when
664 Please read the comments at the top of
665 <file:drivers/ide/pci/pdc202xx_old.c>.
669 config PDC202XX_BURST
670 bool "Special UDMA Feature"
671 depends on BLK_DEV_PDC202XX_OLD
673 This option causes the pdc202xx driver to enable UDMA modes on the
674 PDC202xx even when the PDC202xx BIOS has not done so.
676 It was originally designed for the PDC20246/Ultra33, whose BIOS will
677 only setup UDMA on the first two PDC20246 cards. It has also been
678 used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
679 when the PDC20265 BIOS has been disabled (for faster boot up).
681 Please read the comments at the top of
682 <file:drivers/ide/pci/pdc202xx_old.c>.
686 config BLK_DEV_PDC202XX_NEW
687 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
690 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
692 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
695 config BLK_DEV_SGIIOC4
696 tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support"
697 depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4
698 select IDEPCI_SHARE_IRQ
700 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
701 chipset, which has one channel and can support two devices.
702 Please say Y here if you have an Altix System from SGI.
704 config BLK_DEV_SIIMAGE
705 tristate "Silicon Image chipset support"
707 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
708 3112 (Serial ATA) chips.
710 config BLK_DEV_SIS5513
711 tristate "SiS5513 chipset support"
714 This driver ensures (U)DMA support for SIS5513 chipset family based
717 The following chipsets are supported:
718 ATA16: SiS5511, SiS5513
719 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
720 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
721 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
724 If you say Y here, you need to say Y to "Use DMA by default when
727 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
729 config BLK_DEV_SL82C105
730 tristate "Winbond SL82c105 support"
731 depends on (PPC || ARM)
733 If you have a Winbond SL82c105 IDE controller, say Y here to enable
734 special configuration for this chip. This is common on various CHRP
735 motherboards, but could be used elsewhere. If in doubt, say Y.
737 config BLK_DEV_SLC90E66
738 tristate "SLC90E66 chipset support"
740 This driver ensures (U)DMA support for Victory66 SouthBridges for
741 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
742 The nice thing about it is that you can mix Ultra/DMA/PIO devices
743 and it will handle timing cycles. Since this is an improved
744 look-a-like to the PIIX4 it should be a nice addition.
746 If you say Y here, you need to say Y to "Use DMA by default when
749 Please read the comments at the top of
750 <file:drivers/ide/pci/slc90e66.c>.
752 config BLK_DEV_TRM290
753 tristate "Tekram TRM290 chipset support"
755 This driver adds support for bus master DMA transfers
756 using the Tekram TRM290 PCI IDE chip. Volunteers are
757 needed for further tweaking and development.
758 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
760 config BLK_DEV_VIA82CXXX
761 tristate "VIA82CXXX chipset support"
763 This driver adds explicit support for VIA BusMastering IDE chips.
764 This allows the kernel to change PIO, DMA and UDMA speeds and to
765 configure the chip to optimum performance.
767 config BLK_DEV_TC86C001
768 tristate "Toshiba TC86C001 support"
770 This driver adds support for Toshiba TC86C001 GOKU-S chip.
772 config BLK_DEV_CELLEB
773 tristate "Toshiba's Cell Reference Set IDE support"
774 depends on PPC_CELLEB
776 This driver provides support for the built-in IDE controller on
777 Toshiba Cell Reference Board.
782 config BLK_DEV_IDE_PMAC
783 bool "Builtin PowerMac IDE support"
784 depends on PPC_PMAC && IDE=y
786 This driver provides support for the built-in IDE controller on
787 most of the recent Apple Power Macintoshes and PowerBooks.
790 config BLK_DEV_IDE_PMAC_ATA100FIRST
791 bool "Probe internal ATA/100 (Kauai) first"
792 depends on BLK_DEV_IDE_PMAC
794 This option will cause the ATA/100 controller found in UniNorth2
795 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
796 to be probed before the ATA/66 and ATA/33 controllers. Without
797 these, those machine used to have the hard disk on hdc and the
798 CD-ROM on hda. This option changes this to more natural hda for
799 hard disk and hdc for CD-ROM.
801 config BLK_DEV_IDEDMA_PMAC
802 bool "PowerMac IDE DMA support"
803 depends on BLK_DEV_IDE_PMAC
804 select BLK_DEV_IDEDMA_PCI
806 This option allows the driver for the built-in IDE controller on
807 Power Macintoshes and PowerBooks to use DMA (direct memory access)
808 to transfer data to and from memory. Saying Y is safe and improves
811 config BLK_DEV_IDE_SWARM
812 tristate "IDE for Sibyte evaluation boards"
813 depends on SIBYTE_SB1xxx_SOC
815 config BLK_DEV_IDE_AU1XXX
816 bool "IDE for AMD Alchemy Au1200"
817 depends on SOC_AU1200
819 prompt "IDE Mode for AMD Alchemy Au1200"
820 default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA
821 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
823 config BLK_DEV_IDE_AU1XXX_PIO_DBDMA
824 bool "PIO+DbDMA IDE for AMD Alchemy Au1200"
826 config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
827 bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200"
828 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
831 config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ
832 int "Maximum transfer size (KB) per request (up to 128)"
834 depends on BLK_DEV_IDE_AU1XXX
837 def_bool ARM && (ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
840 config BLK_DEV_IDE_ICSIDE
841 tristate "ICS IDE interface support"
842 depends on ARM && ARCH_ACORN
844 On Acorn systems, say Y here if you wish to use the ICS IDE
845 interface card. This is not required for ICS partition support.
846 If you are unsure, say N to this.
848 config BLK_DEV_IDEDMA_ICS
849 bool "ICS DMA support"
850 depends on BLK_DEV_IDE_ICSIDE
852 Say Y here if you want to add DMA (Direct Memory Access) support to
855 config BLK_DEV_IDE_RAPIDE
856 tristate "RapIDE interface support"
857 depends on ARM && ARCH_ACORN
859 Say Y here if you want to support the Yellowstone RapIDE controller
860 manufactured for use with Acorn computers.
862 config BLK_DEV_IDE_BAST
863 tristate "Simtec BAST / Thorcom VR1000 IDE support"
864 depends on ARM && (ARCH_BAST || MACH_VR1000)
866 Say Y here if you want to support the onboard IDE channels on the
867 Simtec BAST or the Thorcom VR1000
870 bool "Amiga Gayle IDE interface support"
874 This is the IDE driver for the Amiga Gayle IDE interface. It supports
875 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
876 This includes builtin IDE interfaces on some Amiga models (A600,
877 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
878 bus (M-Tech E-Matrix 530 expansion card).
879 Say Y if you have an Amiga with a Gayle IDE interface and want to use
880 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
882 Note that you also have to enable Zorro bus support if you want to
883 use Gayle IDE interfaces on the Zorro expansion bus.
885 config BLK_DEV_IDEDOUBLER
886 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
887 depends on BLK_DEV_GAYLE && EXPERIMENTAL
889 This driver provides support for the so-called `IDE doublers' (made
890 by various manufacturers, e.g. Eyetech) that can be connected to the
891 builtin IDE interface of some Amiga models. Using such an IDE
892 doubler, you can connect up to four instead of two IDE devices on
893 the Amiga's builtin IDE interface.
895 Note that the normal Amiga Gayle IDE driver may not work correctly
896 if you have an IDE doubler and don't enable this driver!
898 Say Y if you have an IDE doubler. The driver is enabled at kernel
899 runtime using the "ide=doubler" kernel boot parameter.
901 config BLK_DEV_BUDDHA
902 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
903 depends on ZORRO && EXPERIMENTAL
906 This is the IDE driver for the IDE interfaces on the Buddha,
907 Catweasel and X-Surf expansion boards. It supports up to two interfaces
908 on the Buddha, three on the Catweasel and two on the X-Surf.
910 Say Y if you have a Buddha or Catweasel expansion board and want to
911 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
912 to one of its IDE interfaces.
914 config BLK_DEV_FALCON_IDE
915 bool "Falcon IDE interface support"
919 This is the IDE driver for the builtin IDE interface on the Atari
920 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
921 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
924 config BLK_DEV_MAC_IDE
925 bool "Macintosh Quadra/Powerbook IDE interface support"
929 This is the IDE driver for the builtin IDE interface on some m68k
930 Macintosh models. It supports both the `Quadra style' (used in
931 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
932 (used in the Powerbook 150 and 190 models) IDE interface.
934 Say Y if you have such an Macintosh model and want to use IDE
935 devices (hard disks, CD-ROM drives, etc.) that are connected to the
936 builtin IDE interface.
938 config BLK_DEV_Q40IDE
939 bool "Q40/Q60 IDE interface support"
943 Enable the on-board IDE controller in the Q40/Q60. This should
944 normally be on; disable it only if you are running a custom hard
945 drive subsystem through an expansion card.
947 config BLK_DEV_MPC8xx_IDE
948 bool "MPC8xx IDE support"
949 depends on 8xx && IDE=y && BLK_DEV_IDE=y
952 This option provides support for IDE on Motorola MPC8xx Systems.
953 Please see 'Type of MPC8xx IDE interface' for details.
958 prompt "Type of MPC8xx IDE interface"
959 depends on BLK_DEV_MPC8xx_IDE
960 default IDE_8xx_PCCARD
962 config IDE_8xx_PCCARD
965 Select how the IDE devices are connected to the MPC8xx system:
967 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
968 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
969 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
972 8xx_DIRECT is used for directly connected IDE devices using the 8xx
973 internal PCMCIA interface (example: IVMS8 systems)
975 EXT_DIRECT is used for IDE devices directly connected to the 8xx
976 bus using some glue logic, but _not_ the 8xx internal
977 PCMCIA interface (example: IDIF860 systems)
979 config IDE_8xx_DIRECT
982 config IDE_EXT_DIRECT
989 bool "Other IDE chipset support"
992 Say Y here if you want to include enhanced support for various IDE
993 interface chipsets used on motherboards and add-on cards. You can
994 then pick your particular IDE chip from among the following options.
995 This enhanced support may be necessary for Linux to be able to
996 access the 3rd/4th drives in some systems. It may also enable
997 setting of higher speed I/O rates to improve system performance with
998 these chipsets. Most of these also require special kernel boot
999 parameters to actually turn on the support at runtime; you can find
1000 a list of these in the file <file:Documentation/ide.txt>.
1002 People with SCSI-only systems can say N here.
1006 comment "Note: most of these also require special kernel boot parameters"
1008 config BLK_DEV_4DRIVES
1009 bool "Generic 4 drives/port support"
1011 Certain older chipsets, including the Tekram 690CD, use a single set
1012 of I/O ports at 0x1f0 to control up to four drives, instead of the
1013 customary two drives per port. Support for this can be enabled at
1014 runtime using the "ide0=four" kernel boot parameter if you say Y
1017 config BLK_DEV_ALI14XX
1018 tristate "ALI M14xx support"
1020 This driver is enabled at runtime using the "ali14xx.probe" kernel
1021 boot parameter. It enables support for the secondary IDE interface
1022 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1023 I/O speeds to be set as well. See the files
1024 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
1027 config BLK_DEV_DTC2278
1028 tristate "DTC-2278 support"
1030 This driver is enabled at runtime using the "dtc2278.probe" kernel
1031 boot parameter. It enables support for the secondary IDE interface
1032 of the DTC-2278 card, and permits faster I/O speeds to be set as
1033 well. See the <file:Documentation/ide.txt> and
1034 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1036 config BLK_DEV_HT6560B
1037 tristate "Holtek HT6560B support"
1039 This driver is enabled at runtime using the "ht6560b.probe" kernel
1040 boot parameter. It enables support for the secondary IDE interface
1041 of the Holtek card, and permits faster I/O speeds to be set as well.
1042 See the <file:Documentation/ide.txt> and
1043 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1045 config BLK_DEV_QD65XX
1046 tristate "QDI QD65xx support"
1048 This driver is enabled at runtime using the "qd65xx.probe" kernel
1049 boot parameter. It permits faster I/O speeds to be set. See the
1050 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
1053 config BLK_DEV_UMC8672
1054 tristate "UMC-8672 support"
1056 This driver is enabled at runtime using the "umc8672.probe" kernel
1057 boot parameter. It enables support for the secondary IDE interface
1058 of the UMC-8672, and permits faster I/O speeds to be set as well.
1059 See the files <file:Documentation/ide.txt> and
1060 <file:drivers/ide/legacy/umc8672.c> for more info.
1064 config BLK_DEV_IDEDMA
1065 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
1068 bool "IGNORE word93 Validation BITS"
1069 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1071 There are unclear terms in ATA-4 and ATA-5 standards how certain
1072 hardware (an 80c ribbon) should be detected. Different interpretations
1073 of the standards have been released in hardware. This causes problems:
1074 for example, a host with Ultra Mode 4 (or higher) will not run
1075 in that mode with an 80c ribbon.
1077 If you are experiencing compatibility or performance problems, you
1078 MAY try to answer Y here. However, it does not necessarily solve
1079 any of your problems, it could even cause more of them.
1081 It is normally safe to answer Y; however, the default is N.
1085 config BLK_DEV_HD_ONLY
1086 bool "Old hard disk (MFM/RLL/IDE) driver"
1087 depends on BLK_DEV_IDE=n
1089 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1090 the newer enhanced driver, but this old one is still around for two
1091 reasons. Some older systems have strange timing problems and seem to
1092 work only with the old driver (which itself does not work with some
1093 newer systems). The other reason is that the old driver is smaller,
1094 since it lacks the enhanced functionality of the new one. This makes
1095 it a good choice for systems with very tight memory restrictions, or
1096 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1097 driver can save 13 KB or so of kernel memory.
1099 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1100 instead of this one. For more detailed information, read the
1101 Disk-HOWTO, available from
1102 <http://www.tldp.org/docs.html#howto>.
1105 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY