2 # IDE ATA ATAPI Block device driver configuration
5 # Select HAVE_IDE if IDE is supported
10 tristate "ATA/ATAPI/MFM/RLL support"
14 If you say Y here, your kernel will be able to manage low cost mass
15 storage units such as ATA/(E)IDE and ATAPI units. The most common
16 cases are IDE hard drives and ATAPI CD-ROM drives.
18 If your system is pure SCSI and doesn't use these interfaces, you
21 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
22 for mass storage units such as hard disks. It was designed by
23 Western Digital and Compaq Computer in 1984. It was then named
24 ST506. Quite a number of disks use the IDE interface.
26 AT Attachment (ATA) is the superset of the IDE specifications.
27 ST506 was also called ATA-1.
29 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
30 ATA-3. It provides support for larger disks (up to 8.4GB by means of
31 the LBA standard), more disks (4 instead of 2) and for other mass
32 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
33 ATA-4 and provides faster (and more CPU friendly) transfer modes
34 than previous PIO (Programmed processor Input/Output) from previous
35 ATA/IDE standards by means of fast DMA controllers.
37 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
38 CD-ROM drives, similar in many respects to the SCSI protocol.
40 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
41 designed in order to prevent data corruption and disk crash by
42 detecting pre hardware failure conditions (heat, access time, and
43 the like...). Disks built since June 1995 may follow this standard.
44 The kernel itself doesn't manage this; however there are quite a
45 number of user programs such as smart that can query the status of
46 SMART parameters from disk drives.
48 To compile this driver as a module, choose M here: the
49 module will be called ide.
51 For further information, please read <file:Documentation/ide/ide.txt>.
58 int "Max IDE interfaces"
59 depends on ALPHA || SUPERH || IA64 || EMBEDDED
63 This is the maximum number of IDE hardware interfaces that will
64 be supported by the driver. Make sure it is at least as high as
65 the number of IDE interfaces in your system.
68 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
70 If you say Y here, you will use the full-featured IDE driver to
71 control up to ten ATA/IDE interfaces, each being able to serve a
72 "master" and a "slave" device, for a total of up to twenty ATA/IDE
73 disk/cdrom/tape/floppy drives.
75 Useful information about large (>540 MB) IDE disks, multiple
76 interfaces, what to do if ATA/IDE devices are not automatically
77 detected, sound card ATA/IDE ports, module support, and other
78 topics, is contained in <file:Documentation/ide/ide.txt>. For detailed
79 information about hard drives, consult the Disk-HOWTO and the
80 Multi-Disk-HOWTO, available from
81 <http://www.tldp.org/docs.html#howto>.
83 To fine-tune ATA/IDE drive/interface parameters for improved
84 performance, look for the hdparm package at
85 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
87 To compile this driver as a module, choose M here and read
88 <file:Documentation/ide/ide.txt>. The module will be called ide-mod.
89 Do not compile this driver as a module if your root file system (the
90 one containing the directory /) is located on an IDE device.
92 If you have one or more IDE drives, say Y or M here. If your system
93 has no IDE drives, or if memory requirements are really tight, you
94 could say N here, and select the "Old hard disk driver" below
95 instead to save about 13 KB of memory in the kernel.
99 comment "Please see Documentation/ide/ide.txt for help/info on IDE drives"
107 config BLK_DEV_IDE_SATA
108 bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
111 There are two drivers for Serial ATA controllers.
113 The main driver, "libata", uses the SCSI subsystem
114 and supports most modern SATA controllers. In order to use it
115 you may take a look at "Serial ATA (prod) and Parallel ATA
116 (experimental) drivers".
118 The IDE driver (which you are currently configuring) supports
119 a few first-generation SATA controllers.
121 In order to eliminate conflicts between the two subsystems,
122 this config option enables the IDE driver's SATA support.
123 Normally this is disabled, as it is preferred that libata
124 supports SATA controllers, and this (IDE) driver supports
129 config BLK_DEV_IDEDISK
130 tristate "Include IDE/ATA-2 DISK support"
132 This will include enhanced support for MFM/RLL/IDE hard disks. If
133 you have a MFM/RLL/IDE disk, and there is no special reason to use
134 the old hard disk driver instead, say Y. If you have an SCSI-only
135 system, you can say N here.
137 To compile this driver as a module, choose M here: the
138 module will be called ide-disk.
139 Do not compile this driver as a module if your root file system
140 (the one containing the directory /) is located on the IDE disk.
144 config IDEDISK_MULTI_MODE
145 bool "Use multiple sector mode for Programmed Input/Output by default"
147 This setting is irrelevant for most IDE disks, with direct memory
148 access, to which multiple sector mode does not apply. Multiple sector
149 mode is a feature of most modern IDE hard drives, permitting the
150 transfer of multiple sectors per Programmed Input/Output interrupt,
151 rather than the usual one sector per interrupt. When this feature is
152 enabled, it can reduce operating system overhead for disk Programmed
153 Input/Output. On some systems, it also can increase the data
154 throughput of Programmed Input/Output. Some drives, however, seemed
155 to run slower with multiple sector mode enabled. Some drives claimed
156 to support multiple sector mode, but lost data at some settings.
157 Under rare circumstances, such failures could result in massive
158 filesystem corruption.
160 If you get the following error, try to say Y here:
162 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
163 hda: set_multmode: error=0x04 { DriveStatusError }
168 tristate "PCMCIA IDE support"
171 Support for Compact Flash cards, outboard IDE disks, tape drives,
172 and CD-ROM drives connected through a PCMCIA card.
174 config BLK_DEV_DELKIN
175 tristate "Cardbus IDE support (Delkin/ASKA/Workbit)"
176 depends on CARDBUS && PCI
178 Support for Delkin, ASKA, and Workbit Cardbus CompactFlash
179 Adapters. This may also work for similar SD and XD adapters.
182 tristate "Include IDE/ATAPI CDROM support"
184 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
185 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
186 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
187 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
188 double(2X) or better speed drives.
190 If you say Y here, the CD-ROM drive will be identified at boot time
191 along with other IDE devices, as "hdb" or "hdc", or something
192 similar (check the boot messages with dmesg). If this is your only
193 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
194 to say Y or M to "ISO 9660 CD-ROM file system support".
196 To compile this driver as a module, choose M here: the
197 module will be called ide-cd.
199 config BLK_DEV_IDECD_VERBOSE_ERRORS
200 bool "Verbose error logging for IDE/ATAPI CDROM driver" if EMBEDDED
201 depends on BLK_DEV_IDECD
204 Turn this on to have the driver print out the meanings of the
205 ATAPI error codes. This will use up additional 8kB of kernel-space
208 config BLK_DEV_IDETAPE
209 tristate "Include IDE/ATAPI TAPE support"
212 If you have an IDE tape drive using the ATAPI protocol, say Y.
213 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
214 similar to the SCSI protocol. If you have an SCSI tape drive
215 however, you can say N here.
217 You should also say Y if you have an OnStream DI-30 tape drive; this
218 will not work with the SCSI protocol, until there is support for the
219 SC-30 and SC-50 versions.
221 If you say Y here, the tape drive will be identified at boot time
222 along with other IDE devices, as "hdb" or "hdc", or something
223 similar, and will be mapped to a character device such as "ht0"
224 (check the boot messages with dmesg). Be sure to consult the
225 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide/ide.txt>
226 files for usage information.
228 To compile this driver as a module, choose M here: the
229 module will be called ide-tape.
231 config BLK_DEV_IDEFLOPPY
232 tristate "Include IDE/ATAPI FLOPPY support"
235 If you have an IDE floppy drive which uses the ATAPI protocol,
236 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
237 drives, similar to the SCSI protocol.
239 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
240 this driver. For information about jumper settings and the question
241 of when a ZIP drive uses a partition table, see
242 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
243 (ATAPI PD-CD/CDR drives are not supported by this driver; support
244 for PD-CD/CDR drives is available if you answer Y to
245 "SCSI emulation support", below).
247 If you say Y here, the FLOPPY drive will be identified along with
248 other IDE devices, as "hdb" or "hdc", or something similar (check
249 the boot messages with dmesg).
251 To compile this driver as a module, choose M here: the
252 module will be called ide-floppy.
254 config BLK_DEV_IDESCSI
255 tristate "SCSI emulation support"
259 WARNING: ide-scsi is no longer needed for cd writing applications!
260 The 2.6 kernel supports direct writing to ide-cd, which eliminates
261 the need for ide-scsi + the entire scsi stack just for writing a
262 cd. The new method is more efficient in every way.
264 This will provide SCSI host adapter emulation for IDE ATAPI devices,
265 and will allow you to use a SCSI device driver instead of a native
268 This is useful if you have an ATAPI device for which no native
269 driver has been written (for example, an ATAPI PD-CD drive);
270 you can then use this emulation together with an appropriate SCSI
271 device driver. In order to do this, say Y here and to "SCSI support"
272 and "SCSI generic support", below. You must then provide the kernel
273 command line "hdx=ide-scsi" (try "man bootparam" or see the
274 documentation of your boot loader (lilo or loadlin) about how to
275 pass options to the kernel at boot time) for devices if you want the
276 native EIDE sub-drivers to skip over the native support, so that
277 this SCSI emulation can be used instead.
279 Note that this option does NOT allow you to attach SCSI devices to a
280 box that doesn't have a SCSI host adapter installed.
282 If both this SCSI emulation and native ATAPI support are compiled
283 into the kernel, the native support will be used.
285 config BLK_DEV_IDEACPI
286 bool "IDE ACPI support"
289 Implement ACPI support for generic IDE devices. On modern
290 machines ACPI support is required to properly handle ACPI S3 states.
292 config IDE_TASK_IOCTL
293 bool "IDE Taskfile Access"
295 This is a direct raw access to the media. It is a complex but
296 elegant solution to test and validate the domain of the hardware and
297 perform below the driver data recovery if needed. This is the most
298 basic form of media-forensics.
300 If you are unsure, say N here.
303 bool "legacy /proc/ide/ support"
304 depends on IDE && PROC_FS
307 This option enables support for the various files in
308 /proc/ide. In Linux 2.6 this has been superseded by
309 files in sysfs but many legacy applications rely on this.
313 comment "IDE chipset support/bugfixes"
316 tristate "generic/default IDE chipset support"
317 depends on ALPHA || X86 || IA64 || M32R || MIPS || PPC32
321 config BLK_DEV_PLATFORM
322 tristate "Platform driver for IDE interfaces"
324 This is the platform IDE driver, used mostly for Memory Mapped
325 IDE devices, like Compact Flashes running in True IDE mode.
329 config BLK_DEV_CMD640
330 tristate "CMD640 chipset bugfix/support"
333 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
334 Pentium motherboards, usually in combination with a "Neptune" or
335 "SiS" chipset. Unfortunately, it has a number of rather nasty
336 design flaws that can cause severe data corruption under many common
337 conditions. Say Y here to include code which tries to automatically
338 detect and correct the problems under Linux. This option also
339 enables access to the secondary IDE ports in some CMD640 based
342 This driver will work automatically in PCI based systems (most new
343 systems have PCI slots). But if your system uses VESA local bus
344 (VLB) instead of PCI, you must also supply a kernel boot parameter
345 to enable the CMD640 bugfix/support: "cmd640.probe_vlb". (Try "man
346 bootparam" or see the documentation of your boot loader about how to
347 pass options to the kernel.)
349 The CMD640 chip is also used on add-in cards by Acculogic, and on
350 the "CSA-6400E PCI to IDE controller" that some people have. For
351 details, read <file:Documentation/ide/ide.txt>.
353 config BLK_DEV_CMD640_ENHANCED
354 bool "CMD640 enhanced support"
355 depends on BLK_DEV_CMD640
357 This option includes support for setting/autotuning PIO modes and
358 prefetch on CMD640 IDE interfaces. For details, read
359 <file:Documentation/ide/ide.txt>. If you have a CMD640 IDE interface
360 and your BIOS does not already do this for you, then say Y here.
363 config BLK_DEV_IDEPNP
364 tristate "PNP EIDE support"
367 If you have a PnP (Plug and Play) compatible EIDE card and
368 would like the kernel to automatically detect and activate
371 config BLK_DEV_IDEDMA_SFF
376 comment "PCI IDE chipsets support"
378 config BLK_DEV_IDEPCI
381 config IDEPCI_PCIBUS_ORDER
382 bool "Probe IDE PCI devices in the PCI bus order (DEPRECATED)"
383 depends on BLK_DEV_IDE=y && BLK_DEV_IDEPCI
386 Probe IDE PCI devices in the order in which they appear on the
387 PCI bus (i.e. 00:1f.1 PCI device before 02:01.0 PCI device)
388 instead of the order in which IDE PCI host drivers are loaded.
390 Please note that this method of assuring stable naming of
391 IDE devices is unreliable and use other means for achieving
396 # TODO: split it on per host driver config options (or module parameters)
397 config BLK_DEV_OFFBOARD
398 bool "Boot off-board chipsets first support (DEPRECATED)"
399 depends on BLK_DEV_IDEPCI && (BLK_DEV_AEC62XX || BLK_DEV_GENERIC || BLK_DEV_HPT34X || BLK_DEV_HPT366 || BLK_DEV_PDC202XX_NEW || BLK_DEV_PDC202XX_OLD || BLK_DEV_TC86C001)
401 Normally, IDE controllers built into the motherboard (on-board
402 controllers) are assigned to ide0 and ide1 while those on add-in PCI
403 cards (off-board controllers) are relegated to ide2 and ide3.
404 Answering Y here will allow you to reverse the situation, with
405 off-board controllers on ide0/1 and on-board controllers on ide2/3.
406 This can improve the usability of some boot managers such as lilo
407 when booting from a drive on an off-board controller.
409 Note that, if you do this, the order of the hd* devices will be
410 rearranged which may require modification of fstab and other files.
412 Please also note that this method of assuring stable naming of
413 IDE devices is unreliable and use other means for achieving it
418 config BLK_DEV_GENERIC
419 tristate "Generic PCI IDE Chipset Support"
420 select BLK_DEV_IDEPCI
422 This option provides generic support for various PCI IDE Chipsets
423 which otherwise might not be supported.
425 config BLK_DEV_OPTI621
426 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
427 depends on EXPERIMENTAL
428 select BLK_DEV_IDEPCI
430 This is a driver for the OPTi 82C621 EIDE controller.
431 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
433 config BLK_DEV_RZ1000
434 tristate "RZ1000 chipset bugfix/support"
436 select BLK_DEV_IDEPCI
438 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
439 Pentium motherboards, usually along with the "Neptune" chipset.
440 Unfortunately, it has a rather nasty design flaw that can cause
441 severe data corruption under many conditions. Say Y here to include
442 code which automatically detects and corrects the problem under
443 Linux. This may slow disk throughput by a few percent, but at least
444 things will operate 100% reliably.
446 config BLK_DEV_IDEDMA_PCI
448 select BLK_DEV_IDEPCI
449 select BLK_DEV_IDEDMA_SFF
451 config BLK_DEV_AEC62XX
452 tristate "AEC62XX chipset support"
453 select BLK_DEV_IDEDMA_PCI
455 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
456 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
457 speeds and to configure the chip to optimum performance.
459 config BLK_DEV_ALI15X3
460 tristate "ALI M15x3 chipset support"
461 select BLK_DEV_IDEDMA_PCI
463 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
464 onboard chipsets. It also tests for Simplex mode and enables
465 normal dual channel support.
467 Please read the comments at the top of
468 <file:drivers/ide/pci/alim15x3.c>.
472 config BLK_DEV_AMD74XX
473 tristate "AMD and nVidia IDE support"
476 select BLK_DEV_IDEDMA_PCI
478 This driver adds explicit support for AMD-7xx and AMD-8111 chips
479 and also for the nVidia nForce chip. This allows the kernel to
480 change PIO, DMA and UDMA speeds and to configure the chip to
483 config BLK_DEV_ATIIXP
484 tristate "ATI IXP chipset IDE support"
486 select BLK_DEV_IDEDMA_PCI
488 This driver adds explicit support for ATI IXP chipset.
489 This allows the kernel to change PIO, DMA and UDMA speeds
490 and to configure the chip to optimum performance.
492 Say Y here if you have an ATI IXP chipset IDE controller.
494 config BLK_DEV_CMD64X
495 tristate "CMD64{3|6|8|9} chipset support"
496 select BLK_DEV_IDEDMA_PCI
498 Say Y here if you have an IDE controller which uses any of these
499 chipsets: CMD643, CMD646, or CMD648.
501 config BLK_DEV_TRIFLEX
502 tristate "Compaq Triflex IDE support"
503 select BLK_DEV_IDEDMA_PCI
505 Say Y here if you have a Compaq Triflex IDE controller, such
506 as those commonly found on Compaq Pentium-Pro systems
508 config BLK_DEV_CY82C693
509 tristate "CY82C693 chipset support"
510 select BLK_DEV_IDEDMA_PCI
512 This driver adds detection and support for the CY82C693 chipset
513 used on Digital's PC-Alpha 164SX boards.
515 config BLK_DEV_CS5520
516 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
517 depends on EXPERIMENTAL
518 select BLK_DEV_IDEDMA_PCI
520 Include support for PIO tuning and virtual DMA on the Cyrix MediaGX
521 5510/5520 chipset. This will automatically be detected and
524 It is safe to say Y to this question.
526 config BLK_DEV_CS5530
527 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
528 select BLK_DEV_IDEDMA_PCI
530 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
531 will automatically be detected and configured if found.
533 It is safe to say Y to this question.
535 config BLK_DEV_CS5535
536 tristate "AMD CS5535 chipset support"
537 depends on X86 && !X86_64
538 select BLK_DEV_IDEDMA_PCI
540 Include support for UDMA on the NSC/AMD CS5535 companion chipset.
541 This will automatically be detected and configured if found.
543 It is safe to say Y to this question.
545 config BLK_DEV_HPT34X
546 tristate "HPT34X chipset support"
547 select BLK_DEV_IDEDMA_PCI
549 This driver adds up to 4 more EIDE devices sharing a single
550 interrupt. The HPT343 chipset in its current form is a non-bootable
551 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
552 PCI UDMA controllers. This driver requires dynamic tuning of the
553 chipset during the ide-probe at boot time. It is reported to support
554 DVD II drives, by the manufacturer.
556 config HPT34X_AUTODMA
557 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
558 depends on BLK_DEV_HPT34X && EXPERIMENTAL
560 This is a dangerous thing to attempt currently! Please read the
561 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
562 here, then say Y to "Use DMA by default when available" as well.
566 config BLK_DEV_HPT366
567 tristate "HPT36X/37X chipset support"
568 select BLK_DEV_IDEDMA_PCI
570 HPT366 is an Ultra DMA chipset for ATA-66.
571 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
572 HPT370 is an Ultra DMA chipset for ATA-100.
573 HPT372 is an Ultra DMA chipset for ATA-100.
574 HPT374 is an Ultra DMA chipset for ATA-100.
576 This driver adds up to 4 more EIDE devices sharing a single
579 The HPT366 chipset in its current form is bootable. One solution
580 for this problem are special LILO commands for redirecting the
581 reference to device 0x80. The other solution is to say Y to "Boot
582 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
583 your mother board has the chipset natively mounted. Regardless one
584 should use the fore mentioned option and call at LILO.
586 This driver requires dynamic tuning of the chipset during the
587 ide-probe at boot. It is reported to support DVD II drives, by the
590 config BLK_DEV_JMICRON
591 tristate "JMicron JMB36x support"
592 select BLK_DEV_IDEDMA_PCI
594 Basic support for the JMicron ATA controllers. For full support
595 use the libata drivers.
597 config BLK_DEV_SC1200
598 tristate "National SCx200 chipset support"
599 select BLK_DEV_IDEDMA_PCI
601 This driver adds support for the on-board IDE controller on the
602 National SCx200 series of embedded x86 "Geode" systems.
605 tristate "Intel PIIX/ICH chipsets support"
606 select BLK_DEV_IDEDMA_PCI
608 This driver adds explicit support for Intel PIIX and ICH chips.
609 This allows the kernel to change PIO, DMA and UDMA speeds and to
610 configure the chip to optimum performance.
612 config BLK_DEV_IT8213
613 tristate "IT8213 IDE support"
614 select BLK_DEV_IDEDMA_PCI
616 This driver adds support for the ITE 8213 IDE controller.
618 config BLK_DEV_IT821X
619 tristate "IT821X IDE support"
620 select BLK_DEV_IDEDMA_PCI
622 This driver adds support for the ITE 8211 IDE controller and the
623 IT 8212 IDE RAID controller in both RAID and pass-through mode.
625 config BLK_DEV_NS87415
626 tristate "NS87415 chipset support"
627 select BLK_DEV_IDEDMA_PCI
629 This driver adds detection and support for the NS87415 chip
630 (used mainly on SPARC64 and PA-RISC machines).
632 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
634 config BLK_DEV_PDC202XX_OLD
635 tristate "PROMISE PDC202{46|62|65|67} support"
636 select BLK_DEV_IDEDMA_PCI
638 Promise Ultra33 or PDC20246
639 Promise Ultra66 or PDC20262
640 Promise Ultra100 or PDC20265/PDC20267/PDC20268
642 This driver adds up to 4 more EIDE devices sharing a single
643 interrupt. This add-on card is a bootable PCI UDMA controller. Since
644 multiple cards can be installed and there are BIOS ROM problems that
645 happen if the BIOS revisions of all installed cards (three-max) do
646 not match, the driver attempts to do dynamic tuning of the chipset
647 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
648 for more than one card.
650 Please read the comments at the top of
651 <file:drivers/ide/pci/pdc202xx_old.c>.
655 config BLK_DEV_PDC202XX_NEW
656 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
657 select BLK_DEV_IDEDMA_PCI
660 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
661 select BLK_DEV_IDEDMA_PCI
663 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
666 config BLK_DEV_SGIIOC4
667 tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support"
668 depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4
669 select BLK_DEV_IDEDMA_PCI
671 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
672 chipset, which has one channel and can support two devices.
673 Please say Y here if you have an Altix System from SGI.
675 config BLK_DEV_SIIMAGE
676 tristate "Silicon Image chipset support"
677 select BLK_DEV_IDEDMA_PCI
679 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
680 3112 (Serial ATA) chips.
682 config BLK_DEV_SIS5513
683 tristate "SiS5513 chipset support"
685 select BLK_DEV_IDEDMA_PCI
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 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
699 config BLK_DEV_SL82C105
700 tristate "Winbond SL82c105 support"
701 depends on (PPC || ARM)
702 select BLK_DEV_IDEDMA_PCI
704 If you have a Winbond SL82c105 IDE controller, say Y here to enable
705 special configuration for this chip. This is common on various CHRP
706 motherboards, but could be used elsewhere. If in doubt, say Y.
708 config BLK_DEV_SLC90E66
709 tristate "SLC90E66 chipset support"
710 select BLK_DEV_IDEDMA_PCI
712 This driver ensures (U)DMA support for Victory66 SouthBridges for
713 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
714 The nice thing about it is that you can mix Ultra/DMA/PIO devices
715 and it will handle timing cycles. Since this is an improved
716 look-a-like to the PIIX4 it should be a nice addition.
718 Please read the comments at the top of
719 <file:drivers/ide/pci/slc90e66.c>.
721 config BLK_DEV_TRM290
722 tristate "Tekram TRM290 chipset support"
723 select BLK_DEV_IDEDMA_PCI
725 This driver adds support for bus master DMA transfers
726 using the Tekram TRM290 PCI IDE chip. Volunteers are
727 needed for further tweaking and development.
728 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
730 config BLK_DEV_VIA82CXXX
731 tristate "VIA82CXXX chipset support"
733 select BLK_DEV_IDEDMA_PCI
735 This driver adds explicit support for VIA BusMastering IDE chips.
736 This allows the kernel to change PIO, DMA and UDMA speeds and to
737 configure the chip to optimum performance.
739 config BLK_DEV_TC86C001
740 tristate "Toshiba TC86C001 support"
741 select BLK_DEV_IDEDMA_PCI
743 This driver adds support for Toshiba TC86C001 GOKU-S chip.
745 config BLK_DEV_CELLEB
746 tristate "Toshiba's Cell Reference Set IDE support"
747 depends on PPC_CELLEB
748 select BLK_DEV_IDEDMA_PCI
750 This driver provides support for the on-board IDE controller on
751 Toshiba Cell Reference Board.
756 config BLK_DEV_IDE_PMAC
757 tristate "PowerMac on-board IDE support"
758 depends on PPC_PMAC && IDE=y && BLK_DEV_IDE=y
761 This driver provides support for the on-board IDE controller on
762 most of the recent Apple Power Macintoshes and PowerBooks.
765 config BLK_DEV_IDE_PMAC_ATA100FIRST
766 bool "Probe on-board ATA/100 (Kauai) first"
767 depends on BLK_DEV_IDE_PMAC
769 This option will cause the ATA/100 controller found in UniNorth2
770 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
771 to be probed before the ATA/66 and ATA/33 controllers. Without
772 these, those machine used to have the hard disk on hdc and the
773 CD-ROM on hda. This option changes this to more natural hda for
774 hard disk and hdc for CD-ROM.
776 config BLK_DEV_IDEDMA_PMAC
777 bool "PowerMac IDE DMA support"
778 depends on BLK_DEV_IDE_PMAC
779 select BLK_DEV_IDEDMA_PCI
781 This option allows the driver for the on-board IDE controller on
782 Power Macintoshes and PowerBooks to use DMA (direct memory access)
783 to transfer data to and from memory. Saying Y is safe and improves
786 config BLK_DEV_IDE_SWARM
787 tristate "IDE for Sibyte evaluation boards"
788 depends on SIBYTE_SB1xxx_SOC
790 config BLK_DEV_IDE_AU1XXX
791 bool "IDE for AMD Alchemy Au1200"
792 depends on SOC_AU1200
794 prompt "IDE Mode for AMD Alchemy Au1200"
795 default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA
796 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
798 config BLK_DEV_IDE_AU1XXX_PIO_DBDMA
799 bool "PIO+DbDMA IDE for AMD Alchemy Au1200"
801 config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
802 bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200"
803 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
806 config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ
807 int "Maximum transfer size (KB) per request (up to 128)"
809 depends on BLK_DEV_IDE_AU1XXX
812 tristate "ARM IDE support"
813 depends on ARM && (ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
816 config BLK_DEV_IDE_ICSIDE
817 tristate "ICS IDE interface support"
818 depends on ARM && ARCH_ACORN
820 On Acorn systems, say Y here if you wish to use the ICS IDE
821 interface card. This is not required for ICS partition support.
822 If you are unsure, say N to this.
824 config BLK_DEV_IDEDMA_ICS
825 bool "ICS DMA support"
826 depends on BLK_DEV_IDE_ICSIDE
828 Say Y here if you want to add DMA (Direct Memory Access) support to
831 config BLK_DEV_IDE_RAPIDE
832 tristate "RapIDE interface support"
833 depends on ARM && ARCH_ACORN
835 Say Y here if you want to support the Yellowstone RapIDE controller
836 manufactured for use with Acorn computers.
839 tristate "H8300 IDE support"
843 Enables the H8300 IDE driver.
846 tristate "Amiga Gayle IDE interface support"
849 This is the IDE driver for the Amiga Gayle IDE interface. It supports
850 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
851 This includes on-board IDE interfaces on some Amiga models (A600,
852 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
853 bus (M-Tech E-Matrix 530 expansion card).
854 Say Y if you have an Amiga with a Gayle IDE interface and want to use
855 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
857 Note that you also have to enable Zorro bus support if you want to
858 use Gayle IDE interfaces on the Zorro expansion bus.
860 config BLK_DEV_IDEDOUBLER
861 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
862 depends on BLK_DEV_GAYLE && EXPERIMENTAL
864 This feature provides support for the so-called `IDE doublers' (made
865 by various manufacturers, e.g. Eyetech) that can be connected to
866 the on-board IDE interface of some Amiga models. Using such an IDE
867 doubler, you can connect up to four instead of two IDE devices to
868 the Amiga's on-board IDE interface.
870 Note that the normal Amiga Gayle IDE driver may not work correctly
871 if you have an IDE doubler and don't enable this feature!
873 Say Y if you have an IDE doubler. The feature is enabled at kernel
874 runtime using the "gayle.doubler" kernel boot parameter.
876 config BLK_DEV_BUDDHA
877 tristate "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
878 depends on ZORRO && EXPERIMENTAL
880 This is the IDE driver for the IDE interfaces on the Buddha, Catweasel
881 and X-Surf expansion boards. It supports up to two interfaces on the
882 Buddha, three on the Catweasel and two on the X-Surf.
884 Say Y if you have a Buddha or Catweasel expansion board and want to
885 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
886 to one of its IDE interfaces.
888 config BLK_DEV_FALCON_IDE
889 tristate "Falcon IDE interface support"
892 This is the IDE driver for the on-board IDE interface on the Atari
893 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
894 disks, CD-ROM drives, etc.) that are connected to the on-board IDE
897 config BLK_DEV_MAC_IDE
898 tristate "Macintosh Quadra/Powerbook IDE interface support"
901 This is the IDE driver for the on-board IDE interface on some m68k
902 Macintosh models. It supports both the `Quadra style' (used in
903 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
904 (used in the Powerbook 150 and 190 models) IDE interface.
906 Say Y if you have such an Macintosh model and want to use IDE
907 devices (hard disks, CD-ROM drives, etc.) that are connected to the
908 on-board IDE interface.
910 config BLK_DEV_Q40IDE
911 tristate "Q40/Q60 IDE interface support"
914 Enable the on-board IDE controller in the Q40/Q60. This should
915 normally be on; disable it only if you are running a custom hard
916 drive subsystem through an expansion card.
918 config BLK_DEV_PALMCHIP_BK3710
919 tristate "Palmchip bk3710 IDE controller support"
920 depends on ARCH_DAVINCI
922 select BLK_DEV_IDEDMA_SFF
924 Say Y here if you want to support the onchip IDE controller on the
928 config BLK_DEV_MPC8xx_IDE
929 tristate "MPC8xx IDE support"
930 depends on 8xx && (LWMON || IVMS8 || IVML24 || TQM8xxL) && IDE=y && BLK_DEV_IDE=y && !PPC_MERGE
932 This option provides support for IDE on Motorola MPC8xx Systems.
933 Please see 'Type of MPC8xx IDE interface' for details.
938 prompt "Type of MPC8xx IDE interface"
939 depends on BLK_DEV_MPC8xx_IDE
940 default IDE_8xx_PCCARD
942 config IDE_8xx_PCCARD
945 Select how the IDE devices are connected to the MPC8xx system:
947 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
948 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
949 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
952 8xx_DIRECT is used for directly connected IDE devices using the 8xx
953 internal PCMCIA interface (example: IVMS8 systems)
955 EXT_DIRECT is used for IDE devices directly connected to the 8xx
956 bus using some glue logic, but _not_ the 8xx internal
957 PCMCIA interface (example: IDIF860 systems)
959 config IDE_8xx_DIRECT
962 config IDE_EXT_DIRECT
968 if ISA && (ALPHA || X86 || MIPS)
970 comment "Other IDE chipsets support"
971 comment "Note: most of these also require special kernel boot parameters"
973 config BLK_DEV_4DRIVES
974 tristate "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 "ide-4drives.probe" kernel boot parameter if you
982 config BLK_DEV_ALI14XX
983 tristate "ALI M14xx support"
986 This driver is enabled at runtime using the "ali14xx.probe" kernel
987 boot parameter. It enables support for the secondary IDE interface
988 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
989 I/O speeds to be set as well.
990 See the files <file:Documentation/ide/ide.txt> and
991 <file:drivers/ide/legacy/ali14xx.c> for more info.
993 config BLK_DEV_DTC2278
994 tristate "DTC-2278 support"
996 This driver is enabled at runtime using the "dtc2278.probe" kernel
997 boot parameter. It enables support for the secondary IDE interface
998 of the DTC-2278 card, and permits faster I/O speeds to be set as
999 well. See the <file:Documentation/ide/ide.txt> and
1000 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1002 config BLK_DEV_HT6560B
1003 tristate "Holtek HT6560B support"
1005 This driver is enabled at runtime using the "ht6560b.probe" kernel
1006 boot parameter. It enables support for the secondary IDE interface
1007 of the Holtek card, and permits faster I/O speeds to be set as well.
1008 See the <file:Documentation/ide/ide.txt> and
1009 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1011 config BLK_DEV_QD65XX
1012 tristate "QDI QD65xx support"
1014 This driver is enabled at runtime using the "qd65xx.probe" kernel
1015 boot parameter. It permits faster I/O speeds to be set. See the
1016 <file:Documentation/ide/ide.txt> and <file:drivers/ide/legacy/qd65xx.c>
1019 config BLK_DEV_UMC8672
1020 tristate "UMC-8672 support"
1022 This driver is enabled at runtime using the "umc8672.probe" kernel
1023 boot parameter. It enables support for the secondary IDE interface
1024 of the UMC-8672, and permits faster I/O speeds to be set as well.
1025 See the files <file:Documentation/ide/ide.txt> and
1026 <file:drivers/ide/legacy/umc8672.c> for more info.
1030 config BLK_DEV_IDEDMA
1031 def_bool BLK_DEV_IDEDMA_SFF || BLK_DEV_IDEDMA_PMAC || \
1032 BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
1036 config BLK_DEV_HD_ONLY
1037 bool "Old hard disk (MFM/RLL/IDE) driver"
1038 depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
1040 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1041 the newer enhanced driver, but this old one is still around for two
1042 reasons. Some older systems have strange timing problems and seem to
1043 work only with the old driver (which itself does not work with some
1044 newer systems). The other reason is that the old driver is smaller,
1045 since it lacks the enhanced functionality of the new one. This makes
1046 it a good choice for systems with very tight memory restrictions, or
1047 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1048 driver can save 13 KB or so of kernel memory.
1050 If you want to use this driver together with the new one you have
1051 to use "hda=noprobe hdb=noprobe" kernel parameters to prevent the new
1052 driver from probing the primary interface.
1054 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1055 instead of this one. For more detailed information, read the
1056 Disk-HOWTO, available from
1057 <http://www.tldp.org/docs.html#howto>.
1060 def_bool BLK_DEV_HD_ONLY