2 # IDE ATA ATAPI Block device driver configuration
4 # Andre Hedrick <andre@linux-ide.org>
7 menu "ATA/ATAPI/MFM/RLL support"
10 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
60 This is the maximum number of IDE hardware interfaces that will
61 be supported by the driver. Make sure it is at least as high as
62 the number of IDE interfaces in your system.
65 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
67 If you say Y here, you will use the full-featured IDE driver to
68 control up to ten ATA/IDE interfaces, each being able to serve a
69 "master" and a "slave" device, for a total of up to twenty ATA/IDE
70 disk/cdrom/tape/floppy drives.
72 Useful information about large (>540 MB) IDE disks, multiple
73 interfaces, what to do if ATA/IDE devices are not automatically
74 detected, sound card ATA/IDE ports, module support, and other
75 topics, is contained in <file:Documentation/ide.txt>. For detailed
76 information about hard drives, consult the Disk-HOWTO and the
77 Multi-Disk-HOWTO, available from
78 <http://www.tldp.org/docs.html#howto>.
80 To fine-tune ATA/IDE drive/interface parameters for improved
81 performance, look for the hdparm package at
82 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
84 To compile this driver as a module, choose M here and read
85 <file:Documentation/ide.txt>. The module will be called ide-mod.
86 Do not compile this driver as a module if your root file system (the
87 one containing the directory /) is located on an IDE device.
89 If you have one or more IDE drives, say Y or M here. If your system
90 has no IDE drives, or if memory requirements are really tight, you
91 could say N here, and select the "Old hard disk driver" below
92 instead to save about 13 KB of memory in the kernel.
96 comment "Please see Documentation/ide.txt for help/info on IDE drives"
98 config BLK_DEV_IDE_SATA
99 bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
102 There are two drivers for Serial ATA controllers.
104 The main driver, "libata", exists inside the SCSI subsystem
105 and supports most modern SATA controllers.
107 The IDE driver (which you are currently configuring) supports
108 a few first-generation SATA controllers.
110 In order to eliminate conflicts between the two subsystems,
111 this config option enables the IDE driver's SATA support.
112 Normally this is disabled, as it is preferred that libata
113 supports SATA controllers, and this (IDE) driver supports
118 config BLK_DEV_HD_IDE
119 bool "Use old disk-only driver on primary interface"
120 depends on (X86 || SH_MPC1211)
122 There are two drivers for MFM/RLL/IDE disks. Most people use just
123 the new enhanced driver by itself. This option however installs the
124 old hard disk driver to control the primary IDE/disk interface in
125 the system, leaving the new enhanced IDE driver to take care of only
126 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
127 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
128 IDE interface. Choosing this option may be useful for older systems
129 which have MFM/RLL/ESDI controller+drives at the primary port
130 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
133 Normally, just say N here; you will then use the new driver for all
136 config BLK_DEV_IDEDISK
137 tristate "Include IDE/ATA-2 DISK support"
139 This will include enhanced support for MFM/RLL/IDE hard disks. If
140 you have a MFM/RLL/IDE disk, and there is no special reason to use
141 the old hard disk driver instead, say Y. If you have an SCSI-only
142 system, you can say N here.
144 To compile this driver as a module, choose M here: the
145 module will be called ide-disk.
146 Do not compile this driver as a module if your root file system
147 (the one containing the directory /) is located on the IDE disk.
151 config IDEDISK_MULTI_MODE
152 bool "Use multi-mode by default"
153 depends on BLK_DEV_IDEDISK
155 If you get this error, try to say Y here:
157 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
158 hda: set_multmode: error=0x04 { DriveStatusError }
163 tristate "PCMCIA IDE support"
166 Support for outboard IDE disks, tape drives, and CD-ROM drives
167 connected through a PCMCIA card.
170 tristate "Include IDE/ATAPI CDROM support"
172 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
173 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
174 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
175 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
176 double(2X) or better speed drives.
178 If you say Y here, the CD-ROM drive will be identified at boot time
179 along with other IDE devices, as "hdb" or "hdc", or something
180 similar (check the boot messages with dmesg). If this is your only
181 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
182 to say Y or M to "ISO 9660 CD-ROM file system support".
184 Note that older versions of LILO (LInux LOader) cannot properly deal
185 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
186 <http://lilo.go.dyndns.org/>.
188 To compile this driver as a module, choose M here: the
189 module will be called ide-cd.
191 config BLK_DEV_IDETAPE
192 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
193 depends on EXPERIMENTAL
195 If you have an IDE tape drive using the ATAPI protocol, say Y.
196 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
197 similar to the SCSI protocol. If you have an SCSI tape drive
198 however, you can say N here.
200 You should also say Y if you have an OnStream DI-30 tape drive; this
201 will not work with the SCSI protocol, until there is support for the
202 SC-30 and SC-50 versions.
204 If you say Y here, the tape drive will be identified at boot time
205 along with other IDE devices, as "hdb" or "hdc", or something
206 similar, and will be mapped to a character device such as "ht0"
207 (check the boot messages with dmesg). Be sure to consult the
208 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
209 for usage information.
211 To compile this driver as a module, choose M here: the
212 module will be called ide-tape.
214 config BLK_DEV_IDEFLOPPY
215 tristate "Include IDE/ATAPI FLOPPY support"
217 If you have an IDE floppy drive which uses the ATAPI protocol,
218 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
219 drives, similar to the SCSI protocol.
221 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
222 this driver. For information about jumper settings and the question
223 of when a ZIP drive uses a partition table, see
224 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
225 (ATAPI PD-CD/CDR drives are not supported by this driver; support
226 for PD-CD/CDR drives is available if you answer Y to
227 "SCSI emulation support", below).
229 If you say Y here, the FLOPPY drive will be identified along with
230 other IDE devices, as "hdb" or "hdc", or something similar (check
231 the boot messages with dmesg).
233 To compile this driver as a module, choose M here: the
234 module will be called ide-floppy.
236 config BLK_DEV_IDESCSI
237 tristate "SCSI emulation support"
240 WARNING: ide-scsi is no longer needed for cd writing applications!
241 The 2.6 kernel supports direct writing to ide-cd, which eliminates
242 the need for ide-scsi + the entire scsi stack just for writing a
243 cd. The new method is more efficient in every way.
245 This will provide SCSI host adapter emulation for IDE ATAPI devices,
246 and will allow you to use a SCSI device driver instead of a native
249 This is useful if you have an ATAPI device for which no native
250 driver has been written (for example, an ATAPI PD-CD drive);
251 you can then use this emulation together with an appropriate SCSI
252 device driver. In order to do this, say Y here and to "SCSI support"
253 and "SCSI generic support", below. You must then provide the kernel
254 command line "hdx=ide-scsi" (try "man bootparam" or see the
255 documentation of your boot loader (lilo or loadlin) about how to
256 pass options to the kernel at boot time) for devices if you want the
257 native EIDE sub-drivers to skip over the native support, so that
258 this SCSI emulation can be used instead.
260 Note that this option does NOT allow you to attach SCSI devices to a
261 box that doesn't have a SCSI host adapter installed.
263 If both this SCSI emulation and native ATAPI support are compiled
264 into the kernel, the native support will be used.
266 config IDE_TASK_IOCTL
267 bool "IDE Taskfile Access"
269 This is a direct raw access to the media. It is a complex but
270 elegant solution to test and validate the domain of the hardware and
271 perform below the driver data recover if needed. This is the most
272 basic form of media-forensics.
274 If you are unsure, say N here.
276 comment "IDE chipset support/bugfixes"
279 tristate "generic/default IDE chipset support"
284 config BLK_DEV_CMD640
285 bool "CMD640 chipset bugfix/support"
288 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
289 Pentium motherboards, usually in combination with a "Neptune" or
290 "SiS" chipset. Unfortunately, it has a number of rather nasty
291 design flaws that can cause severe data corruption under many common
292 conditions. Say Y here to include code which tries to automatically
293 detect and correct the problems under Linux. This option also
294 enables access to the secondary IDE ports in some CMD640 based
297 This driver will work automatically in PCI based systems (most new
298 systems have PCI slots). But if your system uses VESA local bus
299 (VLB) instead of PCI, you must also supply a kernel boot parameter
300 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
301 bootparam" or see the documentation of your boot loader about how to
302 pass options to the kernel.)
304 The CMD640 chip is also used on add-in cards by Acculogic, and on
305 the "CSA-6400E PCI to IDE controller" that some people have. For
306 details, read <file:Documentation/ide.txt>.
308 config BLK_DEV_CMD640_ENHANCED
309 bool "CMD640 enhanced support"
310 depends on BLK_DEV_CMD640
312 This option includes support for setting/autotuning PIO modes and
313 prefetch on CMD640 IDE interfaces. For details, read
314 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
315 and your BIOS does not already do this for you, then say Y here.
318 config BLK_DEV_IDEPNP
319 bool "PNP EIDE support"
322 If you have a PnP (Plug and Play) compatible EIDE card and
323 would like the kernel to automatically detect and activate
326 config BLK_DEV_IDEPCI
327 bool "PCI IDE chipset support" if PCI
328 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
330 Say Y here for PCI systems which use IDE drive(s).
331 This option helps the IDE driver to automatically detect and
332 configure all PCI-based IDE interfaces in your system.
334 config IDEPCI_SHARE_IRQ
335 bool "Sharing PCI IDE interrupts support"
336 depends on PCI && BLK_DEV_IDEPCI
338 Some ATA/IDE chipsets have hardware support which allows for
339 sharing a single IRQ with other cards. To enable support for
340 this in the ATA/IDE driver, say Y here.
342 It is safe to say Y to this question, in most cases.
345 config BLK_DEV_OFFBOARD
346 bool "Boot off-board chipsets first support"
347 depends on PCI && BLK_DEV_IDEPCI
349 Normally, IDE controllers built into the motherboard (on-board
350 controllers) are assigned to ide0 and ide1 while those on add-in PCI
351 cards (off-board controllers) are relegated to ide2 and ide3.
352 Answering Y here will allow you to reverse the situation, with
353 off-board controllers on ide0/1 and on-board controllers on ide2/3.
354 This can improve the usability of some boot managers such as lilo
355 when booting from a drive on an off-board controller.
357 If you say Y here, and you actually want to reverse the device scan
358 order as explained above, you also need to issue the kernel command
359 line option "ide=reverse". (Try "man bootparam" or see the
360 documentation of your boot loader (lilo or loadlin) about how to
361 pass options to the kernel at boot time.)
363 Note that, if you do this, the order of the hd* devices will be
364 rearranged which may require modification of fstab and other files.
368 config BLK_DEV_GENERIC
369 tristate "Generic PCI IDE Chipset Support"
370 depends on BLK_DEV_IDEPCI
372 config BLK_DEV_OPTI621
373 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
374 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
376 This is a driver for the OPTi 82C621 EIDE controller.
377 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
379 config BLK_DEV_RZ1000
380 tristate "RZ1000 chipset bugfix/support"
381 depends on PCI && BLK_DEV_IDEPCI && X86
383 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
384 Pentium motherboards, usually along with the "Neptune" chipset.
385 Unfortunately, it has a rather nasty design flaw that can cause
386 severe data corruption under many conditions. Say Y here to include
387 code which automatically detects and corrects the problem under
388 Linux. This may slow disk throughput by a few percent, but at least
389 things will operate 100% reliably.
391 config BLK_DEV_SL82C105
392 tristate "Winbond SL82c105 support"
393 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
395 If you have a Winbond SL82c105 IDE controller, say Y here to enable
396 special configuration for this chip. This is common on various CHRP
397 motherboards, but could be used elsewhere. If in doubt, say Y.
399 config BLK_DEV_IDEDMA_PCI
400 bool "Generic PCI bus-master DMA support"
401 depends on PCI && BLK_DEV_IDEPCI
403 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
404 is capable of bus-master DMA operation (most Pentium PCI systems),
405 you will want to say Y here to reduce CPU overhead. You can then use
406 the "hdparm" utility to enable DMA for drives for which it was not
407 enabled automatically. By default, DMA is not enabled automatically
408 for these drives, but you can change that by saying Y to the
409 following question "Use DMA by default when available". You can get
410 the latest version of the hdparm utility from
411 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
413 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
414 and the file <file:Documentation/ide.txt> for more information.
416 It is safe to say Y to this question.
418 if BLK_DEV_IDEDMA_PCI
420 config BLK_DEV_IDEDMA_FORCED
421 bool "Force enable legacy 2.0.X HOSTS to use DMA"
423 This is an old piece of lost code from Linux 2.0 Kernels.
425 Generally say N here.
427 config IDEDMA_PCI_AUTO
428 bool "Use PCI DMA by default when available"
430 Prior to kernel version 2.1.112, Linux used to automatically use
431 DMA for IDE drives and chipsets which support it. Due to concerns
432 about a couple of cases where buggy hardware may have caused damage,
433 the default is now to NOT use DMA automatically. To revert to the
434 previous behaviour, say Y to this question.
436 If you suspect your hardware is at all flakey, say N here.
437 Do NOT email the IDE kernel people regarding this issue!
439 It is normally safe to answer Y to this question unless your
440 motherboard uses a VIA VP2 chipset, in which case you should say N.
442 config IDEDMA_ONLYDISK
443 bool "Enable DMA only for disks "
444 depends on IDEDMA_PCI_AUTO
446 This is used if you know your ATAPI Devices are going to fail DMA
449 Generally say N here.
451 config BLK_DEV_AEC62XX
452 tristate "AEC62XX chipset support"
454 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
455 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
456 speeds and to configure the chip to optimum performance.
458 config BLK_DEV_ALI15X3
459 tristate "ALI M15x3 chipset support"
461 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
462 onboard chipsets. It also tests for Simplex mode and enables
463 normal dual channel support.
465 If you say Y here, you also need to say Y to "Use DMA by default
466 when available", above. Please read the comments at the top of
467 <file:drivers/ide/pci/alim15x3.c>.
472 bool "ALI M15x3 WDC support (DANGEROUS)"
473 depends on BLK_DEV_ALI15X3
475 This allows for UltraDMA support for WDC drives that ignore CRC
476 checking. You are a fool for enabling this option, but there have
477 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
478 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
481 Using this option can allow WDC drives to run at ATA-4/5 transfer
482 rates with only an ATA-2 support structure.
486 config BLK_DEV_AMD74XX
487 tristate "AMD and nVidia IDE support"
489 This driver adds explicit support for AMD-7xx and AMD-8111 chips
490 and also for the nVidia nForce chip. This allows the kernel to
491 change PIO, DMA and UDMA speeds and to configure the chip to
494 config BLK_DEV_ATIIXP
495 tristate "ATI IXP chipset IDE support"
498 This driver adds explicit support for ATI IXP chipset.
499 This allows the kernel to change PIO, DMA and UDMA speeds
500 and to configure the chip to optimum performance.
502 Say Y here if you have an ATI IXP chipset IDE controller.
504 config BLK_DEV_CMD64X
505 tristate "CMD64{3|6|8|9} chipset support"
507 Say Y here if you have an IDE controller which uses any of these
508 chipsets: CMD643, CMD646, or CMD648.
510 config BLK_DEV_TRIFLEX
511 tristate "Compaq Triflex IDE support"
513 Say Y here if you have a Compaq Triflex IDE controller, such
514 as those commonly found on Compaq Pentium-Pro systems
516 config BLK_DEV_CY82C693
517 tristate "CY82C693 chipset support"
519 This driver adds detection and support for the CY82C693 chipset
520 used on Digital's PC-Alpha 164SX boards.
522 If you say Y here, you need to say Y to "Use DMA by default
523 when available" as well.
525 config BLK_DEV_CS5520
526 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
527 depends on EXPERIMENTAL
529 Include support for PIO tuning an virtual DMA on the Cyrix MediaGX
530 5510/5520 chipset. This will automatically be detected and
533 It is safe to say Y to this question.
535 config BLK_DEV_CS5530
536 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
538 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
539 will automatically be detected and configured if found.
541 It is safe to say Y to this question.
543 config BLK_DEV_HPT34X
544 tristate "HPT34X chipset support"
546 This driver adds up to 4 more EIDE devices sharing a single
547 interrupt. The HPT343 chipset in its current form is a non-bootable
548 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
549 PCI UDMA controllers. This driver requires dynamic tuning of the
550 chipset during the ide-probe at boot time. It is reported to support
551 DVD II drives, by the manufacturer.
553 config HPT34X_AUTODMA
554 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
555 depends on BLK_DEV_HPT34X && EXPERIMENTAL
557 This is a dangerous thing to attempt currently! Please read the
558 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
559 here, then say Y to "Use DMA by default when available" as well.
563 config BLK_DEV_HPT366
564 tristate "HPT36X/37X chipset support"
566 HPT366 is an Ultra DMA chipset for ATA-66.
567 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
568 HPT370 is an Ultra DMA chipset for ATA-100.
569 HPT372 is an Ultra DMA chipset for ATA-100.
570 HPT374 is an Ultra DMA chipset for ATA-100.
572 This driver adds up to 4 more EIDE devices sharing a single
575 The HPT366 chipset in its current form is bootable. One solution
576 for this problem are special LILO commands for redirecting the
577 reference to device 0x80. The other solution is to say Y to "Boot
578 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
579 your mother board has the chipset natively mounted. Regardless one
580 should use the fore mentioned option and call at LILO or include
581 "ide=reverse" in LILO's append-line.
583 This driver requires dynamic tuning of the chipset during the
584 ide-probe at boot. It is reported to support DVD II drives, by the
587 config BLK_DEV_SC1200
588 tristate "National SCx200 chipset support"
590 This driver adds support for the built in IDE on the National
591 SCx200 series of embedded x86 "Geode" systems
594 tristate "Intel PIIXn chipsets support"
596 This driver adds explicit support for Intel PIIX and ICH chips
597 and also for the Efar Victory66 (slc90e66) chip. This allows
598 the kernel to change PIO, DMA and UDMA speeds and to configure
599 the chip to optimum performance.
601 config BLK_DEV_IT8172
602 bool "IT8172 IDE support"
603 depends on (MIPS_ITE8172 || MIPS_IVR)
605 Say Y here to support the on-board IDE controller on the Integrated
606 Technology Express, Inc. ITE8172 SBC. Vendor page at
607 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
608 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
610 config BLK_DEV_NS87415
611 tristate "NS87415 chipset support"
613 This driver adds detection and support for the NS87415 chip
614 (used in SPARC64, among others).
616 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
618 config BLK_DEV_PDC202XX_OLD
619 tristate "PROMISE PDC202{46|62|65|67} support"
621 Promise Ultra33 or PDC20246
622 Promise Ultra66 or PDC20262
623 Promise Ultra100 or PDC20265/PDC20267/PDC20268
625 This driver adds up to 4 more EIDE devices sharing a single
626 interrupt. This add-on card is a bootable PCI UDMA controller. Since
627 multiple cards can be installed and there are BIOS ROM problems that
628 happen if the BIOS revisions of all installed cards (three-max) do
629 not match, the driver attempts to do dynamic tuning of the chipset
630 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
631 for more than one card. This card may require that you say Y to
632 "Special UDMA Feature".
634 If you say Y here, you need to say Y to "Use DMA by default when
637 Please read the comments at the top of
638 <file:drivers/ide/pci/pdc202xx_old.c>.
642 config PDC202XX_BURST
643 bool "Special UDMA Feature"
644 depends on BLK_DEV_PDC202XX_OLD
646 This option causes the pdc202xx driver to enable UDMA modes on the
647 PDC202xx even when the PDC202xx BIOS has not done so.
649 It was originally designed for the PDC20246/Ultra33, whose BIOS will
650 only setup UDMA on the first two PDC20246 cards. It has also been
651 used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
652 when the PDC20265 BIOS has been disabled (for faster boot up).
654 Please read the comments at the top of
655 <file:drivers/ide/pci/pdc202xx_old.c>.
659 config BLK_DEV_PDC202XX_NEW
660 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
662 # FIXME - probably wants to be one for old and for new
663 config PDC202XX_FORCE
664 bool "Enable controller even if disabled by BIOS"
665 depends on BLK_DEV_PDC202XX_NEW
667 Enable the PDC202xx controller even if it has been disabled in the BIOS setup.
670 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
672 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
675 config BLK_DEV_SGIIOC4
676 tristate "Silicon Graphics IOC4 chipset support"
677 depends on IA64_SGI_SN2 || IA64_GENERIC
679 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
680 chipset, which has one channel and can support two devices.
681 Please say Y here if you have an Altix System from SGI.
683 config BLK_DEV_SIIMAGE
684 tristate "Silicon Image chipset support"
686 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
687 3112 (Serial ATA) chips.
689 config BLK_DEV_SIS5513
690 tristate "SiS5513 chipset support"
693 This driver ensures (U)DMA support for SIS5513 chipset family based
696 The following chipsets are supported:
697 ATA16: SiS5511, SiS5513
698 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
699 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
700 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
703 If you say Y here, you need to say Y to "Use DMA by default when
706 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
708 config BLK_DEV_SLC90E66
709 tristate "SLC90E66 chipset support"
711 This driver ensures (U)DMA support for Victroy66 SouthBridges for
712 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
713 The nice thing about it is that you can mix Ultra/DMA/PIO devices
714 and it will handle timing cycles. Since this is an improved
715 look-a-like to the PIIX4 it should be a nice addition.
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
721 <file:drivers/ide/pci/slc90e66.c>.
723 config BLK_DEV_TRM290
724 tristate "Tekram TRM290 chipset support"
726 This driver adds support for bus master DMA transfers
727 using the Tekram TRM290 PCI IDE chip. Volunteers are
728 needed for further tweaking and development.
729 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
731 config BLK_DEV_VIA82CXXX
732 tristate "VIA82CXXX chipset support"
734 This driver adds explicit support for VIA BusMastering IDE chips.
735 This allows the kernel to change PIO, DMA and UDMA speeds and to
736 configure the chip to optimum performance.
740 config BLK_DEV_IDE_PMAC
741 bool "Builtin PowerMac IDE support"
742 depends on PPC_PMAC && IDE=y
744 This driver provides support for the built-in IDE controller on
745 most of the recent Apple Power Macintoshes and PowerBooks.
748 config BLK_DEV_IDE_PMAC_ATA100FIRST
749 bool "Probe internal ATA/100 (Kauai) first"
750 depends on BLK_DEV_IDE_PMAC
752 This option will cause the ATA/100 controller found in UniNorth2
753 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
754 to be probed before the ATA/66 and ATA/33 controllers. Without
755 these, those machine used to have the hard disk on hdc and the
756 CD-ROM on hda. This option changes this to more natural hda for
757 hard disk and hdc for CD-ROM.
759 config BLK_DEV_IDEDMA_PMAC
760 bool "PowerMac IDE DMA support"
761 depends on BLK_DEV_IDE_PMAC
763 This option allows the driver for the built-in IDE controller on
764 Power Macintoshes and PowerBooks to use DMA (direct memory access)
765 to transfer data to and from memory. Saying Y is safe and improves
768 config BLK_DEV_IDE_PMAC_BLINK
769 bool "Blink laptop LED on drive activity"
770 depends on BLK_DEV_IDE_PMAC && ADB_PMU
772 This option enables the use of the sleep LED as a hard drive
776 def_bool ARM && (ARCH_A5K || ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
778 config BLK_DEV_IDE_ICSIDE
779 tristate "ICS IDE interface support"
780 depends on ARM && ARCH_ACORN
782 On Acorn systems, say Y here if you wish to use the ICS IDE
783 interface card. This is not required for ICS partition support.
784 If you are unsure, say N to this.
786 config BLK_DEV_IDEDMA_ICS
787 bool "ICS DMA support"
788 depends on BLK_DEV_IDE_ICSIDE
790 Say Y here if you want to add DMA (Direct Memory Access) support to
793 config IDEDMA_ICS_AUTO
794 bool "Use ICS DMA by default"
795 depends on BLK_DEV_IDEDMA_ICS
797 Prior to kernel version 2.1.112, Linux used to automatically use
798 DMA for IDE drives and chipsets which support it. Due to concerns
799 about a couple of cases where buggy hardware may have caused damage,
800 the default is now to NOT use DMA automatically. To revert to the
801 previous behaviour, say Y to this question.
803 If you suspect your hardware is at all flakey, say N here.
804 Do NOT email the IDE kernel people regarding this issue!
806 config BLK_DEV_IDE_RAPIDE
807 tristate "RapIDE interface support"
808 depends on ARM && ARCH_ACORN
810 Say Y here if you want to support the Yellowstone RapIDE controller
811 manufactured for use with Acorn computers.
813 config BLK_DEV_IDE_BAST
814 tristate "Simtec BAST / Thorcom VR1000 IDE support"
815 depends on ARM && (ARCH_BAST || MACH_VR1000)
817 Say Y here if you want to support the onboard IDE channels on the
818 Simtec BAST or the Thorcom VR1000
821 bool "Amiga Gayle IDE interface support"
824 This is the IDE driver for the Amiga Gayle IDE interface. It supports
825 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
826 This includes builtin IDE interfaces on some Amiga models (A600,
827 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
828 bus (M-Tech E-Matrix 530 expansion card).
829 Say Y if you have an Amiga with a Gayle IDE interface and want to use
830 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
832 Note that you also have to enable Zorro bus support if you want to
833 use Gayle IDE interfaces on the Zorro expansion bus.
835 config BLK_DEV_IDEDOUBLER
836 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
837 depends on BLK_DEV_GAYLE && EXPERIMENTAL
839 This driver provides support for the so-called `IDE doublers' (made
840 by various manufacturers, e.g. Eyetech) that can be connected to the
841 builtin IDE interface of some Amiga models. Using such an IDE
842 doubler, you can connect up to four instead of two IDE devices on
843 the Amiga's builtin IDE interface.
845 Note that the normal Amiga Gayle IDE driver may not work correctly
846 if you have an IDE doubler and don't enable this driver!
848 Say Y if you have an IDE doubler. The driver is enabled at kernel
849 runtime using the "ide=doubler" kernel boot parameter.
851 config BLK_DEV_BUDDHA
852 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
853 depends on ZORRO && EXPERIMENTAL
855 This is the IDE driver for the IDE interfaces on the Buddha,
856 Catweasel and X-Surf expansion boards. It supports up to two interfaces
857 on the Buddha, three on the Catweasel and two on the X-Surf.
859 Say Y if you have a Buddha or Catweasel expansion board and want to
860 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
861 to one of its IDE interfaces.
863 config BLK_DEV_FALCON_IDE
864 bool "Falcon IDE interface support"
867 This is the IDE driver for the builtin IDE interface on the Atari
868 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
869 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
872 config BLK_DEV_MAC_IDE
873 bool "Macintosh Quadra/Powerbook IDE interface support"
876 This is the IDE driver for the builtin IDE interface on some m68k
877 Macintosh models. It supports both the `Quadra style' (used in
878 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
879 (used in the Powerbook 150 and 190 models) IDE interface.
881 Say Y if you have such an Macintosh model and want to use IDE
882 devices (hard disks, CD-ROM drives, etc.) that are connected to the
883 builtin IDE interface.
885 config BLK_DEV_Q40IDE
886 bool "Q40/Q60 IDE interface support"
889 Enable the on-board IDE controller in the Q40/Q60. This should
890 normally be on; disable it only if you are running a custom hard
891 drive subsystem through an expansion card.
893 config BLK_DEV_MPC8xx_IDE
894 bool "MPC8xx IDE support"
897 This option provides support for IDE on Motorola MPC8xx Systems.
898 Please see 'Type of MPC8xx IDE interface' for details.
903 prompt "Type of MPC8xx IDE interface"
904 depends on BLK_DEV_MPC8xx_IDE
905 default IDE_8xx_PCCARD
907 config IDE_8xx_PCCARD
910 Select how the IDE devices are connected to the MPC8xx system:
912 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
913 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
914 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
917 8xx_DIRECT is used for directly connected IDE devices using the 8xx
918 internal PCMCIA interface (example: IVMS8 systems)
920 EXT_DIRECT is used for IDE devices directly connected to the 8xx
921 bus using some glue logic, but _not_ the 8xx internal
922 PCMCIA interface (example: IDIF860 systems)
924 config IDE_8xx_DIRECT
927 config IDE_EXT_DIRECT
934 bool "Other IDE chipset support"
937 Say Y here if you want to include enhanced support for various IDE
938 interface chipsets used on motherboards and add-on cards. You can
939 then pick your particular IDE chip from among the following options.
940 This enhanced support may be necessary for Linux to be able to
941 access the 3rd/4th drives in some systems. It may also enable
942 setting of higher speed I/O rates to improve system performance with
943 these chipsets. Most of these also require special kernel boot
944 parameters to actually turn on the support at runtime; you can find
945 a list of these in the file <file:Documentation/ide.txt>.
947 People with SCSI-only systems can say N here.
951 comment "Note: most of these also require special kernel boot parameters"
953 config BLK_DEV_4DRIVES
954 bool "Generic 4 drives/port support"
956 Certain older chipsets, including the Tekram 690CD, use a single set
957 of I/O ports at 0x1f0 to control up to four drives, instead of the
958 customary two drives per port. Support for this can be enabled at
959 runtime using the "ide0=four" kernel boot parameter if you say Y
962 config BLK_DEV_ALI14XX
963 tristate "ALI M14xx support"
965 This driver is enabled at runtime using the "ide0=ali14xx" kernel
966 boot parameter. It enables support for the secondary IDE interface
967 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
968 I/O speeds to be set as well. See the files
969 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
972 config BLK_DEV_DTC2278
973 tristate "DTC-2278 support"
975 This driver is enabled at runtime using the "ide0=dtc2278" kernel
976 boot parameter. It enables support for the secondary IDE interface
977 of the DTC-2278 card, and permits faster I/O speeds to be set as
978 well. See the <file:Documentation/ide.txt> and
979 <file:drivers/ide/legacy/dtc2278.c> files for more info.
981 config BLK_DEV_HT6560B
982 tristate "Holtek HT6560B support"
984 This driver is enabled at runtime using the "ide0=ht6560b" kernel
985 boot parameter. It enables support for the secondary IDE interface
986 of the Holtek card, and permits faster I/O speeds to be set as well.
987 See the <file:Documentation/ide.txt> and
988 <file:drivers/ide/legacy/ht6560b.c> files for more info.
990 config BLK_DEV_QD65XX
991 tristate "QDI QD65xx support"
993 This driver is enabled at runtime using the "ide0=qd65xx" kernel
994 boot parameter. It permits faster I/O speeds to be set. See the
995 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
998 config BLK_DEV_UMC8672
999 tristate "UMC-8672 support"
1001 This driver is enabled at runtime using the "ide0=umc8672" kernel
1002 boot parameter. It enables support for the secondary IDE interface
1003 of the UMC-8672, and permits faster I/O speeds to be set as well.
1004 See the files <file:Documentation/ide.txt> and
1005 <file:drivers/ide/legacy/umc8672.c> for more info.
1009 config BLK_DEV_IDEDMA
1010 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1013 bool "IGNORE word93 Validation BITS"
1014 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1016 There are unclear terms in ATA-4 and ATA-5 standards how certain
1017 hardware (an 80c ribbon) should be detected. Different interpretations
1018 of the standards have been released in hardware. This causes problems:
1019 for example, a host with Ultra Mode 4 (or higher) will not run
1020 in that mode with an 80c ribbon.
1022 If you are experiencing compatibility or performance problems, you
1023 MAY try to answering Y here. However, it does not necessarily solve
1024 any of your problems, it could even cause more of them.
1026 It is normally safe to answer Y; however, the default is N.
1029 def_bool IDEDMA_PCI_AUTO || IDEDMA_ICS_AUTO
1033 config BLK_DEV_HD_ONLY
1034 bool "Old hard disk (MFM/RLL/IDE) driver"
1035 depends on BLK_DEV_IDE=n
1037 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1038 the newer enhanced driver, but this old one is still around for two
1039 reasons. Some older systems have strange timing problems and seem to
1040 work only with the old driver (which itself does not work with some
1041 newer systems). The other reason is that the old driver is smaller,
1042 since it lacks the enhanced functionality of the new one. This makes
1043 it a good choice for systems with very tight memory restrictions, or
1044 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1045 driver can save 13 KB or so of kernel memory.
1047 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1048 instead of this one. For more detailed information, read the
1049 Disk-HOWTO, available from
1050 <http://www.tldp.org/docs.html#howto>.
1053 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY