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 || 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_IDEDISK
117 tristate "Include IDE/ATA-2 DISK support"
119 This will include enhanced support for MFM/RLL/IDE hard disks. If
120 you have a MFM/RLL/IDE disk, and there is no special reason to use
121 the old hard disk driver instead, say Y. If you have an SCSI-only
122 system, you can say N here.
124 To compile this driver as a module, choose M here: the
125 module will be called ide-disk.
126 Do not compile this driver as a module if your root file system
127 (the one containing the directory /) is located on the IDE disk.
131 config IDEDISK_MULTI_MODE
132 bool "Use multi-mode by default"
133 depends on BLK_DEV_IDEDISK
135 If you get this error, try to say Y here:
137 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
138 hda: set_multmode: error=0x04 { DriveStatusError }
143 tristate "PCMCIA IDE support"
146 Support for outboard IDE disks, tape drives, and CD-ROM drives
147 connected through a PCMCIA card.
150 tristate "Include IDE/ATAPI CDROM support"
152 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
153 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
154 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
155 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
156 double(2X) or better speed drives.
158 If you say Y here, the CD-ROM drive will be identified at boot time
159 along with other IDE devices, as "hdb" or "hdc", or something
160 similar (check the boot messages with dmesg). If this is your only
161 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
162 to say Y or M to "ISO 9660 CD-ROM file system support".
164 Note that older versions of LILO (LInux LOader) cannot properly deal
165 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
166 <http://lilo.go.dyndns.org/>.
168 To compile this driver as a module, choose M here: the
169 module will be called ide-cd.
171 config BLK_DEV_IDETAPE
172 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
173 depends on EXPERIMENTAL
175 If you have an IDE tape drive using the ATAPI protocol, say Y.
176 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
177 similar to the SCSI protocol. If you have an SCSI tape drive
178 however, you can say N here.
180 You should also say Y if you have an OnStream DI-30 tape drive; this
181 will not work with the SCSI protocol, until there is support for the
182 SC-30 and SC-50 versions.
184 If you say Y here, the tape drive will be identified at boot time
185 along with other IDE devices, as "hdb" or "hdc", or something
186 similar, and will be mapped to a character device such as "ht0"
187 (check the boot messages with dmesg). Be sure to consult the
188 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
189 for usage information.
191 To compile this driver as a module, choose M here: the
192 module will be called ide-tape.
194 config BLK_DEV_IDEFLOPPY
195 tristate "Include IDE/ATAPI FLOPPY support"
197 If you have an IDE floppy drive which uses the ATAPI protocol,
198 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
199 drives, similar to the SCSI protocol.
201 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
202 this driver. For information about jumper settings and the question
203 of when a ZIP drive uses a partition table, see
204 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
205 (ATAPI PD-CD/CDR drives are not supported by this driver; support
206 for PD-CD/CDR drives is available if you answer Y to
207 "SCSI emulation support", below).
209 If you say Y here, the FLOPPY drive will be identified along with
210 other IDE devices, as "hdb" or "hdc", or something similar (check
211 the boot messages with dmesg).
213 To compile this driver as a module, choose M here: the
214 module will be called ide-floppy.
216 config BLK_DEV_IDESCSI
217 tristate "SCSI emulation support"
220 WARNING: ide-scsi is no longer needed for cd writing applications!
221 The 2.6 kernel supports direct writing to ide-cd, which eliminates
222 the need for ide-scsi + the entire scsi stack just for writing a
223 cd. The new method is more efficient in every way.
225 This will provide SCSI host adapter emulation for IDE ATAPI devices,
226 and will allow you to use a SCSI device driver instead of a native
229 This is useful if you have an ATAPI device for which no native
230 driver has been written (for example, an ATAPI PD-CD drive);
231 you can then use this emulation together with an appropriate SCSI
232 device driver. In order to do this, say Y here and to "SCSI support"
233 and "SCSI generic support", below. You must then provide the kernel
234 command line "hdx=ide-scsi" (try "man bootparam" or see the
235 documentation of your boot loader (lilo or loadlin) about how to
236 pass options to the kernel at boot time) for devices if you want the
237 native EIDE sub-drivers to skip over the native support, so that
238 this SCSI emulation can be used instead.
240 Note that this option does NOT allow you to attach SCSI devices to a
241 box that doesn't have a SCSI host adapter installed.
243 If both this SCSI emulation and native ATAPI support are compiled
244 into the kernel, the native support will be used.
246 config IDE_TASK_IOCTL
247 bool "IDE Taskfile Access"
249 This is a direct raw access to the media. It is a complex but
250 elegant solution to test and validate the domain of the hardware and
251 perform below the driver data recover if needed. This is the most
252 basic form of media-forensics.
254 If you are unsure, say N here.
256 config IDE_TASKFILE_IO
257 bool 'IDE Taskfile IO (EXPERIMENTAL)'
258 depends on EXPERIMENTAL
261 Use new taskfile IO code.
263 It is safe to say Y to this question, in most cases.
265 comment "IDE chipset support/bugfixes"
268 tristate "generic/default IDE chipset support"
273 config BLK_DEV_CMD640
274 bool "CMD640 chipset bugfix/support"
277 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
278 Pentium motherboards, usually in combination with a "Neptune" or
279 "SiS" chipset. Unfortunately, it has a number of rather nasty
280 design flaws that can cause severe data corruption under many common
281 conditions. Say Y here to include code which tries to automatically
282 detect and correct the problems under Linux. This option also
283 enables access to the secondary IDE ports in some CMD640 based
286 This driver will work automatically in PCI based systems (most new
287 systems have PCI slots). But if your system uses VESA local bus
288 (VLB) instead of PCI, you must also supply a kernel boot parameter
289 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
290 bootparam" or see the documentation of your boot loader about how to
291 pass options to the kernel.)
293 The CMD640 chip is also used on add-in cards by Acculogic, and on
294 the "CSA-6400E PCI to IDE controller" that some people have. For
295 details, read <file:Documentation/ide.txt>.
297 config BLK_DEV_CMD640_ENHANCED
298 bool "CMD640 enhanced support"
299 depends on BLK_DEV_CMD640
301 This option includes support for setting/autotuning PIO modes and
302 prefetch on CMD640 IDE interfaces. For details, read
303 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
304 and your BIOS does not already do this for you, then say Y here.
307 config BLK_DEV_IDEPNP
308 bool "PNP EIDE support"
311 If you have a PnP (Plug and Play) compatible EIDE card and
312 would like the kernel to automatically detect and activate
315 config BLK_DEV_IDEPCI
316 bool "PCI IDE chipset support" if PCI
317 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
319 Say Y here for PCI systems which use IDE drive(s).
320 This option helps the IDE driver to automatically detect and
321 configure all PCI-based IDE interfaces in your system.
323 config IDEPCI_SHARE_IRQ
324 bool "Sharing PCI IDE interrupts support"
325 depends on PCI && BLK_DEV_IDEPCI
327 Some ATA/IDE chipsets have hardware support which allows for
328 sharing a single IRQ with other cards. To enable support for
329 this in the ATA/IDE driver, say Y here.
331 It is safe to say Y to this question, in most cases.
334 config BLK_DEV_OFFBOARD
335 bool "Boot off-board chipsets first support"
336 depends on PCI && BLK_DEV_IDEPCI
338 Normally, IDE controllers built into the motherboard (on-board
339 controllers) are assigned to ide0 and ide1 while those on add-in PCI
340 cards (off-board controllers) are relegated to ide2 and ide3.
341 Answering Y here will allow you to reverse the situation, with
342 off-board controllers on ide0/1 and on-board controllers on ide2/3.
343 This can improve the usability of some boot managers such as lilo
344 when booting from a drive on an off-board controller.
346 If you say Y here, and you actually want to reverse the device scan
347 order as explained above, you also need to issue the kernel command
348 line option "ide=reverse". (Try "man bootparam" or see the
349 documentation of your boot loader (lilo or loadlin) about how to
350 pass options to the kernel at boot time.)
352 Note that, if you do this, the order of the hd* devices will be
353 rearranged which may require modification of fstab and other files.
357 config BLK_DEV_GENERIC
358 tristate "Generic PCI IDE Chipset Support"
359 depends on BLK_DEV_IDEPCI
361 config BLK_DEV_OPTI621
362 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
363 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
365 This is a driver for the OPTi 82C621 EIDE controller.
366 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
368 config BLK_DEV_RZ1000
369 tristate "RZ1000 chipset bugfix/support"
370 depends on PCI && BLK_DEV_IDEPCI && X86
372 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
373 Pentium motherboards, usually along with the "Neptune" chipset.
374 Unfortunately, it has a rather nasty design flaw that can cause
375 severe data corruption under many conditions. Say Y here to include
376 code which automatically detects and corrects the problem under
377 Linux. This may slow disk throughput by a few percent, but at least
378 things will operate 100% reliably.
380 config BLK_DEV_SL82C105
381 tristate "Winbond SL82c105 support"
382 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
384 If you have a Winbond SL82c105 IDE controller, say Y here to enable
385 special configuration for this chip. This is common on various CHRP
386 motherboards, but could be used elsewhere. If in doubt, say Y.
388 config BLK_DEV_IDEDMA_PCI
389 bool "Generic PCI bus-master DMA support"
390 depends on PCI && BLK_DEV_IDEPCI
392 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
393 is capable of bus-master DMA operation (most Pentium PCI systems),
394 you will want to say Y here to reduce CPU overhead. You can then use
395 the "hdparm" utility to enable DMA for drives for which it was not
396 enabled automatically. By default, DMA is not enabled automatically
397 for these drives, but you can change that by saying Y to the
398 following question "Use DMA by default when available". You can get
399 the latest version of the hdparm utility from
400 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
402 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
403 and the file <file:Documentation/ide.txt> for more information.
405 It is safe to say Y to this question.
407 if BLK_DEV_IDEDMA_PCI
409 config BLK_DEV_IDEDMA_FORCED
410 bool "Force enable legacy 2.0.X HOSTS to use DMA"
412 This is an old piece of lost code from Linux 2.0 Kernels.
414 Generally say N here.
416 config IDEDMA_PCI_AUTO
417 bool "Use PCI DMA by default when available"
419 Prior to kernel version 2.1.112, Linux used to automatically use
420 DMA for IDE drives and chipsets which support it. Due to concerns
421 about a couple of cases where buggy hardware may have caused damage,
422 the default is now to NOT use DMA automatically. To revert to the
423 previous behaviour, say Y to this question.
425 If you suspect your hardware is at all flakey, say N here.
426 Do NOT email the IDE kernel people regarding this issue!
428 It is normally safe to answer Y to this question unless your
429 motherboard uses a VIA VP2 chipset, in which case you should say N.
431 config IDEDMA_ONLYDISK
432 bool "Enable DMA only for disks "
433 depends on IDEDMA_PCI_AUTO
435 This is used if you know your ATAPI Devices are going to fail DMA
438 Generally say N here.
442 depends on PCI && BLK_DEV_IDEPCI
443 default BLK_DEV_IDEDMA_PCI
445 config BLK_DEV_AEC62XX
446 tristate "AEC62XX chipset support"
448 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
449 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
450 speeds and to configure the chip to optimum performance.
452 config BLK_DEV_ALI15X3
453 tristate "ALI M15x3 chipset support"
455 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
456 onboard chipsets. It also tests for Simplex mode and enables
457 normal dual channel support.
459 If you say Y here, you also need to say Y to "Use DMA by default
460 when available", above. Please read the comments at the top of
461 <file:drivers/ide/pci/alim15x3.c>.
466 bool "ALI M15x3 WDC support (DANGEROUS)"
467 depends on BLK_DEV_ALI15X3
469 This allows for UltraDMA support for WDC drives that ignore CRC
470 checking. You are a fool for enabling this option, but there have
471 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
472 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
475 Using this option can allow WDC drives to run at ATA-4/5 transfer
476 rates with only an ATA-2 support structure.
480 config BLK_DEV_AMD74XX
481 tristate "AMD and nVidia IDE support"
483 This driver adds explicit support for AMD-7xx and AMD-8111 chips
484 and also for the nVidia nForce chip. This allows the kernel to
485 change PIO, DMA and UDMA speeds and to configure the chip to
488 config BLK_DEV_ATIIXP
489 tristate "ATI IXP chipset IDE support"
492 This driver adds explicit support for ATI IXP chipset.
493 This allows the kernel to change PIO, DMA and UDMA speeds
494 and to configure the chip to optimum performance.
496 Say Y here if you have an ATI IXP chipset IDE controller.
498 config BLK_DEV_CMD64X
499 tristate "CMD64{3|6|8|9} chipset support"
501 Say Y here if you have an IDE controller which uses any of these
502 chipsets: CMD643, CMD646, or CMD648.
504 config BLK_DEV_TRIFLEX
505 tristate "Compaq Triflex IDE support"
507 Say Y here if you have a Compaq Triflex IDE controller, such
508 as those commonly found on Compaq Pentium-Pro systems
510 config BLK_DEV_CY82C693
511 tristate "CY82C693 chipset support"
513 This driver adds detection and support for the CY82C693 chipset
514 used on Digital's PC-Alpha 164SX boards.
516 If you say Y here, you need to say Y to "Use DMA by default
517 when available" as well.
519 config BLK_DEV_CS5520
520 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
521 depends on EXPERIMENTAL
523 Include support for PIO tuning an virtual DMA on the Cyrix MediaGX
524 5510/5520 chipset. This will automatically be detected and
527 It is safe to say Y to this question.
529 config BLK_DEV_CS5530
530 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
532 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
533 will automatically be detected and configured if found.
535 It is safe to say Y to this question.
537 config BLK_DEV_HPT34X
538 tristate "HPT34X chipset support"
540 This driver adds up to 4 more EIDE devices sharing a single
541 interrupt. The HPT343 chipset in its current form is a non-bootable
542 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
543 PCI UDMA controllers. This driver requires dynamic tuning of the
544 chipset during the ide-probe at boot time. It is reported to support
545 DVD II drives, by the manufacturer.
547 config HPT34X_AUTODMA
548 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
549 depends on BLK_DEV_HPT34X && EXPERIMENTAL
551 This is a dangerous thing to attempt currently! Please read the
552 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
553 here, then say Y to "Use DMA by default when available" as well.
557 config BLK_DEV_HPT366
558 tristate "HPT36X/37X chipset support"
560 HPT366 is an Ultra DMA chipset for ATA-66.
561 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
562 HPT370 is an Ultra DMA chipset for ATA-100.
563 HPT372 is an Ultra DMA chipset for ATA-100.
564 HPT374 is an Ultra DMA chipset for ATA-100.
566 This driver adds up to 4 more EIDE devices sharing a single
569 The HPT366 chipset in its current form is bootable. One solution
570 for this problem are special LILO commands for redirecting the
571 reference to device 0x80. The other solution is to say Y to "Boot
572 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
573 your mother board has the chipset natively mounted. Regardless one
574 should use the fore mentioned option and call at LILO or include
575 "ide=reverse" in LILO's append-line.
577 This driver requires dynamic tuning of the chipset during the
578 ide-probe at boot. It is reported to support DVD II drives, by the
581 config BLK_DEV_SC1200
582 tristate "National SCx200 chipset support"
584 This driver adds support for the built in IDE on the National
585 SCx200 series of embedded x86 "Geode" systems
588 tristate "Intel PIIXn chipsets support"
590 This driver adds explicit support for Intel PIIX and ICH chips
591 and also for the Efar Victory66 (slc90e66) chip. This allows
592 the kernel to change PIO, DMA and UDMA speeds and to configure
593 the chip to optimum performance.
595 config BLK_DEV_IT8172
596 bool "IT8172 IDE support"
597 depends on (MIPS_ITE8172 || MIPS_IVR)
599 Say Y here to support the on-board IDE controller on the Integrated
600 Technology Express, Inc. ITE8172 SBC. Vendor page at
601 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
602 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
604 config BLK_DEV_NS87415
605 tristate "NS87415 chipset support"
607 This driver adds detection and support for the NS87415 chip
608 (used in SPARC64, among others).
610 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
612 config BLK_DEV_PDC202XX_OLD
613 tristate "PROMISE PDC202{46|62|65|67} support"
615 Promise Ultra33 or PDC20246
616 Promise Ultra66 or PDC20262
617 Promise Ultra100 or PDC20265/PDC20267/PDC20268
619 This driver adds up to 4 more EIDE devices sharing a single
620 interrupt. This add-on card is a bootable PCI UDMA controller. Since
621 multiple cards can be installed and there are BIOS ROM problems that
622 happen if the BIOS revisions of all installed cards (three-max) do
623 not match, the driver attempts to do dynamic tuning of the chipset
624 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
625 for more than one card. This card may require that you say Y to
626 "Special UDMA Feature".
628 If you say Y here, you need to say Y to "Use DMA by default when
631 Please read the comments at the top of
632 <file:drivers/ide/pci/pdc202xx_old.c>.
636 config PDC202XX_BURST
637 bool "Special UDMA Feature"
638 depends on BLK_DEV_PDC202XX_OLD
640 This option causes the pdc202xx driver to enable UDMA modes on the
641 PDC202xx even when the PDC202xx BIOS has not done so.
643 It was originally designed for the PDC20246/Ultra33, whose BIOS will
644 only setup UDMA on the first two PDC20246 cards. It has also been
645 used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
646 when the PDC20265 BIOS has been disabled (for faster boot up).
648 Please read the comments at the top of
649 <file:drivers/ide/pci/pdc202xx_old.c>.
653 config BLK_DEV_PDC202XX_NEW
654 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
656 # FIXME - probably wants to be one for old and for new
657 config PDC202XX_FORCE
658 bool "Enable controller even if disabled by BIOS"
659 depends on BLK_DEV_PDC202XX_NEW
661 Enable the PDC202xx controller even if it has been disabled in the BIOS setup.
664 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
666 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
669 config BLK_DEV_SGIIOC4
670 tristate "Silicon Graphics IOC4 chipset support"
671 depends on IA64_SGI_SN2 || IA64_GENERIC
673 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
674 chipset, which has one channel and can support two devices.
675 Please say Y here if you have an Altix System from SGI.
677 config BLK_DEV_SIIMAGE
678 tristate "Silicon Image chipset support"
680 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
681 3112 (Serial ATA) chips.
683 config BLK_DEV_SIS5513
684 tristate "SiS5513 chipset support"
687 This driver ensures (U)DMA support for SIS5513 chipset family based
690 The following chipsets are supported:
691 ATA16: SiS5511, SiS5513
692 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
693 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
694 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
697 If you say Y here, you need to say Y to "Use DMA by default when
700 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
702 config BLK_DEV_SLC90E66
703 tristate "SLC90E66 chipset support"
705 This driver ensures (U)DMA support for Victroy66 SouthBridges for
706 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
707 The nice thing about it is that you can mix Ultra/DMA/PIO devices
708 and it will handle timing cycles. Since this is an improved
709 look-a-like to the PIIX4 it should be a nice addition.
711 If you say Y here, you need to say Y to "Use DMA by default when
714 Please read the comments at the top of
715 <file:drivers/ide/pci/slc90e66.c>.
717 config BLK_DEV_TRM290
718 tristate "Tekram TRM290 chipset support"
720 This driver adds support for bus master DMA transfers
721 using the Tekram TRM290 PCI IDE chip. Volunteers are
722 needed for further tweaking and development.
723 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
725 config BLK_DEV_VIA82CXXX
726 tristate "VIA82CXXX chipset support"
728 This driver adds explicit support for VIA BusMastering IDE chips.
729 This allows the kernel to change PIO, DMA and UDMA speeds and to
730 configure the chip to optimum performance.
734 config BLK_DEV_IDE_PMAC
735 bool "Builtin PowerMac IDE support"
738 This driver provides support for the built-in IDE controller on
739 most of the recent Apple Power Macintoshes and PowerBooks.
742 config BLK_DEV_IDE_PMAC_ATA100FIRST
743 bool "Probe internal ATA/100 (Kauai) first"
744 depends on BLK_DEV_IDE_PMAC
746 This option will cause the ATA/100 controller found in UniNorth2
747 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
748 to be probed before the ATA/66 and ATA/33 controllers. Without
749 these, those machine used to have the hard disk on hdc and the
750 CD-ROM on hda. This option changes this to more natural hda for
751 hard disk and hdc for CD-ROM.
753 config BLK_DEV_IDEDMA_PMAC
754 bool "PowerMac IDE DMA support"
755 depends on BLK_DEV_IDE_PMAC
757 This option allows the driver for the built-in IDE controller on
758 Power Macintoshes and PowerBooks to use DMA (direct memory access)
759 to transfer data to and from memory. Saying Y is safe and improves
762 config BLK_DEV_IDE_PMAC_BLINK
763 bool "Blink laptop LED on drive activity"
764 depends on BLK_DEV_IDE_PMAC && ADB_PMU
766 This option enables the use of the sleep LED as a hard drive
769 config BLK_DEV_IDEDMA_PMAC_AUTO
770 bool "Use DMA by default"
771 depends on BLK_DEV_IDEDMA_PMAC
773 This option allows the driver for the built-in IDE controller on
774 Power Macintoshes and PowerBooks to use DMA automatically, without
775 it having to be explicitly enabled. This option is provided because
776 of concerns about a couple of cases where using DMA on buggy PC
777 hardware may have caused damage. Saying Y should be safe on all
781 def_bool ARM && (ARCH_A5K || ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
783 config BLK_DEV_IDE_ICSIDE
784 tristate "ICS IDE interface support"
785 depends on ARM && ARCH_ACORN
787 On Acorn systems, say Y here if you wish to use the ICS IDE
788 interface card. This is not required for ICS partition support.
789 If you are unsure, say N to this.
791 config BLK_DEV_IDEDMA_ICS
792 bool "ICS DMA support"
793 depends on BLK_DEV_IDE_ICSIDE
795 Say Y here if you want to add DMA (Direct Memory Access) support to
798 config IDEDMA_ICS_AUTO
799 bool "Use ICS DMA by default"
800 depends on BLK_DEV_IDEDMA_ICS
802 Prior to kernel version 2.1.112, Linux used to automatically use
803 DMA for IDE drives and chipsets which support it. Due to concerns
804 about a couple of cases where buggy hardware may have caused damage,
805 the default is now to NOT use DMA automatically. To revert to the
806 previous behaviour, say Y to this question.
808 If you suspect your hardware is at all flakey, say N here.
809 Do NOT email the IDE kernel people regarding this issue!
811 config BLK_DEV_IDE_RAPIDE
812 tristate "RapIDE interface support"
813 depends on ARM && ARCH_ACORN
815 Say Y here if you want to support the Yellowstone RapIDE controller
816 manufactured for use with Acorn computers.
819 bool "Amiga Gayle IDE interface support"
822 This is the IDE driver for the Amiga Gayle IDE interface. It supports
823 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
824 This includes builtin IDE interfaces on some Amiga models (A600,
825 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
826 bus (M-Tech E-Matrix 530 expansion card).
827 Say Y if you have an Amiga with a Gayle IDE interface and want to use
828 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
830 Note that you also have to enable Zorro bus support if you want to
831 use Gayle IDE interfaces on the Zorro expansion bus.
833 config BLK_DEV_IDEDOUBLER
834 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
835 depends on BLK_DEV_GAYLE && EXPERIMENTAL
837 This driver provides support for the so-called `IDE doublers' (made
838 by various manufacturers, e.g. Eyetech) that can be connected to the
839 builtin IDE interface of some Amiga models. Using such an IDE
840 doubler, you can connect up to four instead of two IDE devices on
841 the Amiga's builtin IDE interface.
843 Note that the normal Amiga Gayle IDE driver may not work correctly
844 if you have an IDE doubler and don't enable this driver!
846 Say Y if you have an IDE doubler. The driver is enabled at kernel
847 runtime using the "ide=doubler" kernel boot parameter.
849 config BLK_DEV_BUDDHA
850 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
851 depends on ZORRO && EXPERIMENTAL
853 This is the IDE driver for the IDE interfaces on the Buddha,
854 Catweasel and X-Surf expansion boards. It supports up to two interfaces
855 on the Buddha, three on the Catweasel and two on the X-Surf.
857 Say Y if you have a Buddha or Catweasel expansion board and want to
858 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
859 to one of its IDE interfaces.
861 config BLK_DEV_FALCON_IDE
862 bool "Falcon IDE interface support"
865 This is the IDE driver for the builtin IDE interface on the Atari
866 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
867 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
870 config BLK_DEV_MAC_IDE
871 bool "Macintosh Quadra/Powerbook IDE interface support"
874 This is the IDE driver for the builtin IDE interface on some m68k
875 Macintosh models. It supports both the `Quadra style' (used in
876 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
877 (used in the Powerbook 150 and 190 models) IDE interface.
879 Say Y if you have such an Macintosh model and want to use IDE
880 devices (hard disks, CD-ROM drives, etc.) that are connected to the
881 builtin IDE interface.
883 config BLK_DEV_Q40IDE
884 bool "Q40/Q60 IDE interface support"
887 Enable the on-board IDE controller in the Q40/Q60. This should
888 normally be on; disable it only if you are running a custom hard
889 drive subsystem through an expansion card.
891 config BLK_DEV_MPC8xx_IDE
892 bool "MPC8xx IDE support"
895 This option provides support for IDE on Motorola MPC8xx Systems.
896 Please see 'Type of MPC8xx IDE interface' for details.
901 prompt "Type of MPC8xx IDE interface"
902 depends on BLK_DEV_MPC8xx_IDE
903 default IDE_8xx_PCCARD
905 config IDE_8xx_PCCARD
908 Select how the IDE devices are connected to the MPC8xx system:
910 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
911 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
912 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
915 8xx_DIRECT is used for directly connected IDE devices using the 8xx
916 internal PCMCIA interface (example: IVMS8 systems)
918 EXT_DIRECT is used for IDE devices directly connected to the 8xx
919 bus using some glue logic, but _not_ the 8xx internal
920 PCMCIA interface (example: IDIF860 systems)
922 config IDE_8xx_DIRECT
925 config IDE_EXT_DIRECT
932 bool "Other IDE chipset support"
935 Say Y here if you want to include enhanced support for various IDE
936 interface chipsets used on motherboards and add-on cards. You can
937 then pick your particular IDE chip from among the following options.
938 This enhanced support may be necessary for Linux to be able to
939 access the 3rd/4th drives in some systems. It may also enable
940 setting of higher speed I/O rates to improve system performance with
941 these chipsets. Most of these also require special kernel boot
942 parameters to actually turn on the support at runtime; you can find
943 a list of these in the file <file:Documentation/ide.txt>.
945 People with SCSI-only systems can say N here.
949 comment "Note: most of these also require special kernel boot parameters"
951 config BLK_DEV_4DRIVES
952 bool "Generic 4 drives/port support"
954 Certain older chipsets, including the Tekram 690CD, use a single set
955 of I/O ports at 0x1f0 to control up to four drives, instead of the
956 customary two drives per port. Support for this can be enabled at
957 runtime using the "ide0=four" kernel boot parameter if you say Y
960 config BLK_DEV_ALI14XX
961 tristate "ALI M14xx support"
963 This driver is enabled at runtime using the "ide0=ali14xx" kernel
964 boot parameter. It enables support for the secondary IDE interface
965 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
966 I/O speeds to be set as well. See the files
967 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
970 config BLK_DEV_DTC2278
971 tristate "DTC-2278 support"
973 This driver is enabled at runtime using the "ide0=dtc2278" kernel
974 boot parameter. It enables support for the secondary IDE interface
975 of the DTC-2278 card, and permits faster I/O speeds to be set as
976 well. See the <file:Documentation/ide.txt> and
977 <file:drivers/ide/legacy/dtc2278.c> files for more info.
979 config BLK_DEV_HT6560B
980 tristate "Holtek HT6560B support"
982 This driver is enabled at runtime using the "ide0=ht6560b" kernel
983 boot parameter. It enables support for the secondary IDE interface
984 of the Holtek card, and permits faster I/O speeds to be set as well.
985 See the <file:Documentation/ide.txt> and
986 <file:drivers/ide/legacy/ht6560b.c> files for more info.
988 config BLK_DEV_PDC4030
989 tristate "PROMISE DC4030 support (EXPERIMENTAL)"
990 depends on BLK_DEV_IDEDISK && EXPERIMENTAL
992 This driver provides support for the secondary IDE interface and
993 cache of the original Promise IDE chipsets, e.g. DC4030 and DC5030.
994 It is nothing to do with the later range of Promise UDMA chipsets -
995 see the PDC_202XX support for these. CD-ROM and TAPE devices are not
996 supported (and probably never will be since I don't think the cards
997 support them). This driver is enabled at runtime using the "ide0=dc4030"
998 or "ide1=dc4030" kernel boot parameter. See the
999 <file:drivers/ide/legacy/pdc4030.c> file for more info.
1001 config BLK_DEV_QD65XX
1002 tristate "QDI QD65xx support"
1004 This driver is enabled at runtime using the "ide0=qd65xx" kernel
1005 boot parameter. It permits faster I/O speeds to be set. See the
1006 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
1009 config BLK_DEV_UMC8672
1010 tristate "UMC-8672 support"
1012 This driver is enabled at runtime using the "ide0=umc8672" kernel
1013 boot parameter. It enables support for the secondary IDE interface
1014 of the UMC-8672, and permits faster I/O speeds to be set as well.
1015 See the files <file:Documentation/ide.txt> and
1016 <file:drivers/ide/legacy/umc8672.c> for more info.
1020 config BLK_DEV_IDEDMA
1021 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1024 bool "IGNORE word93 Validation BITS"
1025 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1027 There are unclear terms in ATA-4 and ATA-5 standards how certain
1028 hardware (an 80c ribbon) should be detected. Different interpretations
1029 of the standards have been released in hardware. This causes problems:
1030 for example, a host with Ultra Mode 4 (or higher) will not run
1031 in that mode with an 80c ribbon.
1033 If you are experiencing compatibility or performance problems, you
1034 MAY try to answering Y here. However, it does not necessarily solve
1035 any of your problems, it could even cause more of them.
1037 It is normally safe to answer Y; however, the default is N.
1040 def_bool IDEDMA_PCI_AUTO || BLK_DEV_IDEDMA_PMAC_AUTO || IDEDMA_ICS_AUTO
1044 config BLK_DEV_HD_ONLY
1045 bool "Old hard disk (MFM/RLL/IDE) driver"
1046 depends on BLK_DEV_IDE=n
1048 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1049 the newer enhanced driver, but this old one is still around for two
1050 reasons. Some older systems have strange timing problems and seem to
1051 work only with the old driver (which itself does not work with some
1052 newer systems). The other reason is that the old driver is smaller,
1053 since it lacks the enhanced functionality of the new one. This makes
1054 it a good choice for systems with very tight memory restrictions, or
1055 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1056 driver can save 13 KB or so of kernel memory.
1058 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1059 instead of this one. For more detailed information, read the
1060 Disk-HOWTO, available from
1061 <http://www.tldp.org/docs.html#howto>.
1064 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY