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 config IDE_TASKFILE_IO
277 bool 'IDE Taskfile IO (EXPERIMENTAL)'
278 depends on EXPERIMENTAL
281 Use new taskfile IO code.
283 It is safe to say Y to this question, in most cases.
285 comment "IDE chipset support/bugfixes"
288 tristate "generic/default IDE chipset support"
293 config BLK_DEV_CMD640
294 bool "CMD640 chipset bugfix/support"
297 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
298 Pentium motherboards, usually in combination with a "Neptune" or
299 "SiS" chipset. Unfortunately, it has a number of rather nasty
300 design flaws that can cause severe data corruption under many common
301 conditions. Say Y here to include code which tries to automatically
302 detect and correct the problems under Linux. This option also
303 enables access to the secondary IDE ports in some CMD640 based
306 This driver will work automatically in PCI based systems (most new
307 systems have PCI slots). But if your system uses VESA local bus
308 (VLB) instead of PCI, you must also supply a kernel boot parameter
309 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
310 bootparam" or see the documentation of your boot loader about how to
311 pass options to the kernel.)
313 The CMD640 chip is also used on add-in cards by Acculogic, and on
314 the "CSA-6400E PCI to IDE controller" that some people have. For
315 details, read <file:Documentation/ide.txt>.
317 config BLK_DEV_CMD640_ENHANCED
318 bool "CMD640 enhanced support"
319 depends on BLK_DEV_CMD640
321 This option includes support for setting/autotuning PIO modes and
322 prefetch on CMD640 IDE interfaces. For details, read
323 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
324 and your BIOS does not already do this for you, then say Y here.
327 config BLK_DEV_IDEPNP
328 bool "PNP EIDE support"
331 If you have a PnP (Plug and Play) compatible EIDE card and
332 would like the kernel to automatically detect and activate
335 config BLK_DEV_IDEPCI
336 bool "PCI IDE chipset support" if PCI
337 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
339 Say Y here for PCI systems which use IDE drive(s).
340 This option helps the IDE driver to automatically detect and
341 configure all PCI-based IDE interfaces in your system.
343 config IDEPCI_SHARE_IRQ
344 bool "Sharing PCI IDE interrupts support"
345 depends on PCI && BLK_DEV_IDEPCI
347 Some ATA/IDE chipsets have hardware support which allows for
348 sharing a single IRQ with other cards. To enable support for
349 this in the ATA/IDE driver, say Y here.
351 It is safe to say Y to this question, in most cases.
354 config BLK_DEV_OFFBOARD
355 bool "Boot off-board chipsets first support"
356 depends on PCI && BLK_DEV_IDEPCI
358 Normally, IDE controllers built into the motherboard (on-board
359 controllers) are assigned to ide0 and ide1 while those on add-in PCI
360 cards (off-board controllers) are relegated to ide2 and ide3.
361 Answering Y here will allow you to reverse the situation, with
362 off-board controllers on ide0/1 and on-board controllers on ide2/3.
363 This can improve the usability of some boot managers such as lilo
364 when booting from a drive on an off-board controller.
366 If you say Y here, and you actually want to reverse the device scan
367 order as explained above, you also need to issue the kernel command
368 line option "ide=reverse". (Try "man bootparam" or see the
369 documentation of your boot loader (lilo or loadlin) about how to
370 pass options to the kernel at boot time.)
372 Note that, if you do this, the order of the hd* devices will be
373 rearranged which may require modification of fstab and other files.
377 config BLK_DEV_GENERIC
378 tristate "Generic PCI IDE Chipset Support"
379 depends on BLK_DEV_IDEPCI
381 config BLK_DEV_OPTI621
382 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
383 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
385 This is a driver for the OPTi 82C621 EIDE controller.
386 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
388 config BLK_DEV_RZ1000
389 tristate "RZ1000 chipset bugfix/support"
390 depends on PCI && BLK_DEV_IDEPCI && X86
392 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
393 Pentium motherboards, usually along with the "Neptune" chipset.
394 Unfortunately, it has a rather nasty design flaw that can cause
395 severe data corruption under many conditions. Say Y here to include
396 code which automatically detects and corrects the problem under
397 Linux. This may slow disk throughput by a few percent, but at least
398 things will operate 100% reliably.
400 config BLK_DEV_SL82C105
401 tristate "Winbond SL82c105 support"
402 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
404 If you have a Winbond SL82c105 IDE controller, say Y here to enable
405 special configuration for this chip. This is common on various CHRP
406 motherboards, but could be used elsewhere. If in doubt, say Y.
408 config BLK_DEV_IDEDMA_PCI
409 bool "Generic PCI bus-master DMA support"
410 depends on PCI && BLK_DEV_IDEPCI
412 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
413 is capable of bus-master DMA operation (most Pentium PCI systems),
414 you will want to say Y here to reduce CPU overhead. You can then use
415 the "hdparm" utility to enable DMA for drives for which it was not
416 enabled automatically. By default, DMA is not enabled automatically
417 for these drives, but you can change that by saying Y to the
418 following question "Use DMA by default when available". You can get
419 the latest version of the hdparm utility from
420 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
422 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
423 and the file <file:Documentation/ide.txt> for more information.
425 It is safe to say Y to this question.
427 if BLK_DEV_IDEDMA_PCI
429 config BLK_DEV_IDEDMA_FORCED
430 bool "Force enable legacy 2.0.X HOSTS to use DMA"
432 This is an old piece of lost code from Linux 2.0 Kernels.
434 Generally say N here.
436 config IDEDMA_PCI_AUTO
437 bool "Use PCI DMA by default when available"
439 Prior to kernel version 2.1.112, Linux used to automatically use
440 DMA for IDE drives and chipsets which support it. Due to concerns
441 about a couple of cases where buggy hardware may have caused damage,
442 the default is now to NOT use DMA automatically. To revert to the
443 previous behaviour, say Y to this question.
445 If you suspect your hardware is at all flakey, say N here.
446 Do NOT email the IDE kernel people regarding this issue!
448 It is normally safe to answer Y to this question unless your
449 motherboard uses a VIA VP2 chipset, in which case you should say N.
451 config IDEDMA_ONLYDISK
452 bool "Enable DMA only for disks "
453 depends on IDEDMA_PCI_AUTO
455 This is used if you know your ATAPI Devices are going to fail DMA
458 Generally say N here.
460 config BLK_DEV_AEC62XX
461 tristate "AEC62XX chipset support"
463 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
464 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
465 speeds and to configure the chip to optimum performance.
467 config BLK_DEV_ALI15X3
468 tristate "ALI M15x3 chipset support"
470 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
471 onboard chipsets. It also tests for Simplex mode and enables
472 normal dual channel support.
474 If you say Y here, you also need to say Y to "Use DMA by default
475 when available", above. Please read the comments at the top of
476 <file:drivers/ide/pci/alim15x3.c>.
481 bool "ALI M15x3 WDC support (DANGEROUS)"
482 depends on BLK_DEV_ALI15X3
484 This allows for UltraDMA support for WDC drives that ignore CRC
485 checking. You are a fool for enabling this option, but there have
486 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
487 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
490 Using this option can allow WDC drives to run at ATA-4/5 transfer
491 rates with only an ATA-2 support structure.
495 config BLK_DEV_AMD74XX
496 tristate "AMD and nVidia IDE support"
498 This driver adds explicit support for AMD-7xx and AMD-8111 chips
499 and also for the nVidia nForce chip. This allows the kernel to
500 change PIO, DMA and UDMA speeds and to configure the chip to
503 config BLK_DEV_ATIIXP
504 tristate "ATI IXP chipset IDE support"
507 This driver adds explicit support for ATI IXP chipset.
508 This allows the kernel to change PIO, DMA and UDMA speeds
509 and to configure the chip to optimum performance.
511 Say Y here if you have an ATI IXP chipset IDE controller.
513 config BLK_DEV_CMD64X
514 tristate "CMD64{3|6|8|9} chipset support"
516 Say Y here if you have an IDE controller which uses any of these
517 chipsets: CMD643, CMD646, or CMD648.
519 config BLK_DEV_TRIFLEX
520 tristate "Compaq Triflex IDE support"
522 Say Y here if you have a Compaq Triflex IDE controller, such
523 as those commonly found on Compaq Pentium-Pro systems
525 config BLK_DEV_CY82C693
526 tristate "CY82C693 chipset support"
528 This driver adds detection and support for the CY82C693 chipset
529 used on Digital's PC-Alpha 164SX boards.
531 If you say Y here, you need to say Y to "Use DMA by default
532 when available" as well.
534 config BLK_DEV_CS5520
535 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
536 depends on EXPERIMENTAL
538 Include support for PIO tuning an virtual DMA on the Cyrix MediaGX
539 5510/5520 chipset. This will automatically be detected and
542 It is safe to say Y to this question.
544 config BLK_DEV_CS5530
545 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
547 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
548 will automatically be detected and configured if found.
550 It is safe to say Y to this question.
552 config BLK_DEV_HPT34X
553 tristate "HPT34X chipset support"
555 This driver adds up to 4 more EIDE devices sharing a single
556 interrupt. The HPT343 chipset in its current form is a non-bootable
557 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
558 PCI UDMA controllers. This driver requires dynamic tuning of the
559 chipset during the ide-probe at boot time. It is reported to support
560 DVD II drives, by the manufacturer.
562 config HPT34X_AUTODMA
563 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
564 depends on BLK_DEV_HPT34X && EXPERIMENTAL
566 This is a dangerous thing to attempt currently! Please read the
567 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
568 here, then say Y to "Use DMA by default when available" as well.
572 config BLK_DEV_HPT366
573 tristate "HPT36X/37X chipset support"
575 HPT366 is an Ultra DMA chipset for ATA-66.
576 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
577 HPT370 is an Ultra DMA chipset for ATA-100.
578 HPT372 is an Ultra DMA chipset for ATA-100.
579 HPT374 is an Ultra DMA chipset for ATA-100.
581 This driver adds up to 4 more EIDE devices sharing a single
584 The HPT366 chipset in its current form is bootable. One solution
585 for this problem are special LILO commands for redirecting the
586 reference to device 0x80. The other solution is to say Y to "Boot
587 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
588 your mother board has the chipset natively mounted. Regardless one
589 should use the fore mentioned option and call at LILO or include
590 "ide=reverse" in LILO's append-line.
592 This driver requires dynamic tuning of the chipset during the
593 ide-probe at boot. It is reported to support DVD II drives, by the
596 config BLK_DEV_SC1200
597 tristate "National SCx200 chipset support"
599 This driver adds support for the built in IDE on the National
600 SCx200 series of embedded x86 "Geode" systems
603 tristate "Intel PIIXn chipsets support"
605 This driver adds explicit support for Intel PIIX and ICH chips
606 and also for the Efar Victory66 (slc90e66) chip. This allows
607 the kernel to change PIO, DMA and UDMA speeds and to configure
608 the chip to optimum performance.
610 config BLK_DEV_IT8172
611 bool "IT8172 IDE support"
612 depends on (MIPS_ITE8172 || MIPS_IVR)
614 Say Y here to support the on-board IDE controller on the Integrated
615 Technology Express, Inc. ITE8172 SBC. Vendor page at
616 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
617 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
619 config BLK_DEV_NS87415
620 tristate "NS87415 chipset support"
622 This driver adds detection and support for the NS87415 chip
623 (used in SPARC64, among others).
625 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
627 config BLK_DEV_PDC202XX_OLD
628 tristate "PROMISE PDC202{46|62|65|67} support"
630 Promise Ultra33 or PDC20246
631 Promise Ultra66 or PDC20262
632 Promise Ultra100 or PDC20265/PDC20267/PDC20268
634 This driver adds up to 4 more EIDE devices sharing a single
635 interrupt. This add-on card is a bootable PCI UDMA controller. Since
636 multiple cards can be installed and there are BIOS ROM problems that
637 happen if the BIOS revisions of all installed cards (three-max) do
638 not match, the driver attempts to do dynamic tuning of the chipset
639 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
640 for more than one card. This card may require that you say Y to
641 "Special UDMA Feature".
643 If you say Y here, you need to say Y to "Use DMA by default when
646 Please read the comments at the top of
647 <file:drivers/ide/pci/pdc202xx_old.c>.
651 config PDC202XX_BURST
652 bool "Special UDMA Feature"
653 depends on BLK_DEV_PDC202XX_OLD
655 This option causes the pdc202xx driver to enable UDMA modes on the
656 PDC202xx even when the PDC202xx BIOS has not done so.
658 It was originally designed for the PDC20246/Ultra33, whose BIOS will
659 only setup UDMA on the first two PDC20246 cards. It has also been
660 used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
661 when the PDC20265 BIOS has been disabled (for faster boot up).
663 Please read the comments at the top of
664 <file:drivers/ide/pci/pdc202xx_old.c>.
668 config BLK_DEV_PDC202XX_NEW
669 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
671 # FIXME - probably wants to be one for old and for new
672 config PDC202XX_FORCE
673 bool "Enable controller even if disabled by BIOS"
674 depends on BLK_DEV_PDC202XX_NEW
676 Enable the PDC202xx controller even if it has been disabled in the BIOS setup.
679 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
681 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
684 config BLK_DEV_SGIIOC4
685 tristate "Silicon Graphics IOC4 chipset support"
686 depends on IA64_SGI_SN2 || IA64_GENERIC
688 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
689 chipset, which has one channel and can support two devices.
690 Please say Y here if you have an Altix System from SGI.
692 config BLK_DEV_SIIMAGE
693 tristate "Silicon Image chipset support"
695 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
696 3112 (Serial ATA) chips.
698 config BLK_DEV_SIS5513
699 tristate "SiS5513 chipset support"
702 This driver ensures (U)DMA support for SIS5513 chipset family based
705 The following chipsets are supported:
706 ATA16: SiS5511, SiS5513
707 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
708 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
709 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
712 If you say Y here, you need to say Y to "Use DMA by default when
715 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
717 config BLK_DEV_SLC90E66
718 tristate "SLC90E66 chipset support"
720 This driver ensures (U)DMA support for Victroy66 SouthBridges for
721 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
722 The nice thing about it is that you can mix Ultra/DMA/PIO devices
723 and it will handle timing cycles. Since this is an improved
724 look-a-like to the PIIX4 it should be a nice addition.
726 If you say Y here, you need to say Y to "Use DMA by default when
729 Please read the comments at the top of
730 <file:drivers/ide/pci/slc90e66.c>.
732 config BLK_DEV_TRM290
733 tristate "Tekram TRM290 chipset support"
735 This driver adds support for bus master DMA transfers
736 using the Tekram TRM290 PCI IDE chip. Volunteers are
737 needed for further tweaking and development.
738 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
740 config BLK_DEV_VIA82CXXX
741 tristate "VIA82CXXX chipset support"
743 This driver adds explicit support for VIA BusMastering IDE chips.
744 This allows the kernel to change PIO, DMA and UDMA speeds and to
745 configure the chip to optimum performance.
749 config BLK_DEV_IDE_PMAC
750 bool "Builtin PowerMac IDE support"
751 depends on PPC_PMAC && IDE=y
753 This driver provides support for the built-in IDE controller on
754 most of the recent Apple Power Macintoshes and PowerBooks.
757 config BLK_DEV_IDE_PMAC_ATA100FIRST
758 bool "Probe internal ATA/100 (Kauai) first"
759 depends on BLK_DEV_IDE_PMAC
761 This option will cause the ATA/100 controller found in UniNorth2
762 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
763 to be probed before the ATA/66 and ATA/33 controllers. Without
764 these, those machine used to have the hard disk on hdc and the
765 CD-ROM on hda. This option changes this to more natural hda for
766 hard disk and hdc for CD-ROM.
768 config BLK_DEV_IDEDMA_PMAC
769 bool "PowerMac IDE DMA support"
770 depends on BLK_DEV_IDE_PMAC
772 This option allows the driver for the built-in IDE controller on
773 Power Macintoshes and PowerBooks to use DMA (direct memory access)
774 to transfer data to and from memory. Saying Y is safe and improves
777 config BLK_DEV_IDE_PMAC_BLINK
778 bool "Blink laptop LED on drive activity"
779 depends on BLK_DEV_IDE_PMAC && ADB_PMU
781 This option enables the use of the sleep LED as a hard drive
784 config BLK_DEV_IDEDMA_PMAC_AUTO
785 bool "Use DMA by default"
786 depends on BLK_DEV_IDEDMA_PMAC
788 This option allows the driver for the built-in IDE controller on
789 Power Macintoshes and PowerBooks to use DMA automatically, without
790 it having to be explicitly enabled. This option is provided because
791 of concerns about a couple of cases where using DMA on buggy PC
792 hardware may have caused damage. Saying Y should be safe on all
796 def_bool ARM && (ARCH_A5K || ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
798 config BLK_DEV_IDE_ICSIDE
799 tristate "ICS IDE interface support"
800 depends on ARM && ARCH_ACORN
802 On Acorn systems, say Y here if you wish to use the ICS IDE
803 interface card. This is not required for ICS partition support.
804 If you are unsure, say N to this.
806 config BLK_DEV_IDEDMA_ICS
807 bool "ICS DMA support"
808 depends on BLK_DEV_IDE_ICSIDE
810 Say Y here if you want to add DMA (Direct Memory Access) support to
813 config IDEDMA_ICS_AUTO
814 bool "Use ICS DMA by default"
815 depends on BLK_DEV_IDEDMA_ICS
817 Prior to kernel version 2.1.112, Linux used to automatically use
818 DMA for IDE drives and chipsets which support it. Due to concerns
819 about a couple of cases where buggy hardware may have caused damage,
820 the default is now to NOT use DMA automatically. To revert to the
821 previous behaviour, say Y to this question.
823 If you suspect your hardware is at all flakey, say N here.
824 Do NOT email the IDE kernel people regarding this issue!
826 config BLK_DEV_IDE_RAPIDE
827 tristate "RapIDE interface support"
828 depends on ARM && ARCH_ACORN
830 Say Y here if you want to support the Yellowstone RapIDE controller
831 manufactured for use with Acorn computers.
833 config BLK_DEV_IDE_BAST
834 tristate "Simtec BAST / Thorcom VR1000 IDE support"
835 depends on ARM && (ARCH_BAST || MACH_VR100)
837 Say Y here if you want to support the onboard IDE channels on the
838 Simtec BAST or the Thorcom VR1000
841 bool "Amiga Gayle IDE interface support"
844 This is the IDE driver for the Amiga Gayle IDE interface. It supports
845 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
846 This includes builtin IDE interfaces on some Amiga models (A600,
847 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
848 bus (M-Tech E-Matrix 530 expansion card).
849 Say Y if you have an Amiga with a Gayle IDE interface and want to use
850 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
852 Note that you also have to enable Zorro bus support if you want to
853 use Gayle IDE interfaces on the Zorro expansion bus.
855 config BLK_DEV_IDEDOUBLER
856 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
857 depends on BLK_DEV_GAYLE && EXPERIMENTAL
859 This driver provides support for the so-called `IDE doublers' (made
860 by various manufacturers, e.g. Eyetech) that can be connected to the
861 builtin IDE interface of some Amiga models. Using such an IDE
862 doubler, you can connect up to four instead of two IDE devices on
863 the Amiga's builtin IDE interface.
865 Note that the normal Amiga Gayle IDE driver may not work correctly
866 if you have an IDE doubler and don't enable this driver!
868 Say Y if you have an IDE doubler. The driver is enabled at kernel
869 runtime using the "ide=doubler" kernel boot parameter.
871 config BLK_DEV_BUDDHA
872 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
873 depends on ZORRO && EXPERIMENTAL
875 This is the IDE driver for the IDE interfaces on the Buddha,
876 Catweasel and X-Surf expansion boards. It supports up to two interfaces
877 on the Buddha, three on the Catweasel and two on the X-Surf.
879 Say Y if you have a Buddha or Catweasel expansion board and want to
880 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
881 to one of its IDE interfaces.
883 config BLK_DEV_FALCON_IDE
884 bool "Falcon IDE interface support"
887 This is the IDE driver for the builtin IDE interface on the Atari
888 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
889 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
892 config BLK_DEV_MAC_IDE
893 bool "Macintosh Quadra/Powerbook IDE interface support"
896 This is the IDE driver for the builtin IDE interface on some m68k
897 Macintosh models. It supports both the `Quadra style' (used in
898 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
899 (used in the Powerbook 150 and 190 models) IDE interface.
901 Say Y if you have such an Macintosh model and want to use IDE
902 devices (hard disks, CD-ROM drives, etc.) that are connected to the
903 builtin IDE interface.
905 config BLK_DEV_Q40IDE
906 bool "Q40/Q60 IDE interface support"
909 Enable the on-board IDE controller in the Q40/Q60. This should
910 normally be on; disable it only if you are running a custom hard
911 drive subsystem through an expansion card.
913 config BLK_DEV_MPC8xx_IDE
914 bool "MPC8xx IDE support"
917 This option provides support for IDE on Motorola MPC8xx Systems.
918 Please see 'Type of MPC8xx IDE interface' for details.
923 prompt "Type of MPC8xx IDE interface"
924 depends on BLK_DEV_MPC8xx_IDE
925 default IDE_8xx_PCCARD
927 config IDE_8xx_PCCARD
930 Select how the IDE devices are connected to the MPC8xx system:
932 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
933 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
934 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
937 8xx_DIRECT is used for directly connected IDE devices using the 8xx
938 internal PCMCIA interface (example: IVMS8 systems)
940 EXT_DIRECT is used for IDE devices directly connected to the 8xx
941 bus using some glue logic, but _not_ the 8xx internal
942 PCMCIA interface (example: IDIF860 systems)
944 config IDE_8xx_DIRECT
947 config IDE_EXT_DIRECT
954 bool "Other IDE chipset support"
957 Say Y here if you want to include enhanced support for various IDE
958 interface chipsets used on motherboards and add-on cards. You can
959 then pick your particular IDE chip from among the following options.
960 This enhanced support may be necessary for Linux to be able to
961 access the 3rd/4th drives in some systems. It may also enable
962 setting of higher speed I/O rates to improve system performance with
963 these chipsets. Most of these also require special kernel boot
964 parameters to actually turn on the support at runtime; you can find
965 a list of these in the file <file:Documentation/ide.txt>.
967 People with SCSI-only systems can say N here.
971 comment "Note: most of these also require special kernel boot parameters"
973 config BLK_DEV_4DRIVES
974 bool "Generic 4 drives/port support"
976 Certain older chipsets, including the Tekram 690CD, use a single set
977 of I/O ports at 0x1f0 to control up to four drives, instead of the
978 customary two drives per port. Support for this can be enabled at
979 runtime using the "ide0=four" kernel boot parameter if you say Y
982 config BLK_DEV_ALI14XX
983 tristate "ALI M14xx support"
985 This driver is enabled at runtime using the "ide0=ali14xx" kernel
986 boot parameter. It enables support for the secondary IDE interface
987 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
988 I/O speeds to be set as well. See the files
989 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
992 config BLK_DEV_DTC2278
993 tristate "DTC-2278 support"
995 This driver is enabled at runtime using the "ide0=dtc2278" kernel
996 boot parameter. It enables support for the secondary IDE interface
997 of the DTC-2278 card, and permits faster I/O speeds to be set as
998 well. See the <file:Documentation/ide.txt> and
999 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1001 config BLK_DEV_HT6560B
1002 tristate "Holtek HT6560B support"
1004 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1005 boot parameter. It enables support for the secondary IDE interface
1006 of the Holtek card, and permits faster I/O speeds to be set as well.
1007 See the <file:Documentation/ide.txt> and
1008 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1010 config BLK_DEV_PDC4030
1011 tristate "PROMISE DC4030 support (EXPERIMENTAL)"
1012 depends on BLK_DEV_IDEDISK && EXPERIMENTAL
1014 This driver provides support for the secondary IDE interface and
1015 cache of the original Promise IDE chipsets, e.g. DC4030 and DC5030.
1016 It is nothing to do with the later range of Promise UDMA chipsets -
1017 see the PDC_202XX support for these. CD-ROM and TAPE devices are not
1018 supported (and probably never will be since I don't think the cards
1019 support them). This driver is enabled at runtime using the "ide0=dc4030"
1020 or "ide1=dc4030" kernel boot parameter. See the
1021 <file:drivers/ide/legacy/pdc4030.c> file 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
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 answering 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 || BLK_DEV_IDEDMA_PMAC_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