2 # IDE ATA ATAPI Block device driver configuration
4 # Andre Hedrick <andre@linux-ide.org>
9 menu "ATA/ATAPI/MFM/RLL support"
12 tristate "ATA/ATAPI/MFM/RLL support"
14 If you say Y here, your kernel will be able to manage low cost mass
15 storage units such as ATA/(E)IDE and ATAPI units. The most common
16 cases are IDE hard drives and ATAPI CD-ROM drives.
18 If your system is pure SCSI and doesn't use these interfaces, you
21 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
22 for mass storage units such as hard disks. It was designed by
23 Western Digital and Compaq Computer in 1984. It was then named
24 ST506. Quite a number of disks use the IDE interface.
26 AT Attachment (ATA) is the superset of the IDE specifications.
27 ST506 was also called ATA-1.
29 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
30 ATA-3. It provides support for larger disks (up to 8.4GB by means of
31 the LBA standard), more disks (4 instead of 2) and for other mass
32 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
33 ATA-4 and provides faster (and more CPU friendly) transfer modes
34 than previous PIO (Programmed processor Input/Output) from previous
35 ATA/IDE standards by means of fast DMA controllers.
37 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
38 CD-ROM drives, similar in many respects to the SCSI protocol.
40 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
41 designed in order to prevent data corruption and disk crash by
42 detecting pre hardware failure conditions (heat, access time, and
43 the like...). Disks built since June 1995 may follow this standard.
44 The kernel itself doesn't manage this; however there are quite a
45 number of user programs such as smart that can query the status of
46 SMART parameters from disk drives.
48 To compile this driver as a module, choose M here: the
49 module will be called ide.
51 For further information, please read <file:Documentation/ide.txt>.
58 int "Max IDE interfaces"
59 depends on ALPHA || SUPERH || IA64 || EMBEDDED
62 This is the maximum number of IDE hardware interfaces that will
63 be supported by the driver. Make sure it is at least as high as
64 the number of IDE interfaces in your system.
67 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
69 If you say Y here, you will use the full-featured IDE driver to
70 control up to ten ATA/IDE interfaces, each being able to serve a
71 "master" and a "slave" device, for a total of up to twenty ATA/IDE
72 disk/cdrom/tape/floppy drives.
74 Useful information about large (>540 MB) IDE disks, multiple
75 interfaces, what to do if ATA/IDE devices are not automatically
76 detected, sound card ATA/IDE ports, module support, and other
77 topics, is contained in <file:Documentation/ide.txt>. For detailed
78 information about hard drives, consult the Disk-HOWTO and the
79 Multi-Disk-HOWTO, available from
80 <http://www.tldp.org/docs.html#howto>.
82 To fine-tune ATA/IDE drive/interface parameters for improved
83 performance, look for the hdparm package at
84 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
86 To compile this driver as a module, choose M here and read
87 <file:Documentation/ide.txt>. The module will be called ide-mod.
88 Do not compile this driver as a module if your root file system (the
89 one containing the directory /) is located on an IDE device.
91 If you have one or more IDE drives, say Y or M here. If your system
92 has no IDE drives, or if memory requirements are really tight, you
93 could say N here, and select the "Old hard disk driver" below
94 instead to save about 13 KB of memory in the kernel.
98 comment "Please see Documentation/ide.txt for help/info on IDE drives"
100 config BLK_DEV_IDE_SATA
101 bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
104 There are two drivers for Serial ATA controllers.
106 The main driver, "libata", exists inside the SCSI subsystem
107 and supports most modern SATA controllers.
109 The IDE driver (which you are currently configuring) supports
110 a few first-generation SATA controllers.
112 In order to eliminate conflicts between the two subsystems,
113 this config option enables the IDE driver's SATA support.
114 Normally this is disabled, as it is preferred that libata
115 supports SATA controllers, and this (IDE) driver supports
120 config BLK_DEV_HD_IDE
121 bool "Use old disk-only driver on primary interface"
122 depends on (X86 || SH_MPC1211)
124 There are two drivers for MFM/RLL/IDE disks. Most people use just
125 the new enhanced driver by itself. This option however installs the
126 old hard disk driver to control the primary IDE/disk interface in
127 the system, leaving the new enhanced IDE driver to take care of only
128 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
129 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
130 IDE interface. Choosing this option may be useful for older systems
131 which have MFM/RLL/ESDI controller+drives at the primary port
132 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
135 Normally, just say N here; you will then use the new driver for all
138 config BLK_DEV_IDEDISK
139 tristate "Include IDE/ATA-2 DISK support"
141 This will include enhanced support for MFM/RLL/IDE hard disks. If
142 you have a MFM/RLL/IDE disk, and there is no special reason to use
143 the old hard disk driver instead, say Y. If you have an SCSI-only
144 system, you can say N here.
146 To compile this driver as a module, choose M here: the
147 module will be called ide-disk.
148 Do not compile this driver as a module if your root file system
149 (the one containing the directory /) is located on the IDE disk.
153 config IDEDISK_MULTI_MODE
154 bool "Use multi-mode by default"
156 If you get this error, try to say Y here:
158 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
159 hda: set_multmode: error=0x04 { DriveStatusError }
164 tristate "PCMCIA IDE support"
167 Support for Compact Flash cards, outboard IDE disks, tape drives,
168 and CD-ROM drives connected through a PCMCIA card.
171 tristate "Include IDE/ATAPI CDROM support"
173 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
174 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
175 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
176 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
177 double(2X) or better speed drives.
179 If you say Y here, the CD-ROM drive will be identified at boot time
180 along with other IDE devices, as "hdb" or "hdc", or something
181 similar (check the boot messages with dmesg). If this is your only
182 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
183 to say Y or M to "ISO 9660 CD-ROM file system support".
185 Note that older versions of LILO (LInux LOader) cannot properly deal
186 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
187 <http://lilo.go.dyndns.org/>.
189 To compile this driver as a module, choose M here: the
190 module will be called ide-cd.
192 config BLK_DEV_IDETAPE
193 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
194 depends on EXPERIMENTAL
196 If you have an IDE tape drive using the ATAPI protocol, say Y.
197 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
198 similar to the SCSI protocol. If you have an SCSI tape drive
199 however, you can say N here.
201 You should also say Y if you have an OnStream DI-30 tape drive; this
202 will not work with the SCSI protocol, until there is support for the
203 SC-30 and SC-50 versions.
205 If you say Y here, the tape drive will be identified at boot time
206 along with other IDE devices, as "hdb" or "hdc", or something
207 similar, and will be mapped to a character device such as "ht0"
208 (check the boot messages with dmesg). Be sure to consult the
209 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
210 for usage information.
212 To compile this driver as a module, choose M here: the
213 module will be called ide-tape.
215 config BLK_DEV_IDEFLOPPY
216 tristate "Include IDE/ATAPI FLOPPY support"
218 If you have an IDE floppy drive which uses the ATAPI protocol,
219 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
220 drives, similar to the SCSI protocol.
222 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
223 this driver. For information about jumper settings and the question
224 of when a ZIP drive uses a partition table, see
225 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
226 (ATAPI PD-CD/CDR drives are not supported by this driver; support
227 for PD-CD/CDR drives is available if you answer Y to
228 "SCSI emulation support", below).
230 If you say Y here, the FLOPPY drive will be identified along with
231 other IDE devices, as "hdb" or "hdc", or something similar (check
232 the boot messages with dmesg).
234 To compile this driver as a module, choose M here: the
235 module will be called ide-floppy.
237 config BLK_DEV_IDESCSI
238 tristate "SCSI emulation support"
241 WARNING: ide-scsi is no longer needed for cd writing applications!
242 The 2.6 kernel supports direct writing to ide-cd, which eliminates
243 the need for ide-scsi + the entire scsi stack just for writing a
244 cd. The new method is more efficient in every way.
246 This will provide SCSI host adapter emulation for IDE ATAPI devices,
247 and will allow you to use a SCSI device driver instead of a native
250 This is useful if you have an ATAPI device for which no native
251 driver has been written (for example, an ATAPI PD-CD drive);
252 you can then use this emulation together with an appropriate SCSI
253 device driver. In order to do this, say Y here and to "SCSI support"
254 and "SCSI generic support", below. You must then provide the kernel
255 command line "hdx=ide-scsi" (try "man bootparam" or see the
256 documentation of your boot loader (lilo or loadlin) about how to
257 pass options to the kernel at boot time) for devices if you want the
258 native EIDE sub-drivers to skip over the native support, so that
259 this SCSI emulation can be used instead.
261 Note that this option does NOT allow you to attach SCSI devices to a
262 box that doesn't have a SCSI host adapter installed.
264 If both this SCSI emulation and native ATAPI support are compiled
265 into the kernel, the native support will be used.
267 config IDE_TASK_IOCTL
268 bool "IDE Taskfile Access"
270 This is a direct raw access to the media. It is a complex but
271 elegant solution to test and validate the domain of the hardware and
272 perform below the driver data recovery if needed. This is the most
273 basic form of media-forensics.
275 If you are unsure, say N here.
277 comment "IDE chipset support/bugfixes"
280 tristate "generic/default IDE chipset support"
285 config BLK_DEV_CMD640
286 bool "CMD640 chipset bugfix/support"
289 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
290 Pentium motherboards, usually in combination with a "Neptune" or
291 "SiS" chipset. Unfortunately, it has a number of rather nasty
292 design flaws that can cause severe data corruption under many common
293 conditions. Say Y here to include code which tries to automatically
294 detect and correct the problems under Linux. This option also
295 enables access to the secondary IDE ports in some CMD640 based
298 This driver will work automatically in PCI based systems (most new
299 systems have PCI slots). But if your system uses VESA local bus
300 (VLB) instead of PCI, you must also supply a kernel boot parameter
301 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
302 bootparam" or see the documentation of your boot loader about how to
303 pass options to the kernel.)
305 The CMD640 chip is also used on add-in cards by Acculogic, and on
306 the "CSA-6400E PCI to IDE controller" that some people have. For
307 details, read <file:Documentation/ide.txt>.
309 config BLK_DEV_CMD640_ENHANCED
310 bool "CMD640 enhanced support"
311 depends on BLK_DEV_CMD640
313 This option includes support for setting/autotuning PIO modes and
314 prefetch on CMD640 IDE interfaces. For details, read
315 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
316 and your BIOS does not already do this for you, then say Y here.
319 config BLK_DEV_IDEPNP
320 bool "PNP EIDE support"
323 If you have a PnP (Plug and Play) compatible EIDE card and
324 would like the kernel to automatically detect and activate
327 config BLK_DEV_IDEPCI
328 bool "PCI IDE chipset support" if PCI
329 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
331 Say Y here for PCI systems which use IDE drive(s).
332 This option helps the IDE driver to automatically detect and
333 configure all PCI-based IDE interfaces in your system.
335 config IDEPCI_SHARE_IRQ
336 bool "Sharing PCI IDE interrupts support"
337 depends on PCI && BLK_DEV_IDEPCI
339 Some ATA/IDE chipsets have hardware support which allows for
340 sharing a single IRQ with other cards. To enable support for
341 this in the ATA/IDE driver, say Y here.
343 It is safe to say Y to this question, in most cases.
346 config BLK_DEV_OFFBOARD
347 bool "Boot off-board chipsets first support"
348 depends on PCI && BLK_DEV_IDEPCI
350 Normally, IDE controllers built into the motherboard (on-board
351 controllers) are assigned to ide0 and ide1 while those on add-in PCI
352 cards (off-board controllers) are relegated to ide2 and ide3.
353 Answering Y here will allow you to reverse the situation, with
354 off-board controllers on ide0/1 and on-board controllers on ide2/3.
355 This can improve the usability of some boot managers such as lilo
356 when booting from a drive on an off-board controller.
358 If you say Y here, and you actually want to reverse the device scan
359 order as explained above, you also need to issue the kernel command
360 line option "ide=reverse". (Try "man bootparam" or see the
361 documentation of your boot loader (lilo or loadlin) about how to
362 pass options to the kernel at boot time.)
364 Note that, if you do this, the order of the hd* devices will be
365 rearranged which may require modification of fstab and other files.
369 config BLK_DEV_GENERIC
370 tristate "Generic PCI IDE Chipset Support"
371 depends on BLK_DEV_IDEPCI
373 config BLK_DEV_OPTI621
374 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
375 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
377 This is a driver for the OPTi 82C621 EIDE controller.
378 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
380 config BLK_DEV_RZ1000
381 tristate "RZ1000 chipset bugfix/support"
382 depends on PCI && BLK_DEV_IDEPCI && X86
384 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
385 Pentium motherboards, usually along with the "Neptune" chipset.
386 Unfortunately, it has a rather nasty design flaw that can cause
387 severe data corruption under many conditions. Say Y here to include
388 code which automatically detects and corrects the problem under
389 Linux. This may slow disk throughput by a few percent, but at least
390 things will operate 100% reliably.
392 config BLK_DEV_P20575
393 tristate "Promise P20575 PATA interface"
394 depends on PCI && BLK_DEV_IDEPCI
396 This driver is for the PATA interface of the Promise 20575
399 config BLK_DEV_SL82C105
400 tristate "Winbond SL82c105 support"
401 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
403 If you have a Winbond SL82c105 IDE controller, say Y here to enable
404 special configuration for this chip. This is common on various CHRP
405 motherboards, but could be used elsewhere. If in doubt, say Y.
407 config BLK_DEV_IDEDMA_PCI
408 bool "Generic PCI bus-master DMA support"
409 depends on PCI && BLK_DEV_IDEPCI
411 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
412 is capable of bus-master DMA operation (most Pentium PCI systems),
413 you will want to say Y here to reduce CPU overhead. You can then use
414 the "hdparm" utility to enable DMA for drives for which it was not
415 enabled automatically. By default, DMA is not enabled automatically
416 for these drives, but you can change that by saying Y to the
417 following question "Use DMA by default when available". You can get
418 the latest version of the hdparm utility from
419 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
421 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
422 and the file <file:Documentation/ide.txt> for more information.
424 It is safe to say Y to this question.
426 if BLK_DEV_IDEDMA_PCI
428 config BLK_DEV_IDEDMA_FORCED
429 bool "Force enable legacy 2.0.X HOSTS to use DMA"
431 This is an old piece of lost code from Linux 2.0 Kernels.
433 Generally say N here.
435 config IDEDMA_PCI_AUTO
436 bool "Use PCI DMA by default when available"
438 Prior to kernel version 2.1.112, Linux used to automatically use
439 DMA for IDE drives and chipsets which support it. Due to concerns
440 about a couple of cases where buggy hardware may have caused damage,
441 the default is now to NOT use DMA automatically. To revert to the
442 previous behaviour, say Y to this question.
444 If you suspect your hardware is at all flakey, say N here.
445 Do NOT email the IDE kernel people regarding this issue!
447 It is normally safe to answer Y to this question unless your
448 motherboard uses a VIA VP2 chipset, in which case you should say N.
450 config IDEDMA_ONLYDISK
451 bool "Enable DMA only for disks "
452 depends on IDEDMA_PCI_AUTO
454 This is used if you know your ATAPI Devices are going to fail DMA
457 Generally say N here.
459 config BLK_DEV_AEC62XX
460 tristate "AEC62XX chipset support"
462 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
463 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
464 speeds and to configure the chip to optimum performance.
466 config BLK_DEV_ALI15X3
467 tristate "ALI M15x3 chipset support"
469 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
470 onboard chipsets. It also tests for Simplex mode and enables
471 normal dual channel support.
473 If you say Y here, you also need to say Y to "Use DMA by default
474 when available", above. Please read the comments at the top of
475 <file:drivers/ide/pci/alim15x3.c>.
480 bool "ALI M15x3 WDC support (DANGEROUS)"
481 depends on BLK_DEV_ALI15X3
483 This allows for UltraDMA support for WDC drives that ignore CRC
484 checking. You are a fool for enabling this option, but there have
485 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
486 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
489 Using this option can allow WDC drives to run at ATA-4/5 transfer
490 rates with only an ATA-2 support structure.
494 config BLK_DEV_AMD74XX
495 tristate "AMD and nVidia IDE support"
497 This driver adds explicit support for AMD-7xx and AMD-8111 chips
498 and also for the nVidia nForce chip. This allows the kernel to
499 change PIO, DMA and UDMA speeds and to configure the chip to
502 config BLK_DEV_ATIIXP
503 tristate "ATI IXP chipset IDE support"
506 This driver adds explicit support for ATI IXP chipset.
507 This allows the kernel to change PIO, DMA and UDMA speeds
508 and to configure the chip to optimum performance.
510 Say Y here if you have an ATI IXP chipset IDE controller.
512 config BLK_DEV_CMD64X
513 tristate "CMD64{3|6|8|9} chipset support"
515 Say Y here if you have an IDE controller which uses any of these
516 chipsets: CMD643, CMD646, or CMD648.
518 config BLK_DEV_TRIFLEX
519 tristate "Compaq Triflex IDE support"
521 Say Y here if you have a Compaq Triflex IDE controller, such
522 as those commonly found on Compaq Pentium-Pro systems
524 config BLK_DEV_CY82C693
525 tristate "CY82C693 chipset support"
527 This driver adds detection and support for the CY82C693 chipset
528 used on Digital's PC-Alpha 164SX boards.
530 If you say Y here, you need to say Y to "Use DMA by default
531 when available" as well.
533 config BLK_DEV_CS5520
534 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
535 depends on EXPERIMENTAL
537 Include support for PIO tuning and virtual DMA on the Cyrix MediaGX
538 5510/5520 chipset. This will automatically be detected and
541 It is safe to say Y to this question.
543 config BLK_DEV_CS5530
544 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
546 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
547 will automatically be detected and configured if found.
549 It is safe to say Y to this question.
551 config BLK_DEV_CS5535
552 tristate "AMD CS5535 chipset support"
553 depends on X86 && !X86_64
555 Include support for UDMA on the NSC/AMD CS5535 companion chipset.
556 This will automatically be detected and configured if found.
558 It is safe to say Y to this question.
560 config BLK_DEV_HPT34X
561 tristate "HPT34X chipset support"
563 This driver adds up to 4 more EIDE devices sharing a single
564 interrupt. The HPT343 chipset in its current form is a non-bootable
565 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
566 PCI UDMA controllers. This driver requires dynamic tuning of the
567 chipset during the ide-probe at boot time. It is reported to support
568 DVD II drives, by the manufacturer.
570 config HPT34X_AUTODMA
571 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
572 depends on BLK_DEV_HPT34X && EXPERIMENTAL
574 This is a dangerous thing to attempt currently! Please read the
575 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
576 here, then say Y to "Use DMA by default when available" as well.
580 config BLK_DEV_HPT366
581 tristate "HPT36X/37X chipset support"
583 HPT366 is an Ultra DMA chipset for ATA-66.
584 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
585 HPT370 is an Ultra DMA chipset for ATA-100.
586 HPT372 is an Ultra DMA chipset for ATA-100.
587 HPT374 is an Ultra DMA chipset for ATA-100.
589 This driver adds up to 4 more EIDE devices sharing a single
592 The HPT366 chipset in its current form is bootable. One solution
593 for this problem are special LILO commands for redirecting the
594 reference to device 0x80. The other solution is to say Y to "Boot
595 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
596 your mother board has the chipset natively mounted. Regardless one
597 should use the fore mentioned option and call at LILO or include
598 "ide=reverse" in LILO's append-line.
600 This driver requires dynamic tuning of the chipset during the
601 ide-probe at boot. It is reported to support DVD II drives, by the
604 config BLK_DEV_JMICRON
605 tristate "JMicron JMB36x support"
607 Basic support for the JMicron ATA controllers. For full support
608 use the libata drivers.
610 config BLK_DEV_SC1200
611 tristate "National SCx200 chipset support"
613 This driver adds support for the built in IDE on the National
614 SCx200 series of embedded x86 "Geode" systems
617 tristate "Intel PIIXn chipsets support"
619 This driver adds explicit support for Intel PIIX and ICH chips
620 and also for the Efar Victory66 (slc90e66) chip. This allows
621 the kernel to change PIO, DMA and UDMA speeds and to configure
622 the chip to optimum performance.
624 config BLK_DEV_IT821X
625 tristate "IT821X IDE support"
627 This driver adds support for the ITE 8211 IDE controller and the
628 IT 8212 IDE RAID controller in both RAID and pass-through mode.
630 config BLK_DEV_NS87415
631 tristate "NS87415 chipset support"
633 This driver adds detection and support for the NS87415 chip
634 (used mainly on SPARC64 and PA-RISC machines).
636 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
638 config BLK_DEV_PDC202XX_OLD
639 tristate "PROMISE PDC202{46|62|65|67} support"
641 Promise Ultra33 or PDC20246
642 Promise Ultra66 or PDC20262
643 Promise Ultra100 or PDC20265/PDC20267/PDC20268
645 This driver adds up to 4 more EIDE devices sharing a single
646 interrupt. This add-on card is a bootable PCI UDMA controller. Since
647 multiple cards can be installed and there are BIOS ROM problems that
648 happen if the BIOS revisions of all installed cards (three-max) do
649 not match, the driver attempts to do dynamic tuning of the chipset
650 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
651 for more than one card. This card may require that you say Y to
652 "Special UDMA Feature".
654 If you say Y here, you need to say Y to "Use DMA by default when
657 Please read the comments at the top of
658 <file:drivers/ide/pci/pdc202xx_old.c>.
662 config PDC202XX_BURST
663 bool "Special UDMA Feature"
664 depends on BLK_DEV_PDC202XX_OLD
666 This option causes the pdc202xx driver to enable UDMA modes on the
667 PDC202xx even when the PDC202xx BIOS has not done so.
669 It was originally designed for the PDC20246/Ultra33, whose BIOS will
670 only setup UDMA on the first two PDC20246 cards. It has also been
671 used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
672 when the PDC20265 BIOS has been disabled (for faster boot up).
674 Please read the comments at the top of
675 <file:drivers/ide/pci/pdc202xx_old.c>.
679 config BLK_DEV_PDC202XX_NEW
680 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
683 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
685 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
688 config BLK_DEV_SGIIOC4
689 tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support"
690 depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4
691 select IDEPCI_SHARE_IRQ
693 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
694 chipset, which has one channel and can support two devices.
695 Please say Y here if you have an Altix System from SGI.
697 config BLK_DEV_SIIMAGE
698 tristate "Silicon Image chipset support"
700 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
701 3112 (Serial ATA) chips.
703 config BLK_DEV_SIS5513
704 tristate "SiS5513 chipset support"
707 This driver ensures (U)DMA support for SIS5513 chipset family based
710 The following chipsets are supported:
711 ATA16: SiS5511, SiS5513
712 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
713 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
714 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
717 If you say Y here, you need to say Y to "Use DMA by default when
720 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
722 config BLK_DEV_SLC90E66
723 tristate "SLC90E66 chipset support"
725 This driver ensures (U)DMA support for Victory66 SouthBridges for
726 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
727 The nice thing about it is that you can mix Ultra/DMA/PIO devices
728 and it will handle timing cycles. Since this is an improved
729 look-a-like to the PIIX4 it should be a nice addition.
731 If you say Y here, you need to say Y to "Use DMA by default when
734 Please read the comments at the top of
735 <file:drivers/ide/pci/slc90e66.c>.
737 config BLK_DEV_TRM290
738 tristate "Tekram TRM290 chipset support"
740 This driver adds support for bus master DMA transfers
741 using the Tekram TRM290 PCI IDE chip. Volunteers are
742 needed for further tweaking and development.
743 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
745 config BLK_DEV_VIA82CXXX
746 tristate "VIA82CXXX chipset support"
748 This driver adds explicit support for VIA BusMastering IDE chips.
749 This allows the kernel to change PIO, DMA and UDMA speeds and to
750 configure the chip to optimum performance.
754 config BLK_DEV_IDE_PMAC
755 bool "Builtin PowerMac IDE support"
756 depends on PPC_PMAC && IDE=y
758 This driver provides support for the built-in IDE controller on
759 most of the recent Apple Power Macintoshes and PowerBooks.
762 config BLK_DEV_IDE_PMAC_ATA100FIRST
763 bool "Probe internal ATA/100 (Kauai) first"
764 depends on BLK_DEV_IDE_PMAC
766 This option will cause the ATA/100 controller found in UniNorth2
767 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
768 to be probed before the ATA/66 and ATA/33 controllers. Without
769 these, those machine used to have the hard disk on hdc and the
770 CD-ROM on hda. This option changes this to more natural hda for
771 hard disk and hdc for CD-ROM.
773 config BLK_DEV_IDEDMA_PMAC
774 bool "PowerMac IDE DMA support"
775 depends on BLK_DEV_IDE_PMAC
776 select BLK_DEV_IDEDMA_PCI
778 This option allows the driver for the built-in IDE controller on
779 Power Macintoshes and PowerBooks to use DMA (direct memory access)
780 to transfer data to and from memory. Saying Y is safe and improves
783 config BLK_DEV_IDE_SWARM
784 tristate "IDE for Sibyte evaluation boards"
785 depends on SIBYTE_SB1xxx_SOC
787 config BLK_DEV_IDE_AU1XXX
788 bool "IDE for AMD Alchemy Au1200"
789 depends on SOC_AU1200
791 prompt "IDE Mode for AMD Alchemy Au1200"
792 default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA
793 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
795 config BLK_DEV_IDE_AU1XXX_PIO_DBDMA
796 bool "PIO+DbDMA IDE for AMD Alchemy Au1200"
798 config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
799 bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200"
800 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
803 config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ
804 int "Maximum transfer size (KB) per request (up to 128)"
806 depends BLK_DEV_IDE_AU1XXX
809 def_bool ARM && (ARCH_A5K || ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
811 config BLK_DEV_IDE_ICSIDE
812 tristate "ICS IDE interface support"
813 depends on ARM && ARCH_ACORN
815 On Acorn systems, say Y here if you wish to use the ICS IDE
816 interface card. This is not required for ICS partition support.
817 If you are unsure, say N to this.
819 config BLK_DEV_IDEDMA_ICS
820 bool "ICS DMA support"
821 depends on BLK_DEV_IDE_ICSIDE
823 Say Y here if you want to add DMA (Direct Memory Access) support to
826 config IDEDMA_ICS_AUTO
827 bool "Use ICS DMA by default"
828 depends on BLK_DEV_IDEDMA_ICS
830 Prior to kernel version 2.1.112, Linux used to automatically use
831 DMA for IDE drives and chipsets which support it. Due to concerns
832 about a couple of cases where buggy hardware may have caused damage,
833 the default is now to NOT use DMA automatically. To revert to the
834 previous behaviour, say Y to this question.
836 If you suspect your hardware is at all flakey, say N here.
837 Do NOT email the IDE kernel people regarding this issue!
839 config BLK_DEV_IDE_RAPIDE
840 tristate "RapIDE interface support"
841 depends on ARM && ARCH_ACORN
843 Say Y here if you want to support the Yellowstone RapIDE controller
844 manufactured for use with Acorn computers.
846 config BLK_DEV_IDE_BAST
847 tristate "Simtec BAST / Thorcom VR1000 IDE support"
848 depends on ARM && (ARCH_BAST || MACH_VR1000)
850 Say Y here if you want to support the onboard IDE channels on the
851 Simtec BAST or the Thorcom VR1000
854 bool "Amiga Gayle IDE interface support"
857 This is the IDE driver for the Amiga Gayle IDE interface. It supports
858 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
859 This includes builtin IDE interfaces on some Amiga models (A600,
860 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
861 bus (M-Tech E-Matrix 530 expansion card).
862 Say Y if you have an Amiga with a Gayle IDE interface and want to use
863 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
865 Note that you also have to enable Zorro bus support if you want to
866 use Gayle IDE interfaces on the Zorro expansion bus.
868 config BLK_DEV_IDEDOUBLER
869 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
870 depends on BLK_DEV_GAYLE && EXPERIMENTAL
872 This driver provides support for the so-called `IDE doublers' (made
873 by various manufacturers, e.g. Eyetech) that can be connected to the
874 builtin IDE interface of some Amiga models. Using such an IDE
875 doubler, you can connect up to four instead of two IDE devices on
876 the Amiga's builtin IDE interface.
878 Note that the normal Amiga Gayle IDE driver may not work correctly
879 if you have an IDE doubler and don't enable this driver!
881 Say Y if you have an IDE doubler. The driver is enabled at kernel
882 runtime using the "ide=doubler" kernel boot parameter.
884 config BLK_DEV_BUDDHA
885 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
886 depends on ZORRO && EXPERIMENTAL
888 This is the IDE driver for the IDE interfaces on the Buddha,
889 Catweasel and X-Surf expansion boards. It supports up to two interfaces
890 on the Buddha, three on the Catweasel and two on the X-Surf.
892 Say Y if you have a Buddha or Catweasel expansion board and want to
893 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
894 to one of its IDE interfaces.
896 config BLK_DEV_FALCON_IDE
897 bool "Falcon IDE interface support"
900 This is the IDE driver for the builtin IDE interface on the Atari
901 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
902 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
905 config BLK_DEV_MAC_IDE
906 bool "Macintosh Quadra/Powerbook IDE interface support"
909 This is the IDE driver for the builtin IDE interface on some m68k
910 Macintosh models. It supports both the `Quadra style' (used in
911 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
912 (used in the Powerbook 150 and 190 models) IDE interface.
914 Say Y if you have such an Macintosh model and want to use IDE
915 devices (hard disks, CD-ROM drives, etc.) that are connected to the
916 builtin IDE interface.
918 config BLK_DEV_Q40IDE
919 bool "Q40/Q60 IDE interface support"
922 Enable the on-board IDE controller in the Q40/Q60. This should
923 normally be on; disable it only if you are running a custom hard
924 drive subsystem through an expansion card.
926 config BLK_DEV_MPC8xx_IDE
927 bool "MPC8xx IDE support"
928 depends on 8xx && IDE=y && BLK_DEV_IDE=y
930 This option provides support for IDE on Motorola MPC8xx Systems.
931 Please see 'Type of MPC8xx IDE interface' for details.
936 prompt "Type of MPC8xx IDE interface"
937 depends on BLK_DEV_MPC8xx_IDE
938 default IDE_8xx_PCCARD
940 config IDE_8xx_PCCARD
943 Select how the IDE devices are connected to the MPC8xx system:
945 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
946 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
947 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
950 8xx_DIRECT is used for directly connected IDE devices using the 8xx
951 internal PCMCIA interface (example: IVMS8 systems)
953 EXT_DIRECT is used for IDE devices directly connected to the 8xx
954 bus using some glue logic, but _not_ the 8xx internal
955 PCMCIA interface (example: IDIF860 systems)
957 config IDE_8xx_DIRECT
960 config IDE_EXT_DIRECT
967 bool "Other IDE chipset support"
970 Say Y here if you want to include enhanced support for various IDE
971 interface chipsets used on motherboards and add-on cards. You can
972 then pick your particular IDE chip from among the following options.
973 This enhanced support may be necessary for Linux to be able to
974 access the 3rd/4th drives in some systems. It may also enable
975 setting of higher speed I/O rates to improve system performance with
976 these chipsets. Most of these also require special kernel boot
977 parameters to actually turn on the support at runtime; you can find
978 a list of these in the file <file:Documentation/ide.txt>.
980 People with SCSI-only systems can say N here.
984 comment "Note: most of these also require special kernel boot parameters"
986 config BLK_DEV_4DRIVES
987 bool "Generic 4 drives/port support"
989 Certain older chipsets, including the Tekram 690CD, use a single set
990 of I/O ports at 0x1f0 to control up to four drives, instead of the
991 customary two drives per port. Support for this can be enabled at
992 runtime using the "ide0=four" kernel boot parameter if you say Y
995 config BLK_DEV_ALI14XX
996 tristate "ALI M14xx support"
998 This driver is enabled at runtime using the "ide0=ali14xx" kernel
999 boot parameter. It enables support for the secondary IDE interface
1000 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1001 I/O speeds to be set as well. See the files
1002 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
1005 config BLK_DEV_DTC2278
1006 tristate "DTC-2278 support"
1008 This driver is enabled at runtime using the "ide0=dtc2278" kernel
1009 boot parameter. It enables support for the secondary IDE interface
1010 of the DTC-2278 card, and permits faster I/O speeds to be set as
1011 well. See the <file:Documentation/ide.txt> and
1012 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1014 config BLK_DEV_HT6560B
1015 tristate "Holtek HT6560B support"
1017 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1018 boot parameter. It enables support for the secondary IDE interface
1019 of the Holtek card, and permits faster I/O speeds to be set as well.
1020 See the <file:Documentation/ide.txt> and
1021 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1023 config BLK_DEV_QD65XX
1024 tristate "QDI QD65xx support"
1026 This driver is enabled at runtime using the "ide0=qd65xx" kernel
1027 boot parameter. It permits faster I/O speeds to be set. See the
1028 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
1031 config BLK_DEV_UMC8672
1032 tristate "UMC-8672 support"
1034 This driver is enabled at runtime using the "ide0=umc8672" kernel
1035 boot parameter. It enables support for the secondary IDE interface
1036 of the UMC-8672, and permits faster I/O speeds to be set as well.
1037 See the files <file:Documentation/ide.txt> and
1038 <file:drivers/ide/legacy/umc8672.c> for more info.
1042 config BLK_DEV_IDEDMA
1043 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
1046 bool "IGNORE word93 Validation BITS"
1047 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1049 There are unclear terms in ATA-4 and ATA-5 standards how certain
1050 hardware (an 80c ribbon) should be detected. Different interpretations
1051 of the standards have been released in hardware. This causes problems:
1052 for example, a host with Ultra Mode 4 (or higher) will not run
1053 in that mode with an 80c ribbon.
1055 If you are experiencing compatibility or performance problems, you
1056 MAY try to answer Y here. However, it does not necessarily solve
1057 any of your problems, it could even cause more of them.
1059 It is normally safe to answer Y; however, the default is N.
1062 def_bool IDEDMA_PCI_AUTO || IDEDMA_ICS_AUTO
1066 config BLK_DEV_HD_ONLY
1067 bool "Old hard disk (MFM/RLL/IDE) driver"
1068 depends on BLK_DEV_IDE=n
1070 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1071 the newer enhanced driver, but this old one is still around for two
1072 reasons. Some older systems have strange timing problems and seem to
1073 work only with the old driver (which itself does not work with some
1074 newer systems). The other reason is that the old driver is smaller,
1075 since it lacks the enhanced functionality of the new one. This makes
1076 it a good choice for systems with very tight memory restrictions, or
1077 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1078 driver can save 13 KB or so of kernel memory.
1080 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1081 instead of this one. For more detailed information, read the
1082 Disk-HOWTO, available from
1083 <http://www.tldp.org/docs.html#howto>.
1086 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY