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"
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"
99 bool "Use old disk-only driver on primary interface"
100 depends on ((X86 && X86_PC9800!=y) || SH_MPC1211)
102 There are two drivers for MFM/RLL/IDE disks. Most people use just
103 the new enhanced driver by itself. This option however installs the
104 old hard disk driver to control the primary IDE/disk interface in
105 the system, leaving the new enhanced IDE driver to take care of only
106 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
107 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
108 IDE interface. Choosing this option may be useful for older systems
109 which have MFM/RLL/ESDI controller+drives at the primary port
110 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
113 Normally, just say N here; you will then use the new driver for all
116 config BLK_DEV_HD_IDE98
117 bool "Use old disk-only driver on primary interface"
118 depends on X86 && X86_PC9800
120 There are two drivers for MFM/RLL/IDE disks. Most people use just
121 the new enhanced driver by itself. This option however installs the
122 old hard disk driver to control the primary IDE/disk interface in
123 the system, leaving the new enhanced IDE driver to take care of only
124 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
125 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
126 IDE interface. Choosing this option may be useful for older systems
127 which have MFM/RLL/ESDI controller+drives at the primary port
128 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
131 Normally, just say N here; you will then use the new driver for all
134 config BLK_DEV_IDEDISK
135 tristate "Include IDE/ATA-2 DISK support"
137 This will include enhanced support for MFM/RLL/IDE hard disks. If
138 you have a MFM/RLL/IDE disk, and there is no special reason to use
139 the old hard disk driver instead, say Y. If you have an SCSI-only
140 system, you can say N here.
142 To compile this driver as a module, choose M here: the
143 module will be called ide-disk.
144 Do not compile this driver as a module if your root file system
145 (the one containing the directory /) is located on the IDE disk.
149 config IDEDISK_MULTI_MODE
150 bool "Use multi-mode by default"
151 depends on BLK_DEV_IDEDISK
153 If you get this error, try to say Y here:
155 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
156 hda: set_multmode: error=0x04 { DriveStatusError }
161 tristate "PCMCIA IDE support"
164 Support for outboard IDE disks, tape drives, and CD-ROM drives
165 connected through a PCMCIA card.
168 tristate "Include IDE/ATAPI CDROM support"
170 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
171 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
172 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
173 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
174 double(2X) or better speed drives.
176 If you say Y here, the CD-ROM drive will be identified at boot time
177 along with other IDE devices, as "hdb" or "hdc", or something
178 similar (check the boot messages with dmesg). If this is your only
179 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
180 to say Y or M to "ISO 9660 CD-ROM file system support".
182 Note that older versions of LILO (LInux LOader) cannot properly deal
183 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
184 <http://lilo.go.dyndns.org/>.
186 To compile this driver as a module, choose M here: the
187 module will be called ide-cd.
189 config BLK_DEV_IDETAPE
190 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
191 depends on EXPERIMENTAL
193 If you have an IDE tape drive using the ATAPI protocol, say Y.
194 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
195 similar to the SCSI protocol. If you have an SCSI tape drive
196 however, you can say N here.
198 You should also say Y if you have an OnStream DI-30 tape drive; this
199 will not work with the SCSI protocol, until there is support for the
200 SC-30 and SC-50 versions.
202 If you say Y here, the tape drive will be identified at boot time
203 along with other IDE devices, as "hdb" or "hdc", or something
204 similar, and will be mapped to a character device such as "ht0"
205 (check the boot messages with dmesg). Be sure to consult the
206 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
207 for usage information.
209 To compile this driver as a module, choose M here: the
210 module will be called ide-tape.
212 config BLK_DEV_IDEFLOPPY
213 tristate "Include IDE/ATAPI FLOPPY support"
215 If you have an IDE floppy drive which uses the ATAPI protocol,
216 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
217 drives, similar to the SCSI protocol.
219 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
220 this driver. For information about jumper settings and the question
221 of when a ZIP drive uses a partition table, see
222 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
223 (ATAPI PD-CD/CDR drives are not supported by this driver; support
224 for PD-CD/CDR drives is available if you answer Y to
225 "SCSI emulation support", below).
227 If you say Y here, the FLOPPY drive will be identified along with
228 other IDE devices, as "hdb" or "hdc", or something similar (check
229 the boot messages with dmesg).
231 To compile this driver as a module, choose M here: the
232 module will be called ide-floppy.
234 config BLK_DEV_IDESCSI
235 tristate "SCSI emulation support"
238 WARNING: ide-scsi is no longer needed for cd writing applications!
239 The 2.6 kernel supports direct writing to ide-cd, which eliminates
240 the need for ide-scsi + the entire scsi stack just for writing a
241 cd. The new method is more efficient in every way.
243 This will provide SCSI host adapter emulation for IDE ATAPI devices,
244 and will allow you to use a SCSI device driver instead of a native
247 This is useful if you have an ATAPI device for which no native
248 driver has been written (for example, an ATAPI PD-CD drive);
249 you can then use this emulation together with an appropriate SCSI
250 device driver. In order to do this, say Y here and to "SCSI support"
251 and "SCSI generic support", below. You must then provide the kernel
252 command line "hdx=ide-scsi" (try "man bootparam" or see the
253 documentation of your boot loader (lilo or loadlin) about how to
254 pass options to the kernel at boot time) for devices if you want the
255 native EIDE sub-drivers to skip over the native support, so that
256 this SCSI emulation can be used instead.
258 Note that this option does NOT allow you to attach SCSI devices to a
259 box that doesn't have a SCSI host adapter installed.
261 If both this SCSI emulation and native ATAPI support are compiled
262 into the kernel, the native support will be used.
264 config IDE_TASK_IOCTL
265 bool "IDE Taskfile Access"
267 This is a direct raw access to the media. It is a complex but
268 elegant solution to test and validate the domain of the hardware and
269 perform below the driver data recover if needed. This is the most
270 basic form of media-forensics.
272 If you are unsure, say N here.
274 config IDE_TASKFILE_IO
275 bool 'IDE Taskfile IO (EXPERIMENTAL)'
276 depends on EXPERIMENTAL
279 Use new taskfile IO code.
281 It is safe to say Y to this question, in most cases.
283 comment "IDE chipset support/bugfixes"
286 tristate "generic/default IDE chipset support"
291 config BLK_DEV_CMD640
292 bool "CMD640 chipset bugfix/support"
295 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
296 Pentium motherboards, usually in combination with a "Neptune" or
297 "SiS" chipset. Unfortunately, it has a number of rather nasty
298 design flaws that can cause severe data corruption under many common
299 conditions. Say Y here to include code which tries to automatically
300 detect and correct the problems under Linux. This option also
301 enables access to the secondary IDE ports in some CMD640 based
304 This driver will work automatically in PCI based systems (most new
305 systems have PCI slots). But if your system uses VESA local bus
306 (VLB) instead of PCI, you must also supply a kernel boot parameter
307 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
308 bootparam" or see the documentation of your boot loader about how to
309 pass options to the kernel.)
311 The CMD640 chip is also used on add-in cards by Acculogic, and on
312 the "CSA-6400E PCI to IDE controller" that some people have. For
313 details, read <file:Documentation/ide.txt>.
315 config BLK_DEV_CMD640_ENHANCED
316 bool "CMD640 enhanced support"
317 depends on BLK_DEV_CMD640
319 This option includes support for setting/autotuning PIO modes and
320 prefetch on CMD640 IDE interfaces. For details, read
321 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
322 and your BIOS does not already do this for you, then say Y here.
325 config BLK_DEV_IDEPNP
326 bool "PNP EIDE support"
329 If you have a PnP (Plug and Play) compatible EIDE card and
330 would like the kernel to automatically detect and activate
333 config BLK_DEV_IDEPCI
334 bool "PCI IDE chipset support" if PCI
335 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
337 Say Y here for PCI systems which use IDE drive(s).
338 This option helps the IDE driver to automatically detect and
339 configure all PCI-based IDE interfaces in your system.
341 config IDEPCI_SHARE_IRQ
342 bool "Sharing PCI IDE interrupts support"
343 depends on PCI && BLK_DEV_IDEPCI
345 Some ATA/IDE chipsets have hardware support which allows for
346 sharing a single IRQ with other cards. To enable support for
347 this in the ATA/IDE driver, say Y here.
349 It is safe to say Y to this question, in most cases.
352 config BLK_DEV_OFFBOARD
353 bool "Boot off-board chipsets first support"
354 depends on PCI && BLK_DEV_IDEPCI
356 Normally, IDE controllers built into the motherboard (on-board
357 controllers) are assigned to ide0 and ide1 while those on add-in PCI
358 cards (off-board controllers) are relegated to ide2 and ide3.
359 Answering Y here will allow you to reverse the situation, with
360 off-board controllers on ide0/1 and on-board controllers on ide2/3.
361 This can improve the usability of some boot managers such as lilo
362 when booting from a drive on an off-board controller.
364 If you say Y here, and you actually want to reverse the device scan
365 order as explained above, you also need to issue the kernel command
366 line option "ide=reverse". (Try "man bootparam" or see the
367 documentation of your boot loader (lilo or loadlin) about how to
368 pass options to the kernel at boot time.)
370 Note that, if you do this, the order of the hd* devices will be
371 rearranged which may require modification of fstab and other files.
375 config BLK_DEV_GENERIC
376 tristate "Generic PCI IDE Chipset Support"
377 depends on BLK_DEV_IDEPCI
379 config BLK_DEV_OPTI621
380 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
381 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
383 This is a driver for the OPTi 82C621 EIDE controller.
384 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
386 config BLK_DEV_RZ1000
387 tristate "RZ1000 chipset bugfix/support"
388 depends on PCI && BLK_DEV_IDEPCI && X86
390 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
391 Pentium motherboards, usually along with the "Neptune" chipset.
392 Unfortunately, it has a rather nasty design flaw that can cause
393 severe data corruption under many conditions. Say Y here to include
394 code which automatically detects and corrects the problem under
395 Linux. This may slow disk throughput by a few percent, but at least
396 things will operate 100% reliably.
398 config BLK_DEV_SL82C105
399 tristate "Winbond SL82c105 support"
400 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
402 If you have a Winbond SL82c105 IDE controller, say Y here to enable
403 special configuration for this chip. This is common on various CHRP
404 motherboards, but could be used elsewhere. If in doubt, say Y.
406 config BLK_DEV_IDEDMA_PCI
407 bool "Generic PCI bus-master DMA support"
408 depends on PCI && BLK_DEV_IDEPCI
410 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
411 is capable of bus-master DMA operation (most Pentium PCI systems),
412 you will want to say Y here to reduce CPU overhead. You can then use
413 the "hdparm" utility to enable DMA for drives for which it was not
414 enabled automatically. By default, DMA is not enabled automatically
415 for these drives, but you can change that by saying Y to the
416 following question "Use DMA by default when available". You can get
417 the latest version of the hdparm utility from
418 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
420 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
421 and the file <file:Documentation/ide.txt> for more information.
423 It is safe to say Y to this question.
425 if BLK_DEV_IDEDMA_PCI
427 config BLK_DEV_IDEDMA_FORCED
428 bool "Force enable legacy 2.0.X HOSTS to use DMA"
430 This is an old piece of lost code from Linux 2.0 Kernels.
432 Generally say N here.
434 config IDEDMA_PCI_AUTO
435 bool "Use PCI DMA by default when available"
437 Prior to kernel version 2.1.112, Linux used to automatically use
438 DMA for IDE drives and chipsets which support it. Due to concerns
439 about a couple of cases where buggy hardware may have caused damage,
440 the default is now to NOT use DMA automatically. To revert to the
441 previous behaviour, say Y to this question.
443 If you suspect your hardware is at all flakey, say N here.
444 Do NOT email the IDE kernel people regarding this issue!
446 It is normally safe to answer Y to this question unless your
447 motherboard uses a VIA VP2 chipset, in which case you should say N.
449 config IDEDMA_ONLYDISK
450 bool "Enable DMA only for disks "
451 depends on IDEDMA_PCI_AUTO
453 This is used if you know your ATAPI Devices are going to fail DMA
456 Generally say N here.
460 depends on PCI && BLK_DEV_IDEPCI
461 default BLK_DEV_IDEDMA_PCI
463 config BLK_DEV_AEC62XX
464 tristate "AEC62XX chipset support"
466 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
467 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
468 speeds and to configure the chip to optimum performance.
470 config BLK_DEV_ALI15X3
471 tristate "ALI M15x3 chipset support"
473 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
474 onboard chipsets. It also tests for Simplex mode and enables
475 normal dual channel support.
477 If you say Y here, you also need to say Y to "Use DMA by default
478 when available", above. Please read the comments at the top of
479 <file:drivers/ide/pci/alim15x3.c>.
484 bool "ALI M15x3 WDC support (DANGEROUS)"
485 depends on BLK_DEV_ALI15X3
487 This allows for UltraDMA support for WDC drives that ignore CRC
488 checking. You are a fool for enabling this option, but there have
489 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
490 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
493 Using this option can allow WDC drives to run at ATA-4/5 transfer
494 rates with only an ATA-2 support structure.
498 config BLK_DEV_AMD74XX
499 tristate "AMD and nVidia IDE support"
501 This driver adds explicit support for AMD-7xx and AMD-8111 chips
502 and also for the nVidia nForce chip. This allows the kernel to
503 change PIO, DMA and UDMA speeds and to configure the chip to
506 config BLK_DEV_ATIIXP
507 tristate "ATI IXP chipset IDE support"
510 This driver adds explicit support for ATI IXP chipset.
511 This allows the kernel to change PIO, DMA and UDMA speeds
512 and to configure the chip to optimum performance.
514 Say Y here if you have an ATI IXP chipset IDE controller.
516 config BLK_DEV_CMD64X
517 tristate "CMD64{3|6|8|9} chipset support"
519 Say Y here if you have an IDE controller which uses any of these
520 chipsets: CMD643, CMD646, or CMD648.
522 config BLK_DEV_TRIFLEX
523 tristate "Compaq Triflex IDE support"
525 Say Y here if you have a Compaq Triflex IDE controller, such
526 as those commonly found on Compaq Pentium-Pro systems
528 config BLK_DEV_CY82C693
529 tristate "CY82C693 chipset support"
531 This driver adds detection and support for the CY82C693 chipset
532 used on Digital's PC-Alpha 164SX boards.
534 If you say Y here, you need to say Y to "Use DMA by default
535 when available" as well.
537 config BLK_DEV_CS5520
538 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
539 depends on EXPERIMENTAL
541 Include support for PIO tuning an virtual DMA on the Cyrix MediaGX
542 5510/5520 chipset. This will automatically be detected and
545 It is safe to say Y to this question.
547 config BLK_DEV_CS5530
548 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
550 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
551 will automatically be detected and configured if found.
553 It is safe to say Y to this question.
555 config BLK_DEV_HPT34X
556 tristate "HPT34X chipset support"
558 This driver adds up to 4 more EIDE devices sharing a single
559 interrupt. The HPT343 chipset in its current form is a non-bootable
560 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
561 PCI UDMA controllers. This driver requires dynamic tuning of the
562 chipset during the ide-probe at boot time. It is reported to support
563 DVD II drives, by the manufacturer.
565 config HPT34X_AUTODMA
566 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
567 depends on BLK_DEV_HPT34X && EXPERIMENTAL
569 This is a dangerous thing to attempt currently! Please read the
570 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
571 here, then say Y to "Use DMA by default when available" as well.
575 config BLK_DEV_HPT366
576 tristate "HPT36X/37X chipset support"
578 HPT366 is an Ultra DMA chipset for ATA-66.
579 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
580 HPT370 is an Ultra DMA chipset for ATA-100.
581 HPT372 is an Ultra DMA chipset for ATA-100.
582 HPT374 is an Ultra DMA chipset for ATA-100.
584 This driver adds up to 4 more EIDE devices sharing a single
587 The HPT366 chipset in its current form is bootable. One solution
588 for this problem are special LILO commands for redirecting the
589 reference to device 0x80. The other solution is to say Y to "Boot
590 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
591 your mother board has the chipset natively mounted. Regardless one
592 should use the fore mentioned option and call at LILO or include
593 "ide=reverse" in LILO's append-line.
595 This driver requires dynamic tuning of the chipset during the
596 ide-probe at boot. It is reported to support DVD II drives, by the
599 config BLK_DEV_SC1200
600 tristate "National SCx200 chipset support"
602 This driver adds support for the built in IDE on the National
603 SCx200 series of embedded x86 "Geode" systems
606 tristate "Intel PIIXn chipsets support"
608 This driver adds explicit support for Intel PIIX and ICH chips
609 and also for the Efar Victory66 (slc90e66) chip. This allows
610 the kernel to change PIO, DMA and UDMA speeds and to configure
611 the chip to optimum performance.
613 config BLK_DEV_IT8172
614 bool "IT8172 IDE support"
615 depends on (MIPS_ITE8172 || MIPS_IVR)
617 Say Y here to support the on-board IDE controller on the Integrated
618 Technology Express, Inc. ITE8172 SBC. Vendor page at
619 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
620 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
622 config BLK_DEV_NS87415
623 tristate "NS87415 chipset support"
625 This driver adds detection and support for the NS87415 chip
626 (used in SPARC64, among others).
628 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
630 config BLK_DEV_PDC202XX_OLD
631 tristate "PROMISE PDC202{46|62|65|67} support"
633 Promise Ultra33 or PDC20246
634 Promise Ultra66 or PDC20262
635 Promise Ultra100 or PDC20265/PDC20267/PDC20268
637 This driver adds up to 4 more EIDE devices sharing a single
638 interrupt. This add-on card is a bootable PCI UDMA controller. Since
639 multiple cards can be installed and there are BIOS ROM problems that
640 happen if the BIOS revisions of all installed cards (three-max) do
641 not match, the driver attempts to do dynamic tuning of the chipset
642 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
643 for more than one card. This card may require that you say Y to
644 "Special UDMA Feature".
646 If you say Y here, you need to say Y to "Use DMA by default when
649 Please read the comments at the top of
650 <file:drivers/ide/pci/pdc202xx_old.c>.
654 config PDC202XX_BURST
655 bool "Special UDMA Feature"
656 depends on BLK_DEV_PDC202XX_OLD
658 This option causes the pdc202xx driver to enable UDMA modes on the
659 PDC202xx even when the PDC202xx BIOS has not done so.
661 It was originally designed for the PDC20246/Ultra33, whose BIOS will
662 only setup UDMA on the first two PDC20246 cards. It has also been
663 used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
664 when the PDC20265 BIOS has been disabled (for faster boot up).
666 Please read the comments at the top of
667 <file:drivers/ide/pci/pdc202xx_old.c>.
671 config BLK_DEV_PDC202XX_NEW
672 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
674 # FIXME - probably wants to be one for old and for new
675 config PDC202XX_FORCE
676 bool "Enable controller even if disabled by BIOS"
677 depends on BLK_DEV_PDC202XX_NEW
679 Enable the PDC202xx controller even if it has been disabled in the BIOS setup.
682 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
684 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
687 config BLK_DEV_SGIIOC4
688 tristate "Silicon Graphics IOC4 chipset support"
689 depends on IA64_SGI_SN2 || IA64_GENERIC
691 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
692 chipset, which has one channel and can support two devices.
693 Please say Y here if you have an Altix System from SGI.
695 config BLK_DEV_SIIMAGE
696 tristate "Silicon Image chipset support"
698 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
699 3112 (Serial ATA) chips.
701 config BLK_DEV_SIS5513
702 tristate "SiS5513 chipset support"
705 This driver ensures (U)DMA support for SIS5513 chipset family based
708 The following chipsets are supported:
709 ATA16: SiS5511, SiS5513
710 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
711 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
712 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
715 If you say Y here, you need to say Y to "Use DMA by default when
718 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
720 config BLK_DEV_SLC90E66
721 tristate "SLC90E66 chipset support"
723 This driver ensures (U)DMA support for Victroy66 SouthBridges for
724 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
725 The nice thing about it is that you can mix Ultra/DMA/PIO devices
726 and it will handle timing cycles. Since this is an improved
727 look-a-like to the PIIX4 it should be a nice addition.
729 If you say Y here, you need to say Y to "Use DMA by default when
732 Please read the comments at the top of
733 <file:drivers/ide/pci/slc90e66.c>.
735 config BLK_DEV_TRM290
736 tristate "Tekram TRM290 chipset support"
738 This driver adds support for bus master DMA transfers
739 using the Tekram TRM290 PCI IDE chip. Volunteers are
740 needed for further tweaking and development.
741 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
743 config BLK_DEV_VIA82CXXX
744 tristate "VIA82CXXX chipset support"
746 This driver adds explicit support for VIA BusMastering IDE chips.
747 This allows the kernel to change PIO, DMA and UDMA speeds and to
748 configure the chip to optimum performance.
752 config BLK_DEV_IDE_PMAC
753 bool "Builtin PowerMac IDE support"
756 This driver provides support for the built-in IDE controller on
757 most of the recent Apple Power Macintoshes and PowerBooks.
760 config BLK_DEV_IDE_PMAC_ATA100FIRST
761 bool "Probe internal ATA/100 (Kauai) first"
762 depends on BLK_DEV_IDE_PMAC
764 This option will cause the ATA/100 controller found in UniNorth2
765 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
766 to be probed before the ATA/66 and ATA/33 controllers. Without
767 these, those machine used to have the hard disk on hdc and the
768 CD-ROM on hda. This option changes this to more natural hda for
769 hard disk and hdc for CD-ROM.
771 config BLK_DEV_IDEDMA_PMAC
772 bool "PowerMac IDE DMA support"
773 depends on BLK_DEV_IDE_PMAC
775 This option allows the driver for the built-in IDE controller on
776 Power Macintoshes and PowerBooks to use DMA (direct memory access)
777 to transfer data to and from memory. Saying Y is safe and improves
780 config BLK_DEV_IDE_PMAC_BLINK
781 bool "Blink laptop LED on drive activity"
782 depends on BLK_DEV_IDE_PMAC && ADB_PMU
784 This option enables the use of the sleep LED as a hard drive
787 config BLK_DEV_IDEDMA_PMAC_AUTO
788 bool "Use DMA by default"
789 depends on BLK_DEV_IDEDMA_PMAC
791 This option allows the driver for the built-in IDE controller on
792 Power Macintoshes and PowerBooks to use DMA automatically, without
793 it having to be explicitly enabled. This option is provided because
794 of concerns about a couple of cases where using DMA on buggy PC
795 hardware may have caused damage. Saying Y should be safe on all
799 def_bool ARM && (ARCH_A5K || ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
801 config BLK_DEV_IDE_ICSIDE
802 tristate "ICS IDE interface support"
803 depends on ARM && ARCH_ACORN
805 On Acorn systems, say Y here if you wish to use the ICS IDE
806 interface card. This is not required for ICS partition support.
807 If you are unsure, say N to this.
809 config BLK_DEV_IDEDMA_ICS
810 bool "ICS DMA support"
811 depends on BLK_DEV_IDE_ICSIDE
813 Say Y here if you want to add DMA (Direct Memory Access) support to
816 config IDEDMA_ICS_AUTO
817 bool "Use ICS DMA by default"
818 depends on BLK_DEV_IDEDMA_ICS
820 Prior to kernel version 2.1.112, Linux used to automatically use
821 DMA for IDE drives and chipsets which support it. Due to concerns
822 about a couple of cases where buggy hardware may have caused damage,
823 the default is now to NOT use DMA automatically. To revert to the
824 previous behaviour, say Y to this question.
826 If you suspect your hardware is at all flakey, say N here.
827 Do NOT email the IDE kernel people regarding this issue!
829 config BLK_DEV_IDE_RAPIDE
830 tristate "RapIDE interface support"
831 depends on ARM && ARCH_ACORN
833 Say Y here if you want to support the Yellowstone RapIDE controller
834 manufactured for use with Acorn computers.
837 bool "Amiga Gayle IDE interface support"
840 This is the IDE driver for the Amiga Gayle IDE interface. It supports
841 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
842 This includes builtin IDE interfaces on some Amiga models (A600,
843 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
844 bus (M-Tech E-Matrix 530 expansion card).
845 Say Y if you have an Amiga with a Gayle IDE interface and want to use
846 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
848 Note that you also have to enable Zorro bus support if you want to
849 use Gayle IDE interfaces on the Zorro expansion bus.
851 config BLK_DEV_IDEDOUBLER
852 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
853 depends on BLK_DEV_GAYLE && EXPERIMENTAL
855 This driver provides support for the so-called `IDE doublers' (made
856 by various manufacturers, e.g. Eyetech) that can be connected to the
857 builtin IDE interface of some Amiga models. Using such an IDE
858 doubler, you can connect up to four instead of two IDE devices on
859 the Amiga's builtin IDE interface.
861 Note that the normal Amiga Gayle IDE driver may not work correctly
862 if you have an IDE doubler and don't enable this driver!
864 Say Y if you have an IDE doubler. The driver is enabled at kernel
865 runtime using the "ide=doubler" kernel boot parameter.
867 config BLK_DEV_BUDDHA
868 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
869 depends on ZORRO && EXPERIMENTAL
871 This is the IDE driver for the IDE interfaces on the Buddha,
872 Catweasel and X-Surf expansion boards. It supports up to two interfaces
873 on the Buddha, three on the Catweasel and two on the X-Surf.
875 Say Y if you have a Buddha or Catweasel expansion board and want to
876 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
877 to one of its IDE interfaces.
879 config BLK_DEV_FALCON_IDE
880 bool "Falcon IDE interface support"
883 This is the IDE driver for the builtin IDE interface on the Atari
884 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
885 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
888 config BLK_DEV_MAC_IDE
889 bool "Macintosh Quadra/Powerbook IDE interface support"
892 This is the IDE driver for the builtin IDE interface on some m68k
893 Macintosh models. It supports both the `Quadra style' (used in
894 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
895 (used in the Powerbook 150 and 190 models) IDE interface.
897 Say Y if you have such an Macintosh model and want to use IDE
898 devices (hard disks, CD-ROM drives, etc.) that are connected to the
899 builtin IDE interface.
901 config BLK_DEV_Q40IDE
902 bool "Q40/Q60 IDE interface support"
905 Enable the on-board IDE controller in the Q40/Q60. This should
906 normally be on; disable it only if you are running a custom hard
907 drive subsystem through an expansion card.
909 config BLK_DEV_MPC8xx_IDE
910 bool "MPC8xx IDE support"
913 This option provides support for IDE on Motorola MPC8xx Systems.
914 Please see 'Type of MPC8xx IDE interface' for details.
919 prompt "Type of MPC8xx IDE interface"
920 depends on BLK_DEV_MPC8xx_IDE
921 default IDE_8xx_PCCARD
923 config IDE_8xx_PCCARD
926 Select how the IDE devices are connected to the MPC8xx system:
928 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
929 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
930 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
933 8xx_DIRECT is used for directly connected IDE devices using the 8xx
934 internal PCMCIA interface (example: IVMS8 systems)
936 EXT_DIRECT is used for IDE devices directly connected to the 8xx
937 bus using some glue logic, but _not_ the 8xx internal
938 PCMCIA interface (example: IDIF860 systems)
940 config IDE_8xx_DIRECT
943 config IDE_EXT_DIRECT
950 bool "Other IDE chipset support"
953 Say Y here if you want to include enhanced support for various IDE
954 interface chipsets used on motherboards and add-on cards. You can
955 then pick your particular IDE chip from among the following options.
956 This enhanced support may be necessary for Linux to be able to
957 access the 3rd/4th drives in some systems. It may also enable
958 setting of higher speed I/O rates to improve system performance with
959 these chipsets. Most of these also require special kernel boot
960 parameters to actually turn on the support at runtime; you can find
961 a list of these in the file <file:Documentation/ide.txt>.
963 People with SCSI-only systems can say N here.
967 comment "Note: most of these also require special kernel boot parameters"
969 config BLK_DEV_4DRIVES
970 bool "Generic 4 drives/port support"
972 Certain older chipsets, including the Tekram 690CD, use a single set
973 of I/O ports at 0x1f0 to control up to four drives, instead of the
974 customary two drives per port. Support for this can be enabled at
975 runtime using the "ide0=four" kernel boot parameter if you say Y
978 config BLK_DEV_ALI14XX
979 tristate "ALI M14xx support"
981 This driver is enabled at runtime using the "ide0=ali14xx" kernel
982 boot parameter. It enables support for the secondary IDE interface
983 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
984 I/O speeds to be set as well. See the files
985 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
988 config BLK_DEV_DTC2278
989 tristate "DTC-2278 support"
991 This driver is enabled at runtime using the "ide0=dtc2278" kernel
992 boot parameter. It enables support for the secondary IDE interface
993 of the DTC-2278 card, and permits faster I/O speeds to be set as
994 well. See the <file:Documentation/ide.txt> and
995 <file:drivers/ide/legacy/dtc2278.c> files for more info.
997 config BLK_DEV_HT6560B
998 tristate "Holtek HT6560B support"
1000 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1001 boot parameter. It enables support for the secondary IDE interface
1002 of the Holtek card, and permits faster I/O speeds to be set as well.
1003 See the <file:Documentation/ide.txt> and
1004 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1006 config BLK_DEV_PDC4030
1007 tristate "PROMISE DC4030 support (EXPERIMENTAL)"
1008 depends on BLK_DEV_IDEDISK && EXPERIMENTAL
1010 This driver provides support for the secondary IDE interface and
1011 cache of the original Promise IDE chipsets, e.g. DC4030 and DC5030.
1012 It is nothing to do with the later range of Promise UDMA chipsets -
1013 see the PDC_202XX support for these. CD-ROM and TAPE devices are not
1014 supported (and probably never will be since I don't think the cards
1015 support them). This driver is enabled at runtime using the "ide0=dc4030"
1016 or "ide1=dc4030" kernel boot parameter. See the
1017 <file:drivers/ide/legacy/pdc4030.c> file for more info.
1019 config BLK_DEV_QD65XX
1020 tristate "QDI QD65xx support"
1022 This driver is enabled at runtime using the "ide0=qd65xx" kernel
1023 boot parameter. It permits faster I/O speeds to be set. See the
1024 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
1027 config BLK_DEV_UMC8672
1028 tristate "UMC-8672 support"
1030 This driver is enabled at runtime using the "ide0=umc8672" kernel
1031 boot parameter. It enables support for the secondary IDE interface
1032 of the UMC-8672, and permits faster I/O speeds to be set as well.
1033 See the files <file:Documentation/ide.txt> and
1034 <file:drivers/ide/legacy/umc8672.c> for more info.
1038 config BLK_DEV_IDEDMA
1039 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1042 bool "IGNORE word93 Validation BITS"
1043 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1045 There are unclear terms in ATA-4 and ATA-5 standards how certain
1046 hardware (an 80c ribbon) should be detected. Different interpretations
1047 of the standards have been released in hardware. This causes problems:
1048 for example, a host with Ultra Mode 4 (or higher) will not run
1049 in that mode with an 80c ribbon.
1051 If you are experiencing compatibility or performance problems, you
1052 MAY try to answering Y here. However, it does not necessarily solve
1053 any of your problems, it could even cause more of them.
1055 It is normally safe to answer Y; however, the default is N.
1058 def_bool IDEDMA_PCI_AUTO || BLK_DEV_IDEDMA_PMAC_AUTO || IDEDMA_ICS_AUTO
1062 config BLK_DEV_HD_ONLY
1063 bool "Old hard disk (MFM/RLL/IDE) driver"
1064 depends on BLK_DEV_IDE=n
1066 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1067 the newer enhanced driver, but this old one is still around for two
1068 reasons. Some older systems have strange timing problems and seem to
1069 work only with the old driver (which itself does not work with some
1070 newer systems). The other reason is that the old driver is smaller,
1071 since it lacks the enhanced functionality of the new one. This makes
1072 it a good choice for systems with very tight memory restrictions, or
1073 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1074 driver can save 13 KB or so of kernel memory.
1076 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1077 instead of this one. For more detailed information, read the
1078 Disk-HOWTO, available from
1079 <http://www.tldp.org/docs.html#howto>.
1082 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY