| blob | df752e690e4739f595dee6dde3c103db522da5fa |
1 #
2 # IDE ATA ATAPI Block device driver configuration
3 #
4 # Andre Hedrick <andre@linux-ide.org>
5 #
7 # Select HAVE_IDE if IDE is supported
8 config HAVE_IDE
9 def_bool n
11 menuconfig IDE
12 tristate "ATA/ATAPI/MFM/RLL support"
13 depends on HAVE_IDE
14 depends on BLOCK
15 ---help---
16 If you say Y here, your kernel will be able to manage low cost mass
17 storage units such as ATA/(E)IDE and ATAPI units. The most common
18 cases are IDE hard drives and ATAPI CD-ROM drives.
20 If your system is pure SCSI and doesn't use these interfaces, you
21 can say N here.
23 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
24 for mass storage units such as hard disks. It was designed by
25 Western Digital and Compaq Computer in 1984. It was then named
26 ST506. Quite a number of disks use the IDE interface.
28 AT Attachment (ATA) is the superset of the IDE specifications.
29 ST506 was also called ATA-1.
31 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
32 ATA-3. It provides support for larger disks (up to 8.4GB by means of
33 the LBA standard), more disks (4 instead of 2) and for other mass
34 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
35 ATA-4 and provides faster (and more CPU friendly) transfer modes
36 than previous PIO (Programmed processor Input/Output) from previous
37 ATA/IDE standards by means of fast DMA controllers.
39 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
40 CD-ROM drives, similar in many respects to the SCSI protocol.
42 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
43 designed in order to prevent data corruption and disk crash by
44 detecting pre hardware failure conditions (heat, access time, and
45 the like...). Disks built since June 1995 may follow this standard.
46 The kernel itself doesn't manage this; however there are quite a
47 number of user programs such as smart that can query the status of
48 SMART parameters from disk drives.
50 To compile this driver as a module, choose M here: the
51 module will be called ide.
53 For further information, please read <file:Documentation/ide.txt>.
55 If unsure, say Y.
57 if IDE
59 config IDE_MAX_HWIFS
60 int "Max IDE interfaces"
61 depends on ALPHA || SUPERH || IA64 || EMBEDDED
62 range 1 10
63 default 4
64 help
65 This is the maximum number of IDE hardware interfaces that will
66 be supported by the driver. Make sure it is at least as high as
67 the number of IDE interfaces in your system.
69 config BLK_DEV_IDE
70 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
71 ---help---
72 If you say Y here, you will use the full-featured IDE driver to
73 control up to ten ATA/IDE interfaces, each being able to serve a
74 "master" and a "slave" device, for a total of up to twenty ATA/IDE
75 disk/cdrom/tape/floppy drives.
77 Useful information about large (>540 MB) IDE disks, multiple
78 interfaces, what to do if ATA/IDE devices are not automatically
79 detected, sound card ATA/IDE ports, module support, and other
80 topics, is contained in <file:Documentation/ide.txt>. For detailed
81 information about hard drives, consult the Disk-HOWTO and the
82 Multi-Disk-HOWTO, available from
83 <http://www.tldp.org/docs.html#howto>.
85 To fine-tune ATA/IDE drive/interface parameters for improved
86 performance, look for the hdparm package at
87 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
89 To compile this driver as a module, choose M here and read
90 <file:Documentation/ide.txt>. The module will be called ide-mod.
91 Do not compile this driver as a module if your root file system (the
92 one containing the directory /) is located on an IDE device.
94 If you have one or more IDE drives, say Y or M here. If your system
95 has no IDE drives, or if memory requirements are really tight, you
96 could say N here, and select the "Old hard disk driver" below
97 instead to save about 13 KB of memory in the kernel.
99 if BLK_DEV_IDE
101 comment "Please see Documentation/ide.txt for help/info on IDE drives"
103 config BLK_DEV_IDE_SATA
104 bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
105 default n
106 ---help---
107 There are two drivers for Serial ATA controllers.
109 The main driver, "libata", uses the SCSI subsystem
110 and supports most modern SATA controllers. In order to use it
111 you may take a look at "Serial ATA (prod) and Parallel ATA
112 (experimental) drivers".
114 The IDE driver (which you are currently configuring) supports
115 a few first-generation SATA controllers.
117 In order to eliminate conflicts between the two subsystems,
118 this config option enables the IDE driver's SATA support.
119 Normally this is disabled, as it is preferred that libata
120 supports SATA controllers, and this (IDE) driver supports
121 PATA controllers.
123 If unsure, say N.
125 config BLK_DEV_HD_IDE
126 bool "Use old disk-only driver on primary interface"
127 depends on (X86 || SH_MPC1211)
128 ---help---
129 There are two drivers for MFM/RLL/IDE disks. Most people use just
130 the new enhanced driver by itself. This option however installs the
131 old hard disk driver to control the primary IDE/disk interface in
132 the system, leaving the new enhanced IDE driver to take care of only
133 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
134 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
135 IDE interface. Choosing this option may be useful for older systems
136 which have MFM/RLL/ESDI controller+drives at the primary port
137 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
138 addresses.
140 Normally, just say N here; you will then use the new driver for all
141 4 interfaces.
143 config BLK_DEV_IDEDISK
144 tristate "Include IDE/ATA-2 DISK support"
145 ---help---
146 This will include enhanced support for MFM/RLL/IDE hard disks. If
147 you have a MFM/RLL/IDE disk, and there is no special reason to use
148 the old hard disk driver instead, say Y. If you have an SCSI-only
149 system, you can say N here.
151 To compile this driver as a module, choose M here: the
152 module will be called ide-disk.
153 Do not compile this driver as a module if your root file system
154 (the one containing the directory /) is located on the IDE disk.
156 If unsure, say Y.
158 config IDEDISK_MULTI_MODE
159 bool "Use multiple sector mode for Programmed Input/Output by default"
160 help
161 This setting is irrelevant for most IDE disks, with direct memory
162 access, to which multiple sector mode does not apply. Multiple sector
163 mode is a feature of most modern IDE hard drives, permitting the
164 transfer of multiple sectors per Programmed Input/Output interrupt,
165 rather than the usual one sector per interrupt. When this feature is
166 enabled, it can reduce operating system overhead for disk Programmed
167 Input/Output. On some systems, it also can increase the data
168 throughput of Programmed Input/Output. Some drives, however, seemed
169 to run slower with multiple sector mode enabled. Some drives claimed
170 to support multiple sector mode, but lost data at some settings.
171 Under rare circumstances, such failures could result in massive
172 filesystem corruption.
174 If you get the following error, try to say Y here:
176 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
177 hda: set_multmode: error=0x04 { DriveStatusError }
179 If in doubt, say N.
181 config BLK_DEV_IDECS
182 tristate "PCMCIA IDE support"
183 depends on PCMCIA
184 help
185 Support for Compact Flash cards, outboard IDE disks, tape drives,
186 and CD-ROM drives connected through a PCMCIA card.
188 config BLK_DEV_DELKIN
189 tristate "Cardbus IDE support (Delkin/ASKA/Workbit)"
190 depends on CARDBUS && PCI
191 help
192 Support for Delkin, ASKA, and Workbit Cardbus CompactFlash
193 Adapters. This may also work for similar SD and XD adapters.
195 config BLK_DEV_IDECD
196 tristate "Include IDE/ATAPI CDROM support"
197 ---help---
198 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
199 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
200 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
201 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
202 double(2X) or better speed drives.
204 If you say Y here, the CD-ROM drive will be identified at boot time
205 along with other IDE devices, as "hdb" or "hdc", or something
206 similar (check the boot messages with dmesg). If this is your only
207 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
208 to say Y or M to "ISO 9660 CD-ROM file system support".
210 To compile this driver as a module, choose M here: the
211 module will be called ide-cd.
213 config BLK_DEV_IDECD_VERBOSE_ERRORS
214 bool "Verbose error logging for IDE/ATAPI CDROM driver" if EMBEDDED
215 depends on BLK_DEV_IDECD
216 default y
217 help
218 Turn this on to have the driver print out the meanings of the
219 ATAPI error codes. This will use up additional 8kB of kernel-space
220 memory, though.
222 config BLK_DEV_IDETAPE
223 tristate "Include IDE/ATAPI TAPE support"
224 help
225 If you have an IDE tape drive using the ATAPI protocol, say Y.
226 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
227 similar to the SCSI protocol. If you have an SCSI tape drive
228 however, you can say N here.
230 You should also say Y if you have an OnStream DI-30 tape drive; this
231 will not work with the SCSI protocol, until there is support for the
232 SC-30 and SC-50 versions.
234 If you say Y here, the tape drive will be identified at boot time
235 along with other IDE devices, as "hdb" or "hdc", or something
236 similar, and will be mapped to a character device such as "ht0"
237 (check the boot messages with dmesg). Be sure to consult the
238 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
239 for usage information.
241 To compile this driver as a module, choose M here: the
242 module will be called ide-tape.
244 config BLK_DEV_IDEFLOPPY
245 tristate "Include IDE/ATAPI FLOPPY support"
246 ---help---
247 If you have an IDE floppy drive which uses the ATAPI protocol,
248 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
249 drives, similar to the SCSI protocol.
251 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
252 this driver. For information about jumper settings and the question
253 of when a ZIP drive uses a partition table, see
254 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
255 (ATAPI PD-CD/CDR drives are not supported by this driver; support
256 for PD-CD/CDR drives is available if you answer Y to
257 "SCSI emulation support", below).
259 If you say Y here, the FLOPPY drive will be identified along with
260 other IDE devices, as "hdb" or "hdc", or something similar (check
261 the boot messages with dmesg).
263 To compile this driver as a module, choose M here: the
264 module will be called ide-floppy.
266 config BLK_DEV_IDESCSI
267 tristate "SCSI emulation support"
268 depends on SCSI
269 ---help---
270 WARNING: ide-scsi is no longer needed for cd writing applications!
271 The 2.6 kernel supports direct writing to ide-cd, which eliminates
272 the need for ide-scsi + the entire scsi stack just for writing a
273 cd. The new method is more efficient in every way.
275 This will provide SCSI host adapter emulation for IDE ATAPI devices,
276 and will allow you to use a SCSI device driver instead of a native
277 ATAPI driver.
279 This is useful if you have an ATAPI device for which no native
280 driver has been written (for example, an ATAPI PD-CD drive);
281 you can then use this emulation together with an appropriate SCSI
282 device driver. In order to do this, say Y here and to "SCSI support"
283 and "SCSI generic support", below. You must then provide the kernel
284 command line "hdx=ide-scsi" (try "man bootparam" or see the
285 documentation of your boot loader (lilo or loadlin) about how to
286 pass options to the kernel at boot time) for devices if you want the
287 native EIDE sub-drivers to skip over the native support, so that
288 this SCSI emulation can be used instead.
290 Note that this option does NOT allow you to attach SCSI devices to a
291 box that doesn't have a SCSI host adapter installed.
293 If both this SCSI emulation and native ATAPI support are compiled
294 into the kernel, the native support will be used.
296 config BLK_DEV_IDEACPI
297 bool "IDE ACPI support"
298 depends on ACPI
299 ---help---
300 Implement ACPI support for generic IDE devices. On modern
301 machines ACPI support is required to properly handle ACPI S3 states.
303 config IDE_TASK_IOCTL
304 bool "IDE Taskfile Access"
305 help
306 This is a direct raw access to the media. It is a complex but
307 elegant solution to test and validate the domain of the hardware and
308 perform below the driver data recovery if needed. This is the most
309 basic form of media-forensics.
311 If you are unsure, say N here.
313 config IDE_PROC_FS
314 bool "legacy /proc/ide/ support"
315 depends on IDE && PROC_FS
316 default y
317 help
318 This option enables support for the various files in
319 /proc/ide. In Linux 2.6 this has been superseded by
320 files in sysfs but many legacy applications rely on this.
322 If unsure say Y.
324 comment "IDE chipset support/bugfixes"
326 config IDE_GENERIC
327 tristate "generic/default IDE chipset support"
328 help
329 If unsure, say N.
331 config BLK_DEV_PLATFORM
332 tristate "Platform driver for IDE interfaces"
333 help
334 This is the platform IDE driver, used mostly for Memory Mapped
335 IDE devices, like Compact Flashes running in True IDE mode.
337 If unsure, say N.
339 config BLK_DEV_CMD640
340 tristate "CMD640 chipset bugfix/support"
341 depends on X86
342 ---help---
343 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
344 Pentium motherboards, usually in combination with a "Neptune" or
345 "SiS" chipset. Unfortunately, it has a number of rather nasty
346 design flaws that can cause severe data corruption under many common
347 conditions. Say Y here to include code which tries to automatically
348 detect and correct the problems under Linux. This option also
349 enables access to the secondary IDE ports in some CMD640 based
350 systems.
352 This driver will work automatically in PCI based systems (most new
353 systems have PCI slots). But if your system uses VESA local bus
354 (VLB) instead of PCI, you must also supply a kernel boot parameter
355 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
356 bootparam" or see the documentation of your boot loader about how to
357 pass options to the kernel.)
359 The CMD640 chip is also used on add-in cards by Acculogic, and on
360 the "CSA-6400E PCI to IDE controller" that some people have. For
361 details, read <file:Documentation/ide.txt>.
363 config BLK_DEV_CMD640_ENHANCED
364 bool "CMD640 enhanced support"
365 depends on BLK_DEV_CMD640
366 help
367 This option includes support for setting/autotuning PIO modes and
368 prefetch on CMD640 IDE interfaces. For details, read
369 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
370 and your BIOS does not already do this for you, then say Y here.
371 Otherwise say N.
373 config BLK_DEV_IDEPNP
374 tristate "PNP EIDE support"
375 depends on PNP
376 help
377 If you have a PnP (Plug and Play) compatible EIDE card and
378 would like the kernel to automatically detect and activate
379 it, say Y here.
381 config BLK_DEV_IDEDMA_SFF
382 bool
384 if PCI
386 comment "PCI IDE chipsets support"
388 config BLK_DEV_IDEPCI
389 bool
391 config IDEPCI_PCIBUS_ORDER
392 bool "Probe IDE PCI devices in the PCI bus order (DEPRECATED)"
393 depends on BLK_DEV_IDE=y && BLK_DEV_IDEPCI
394 default y
395 help
396 Probe IDE PCI devices in the order in which they appear on the
397 PCI bus (i.e. 00:1f.1 PCI device before 02:01.0 PCI device)
398 instead of the order in which IDE PCI host drivers are loaded.
400 Please note that this method of assuring stable naming of
401 IDE devices is unreliable and use other means for achieving
402 it (i.e. udev).
404 If in doubt, say N.
406 # TODO: split it on per host driver config options (or module parameters)
407 config BLK_DEV_OFFBOARD
408 bool "Boot off-board chipsets first support (DEPRECATED)"
409 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)
410 help
411 Normally, IDE controllers built into the motherboard (on-board
412 controllers) are assigned to ide0 and ide1 while those on add-in PCI
413 cards (off-board controllers) are relegated to ide2 and ide3.
414 Answering Y here will allow you to reverse the situation, with
415 off-board controllers on ide0/1 and on-board controllers on ide2/3.
416 This can improve the usability of some boot managers such as lilo
417 when booting from a drive on an off-board controller.
419 If you say Y here, and you actually want to reverse the device scan
420 order as explained above, you also need to issue the kernel command
421 line option "ide=reverse". (Try "man bootparam" or see the
422 documentation of your boot loader (lilo or loadlin) about how to
423 pass options to the kernel at boot time.)
425 Note that, if you do this, the order of the hd* devices will be
426 rearranged which may require modification of fstab and other files.
428 Please also note that this method of assuring stable naming of
429 IDE devices is unreliable and use other means for achieving it
430 (i.e. udev).
432 If in doubt, say N.
434 config BLK_DEV_GENERIC
435 tristate "Generic PCI IDE Chipset Support"
436 select BLK_DEV_IDEPCI
437 help
438 This option provides generic support for various PCI IDE Chipsets
439 which otherwise might not be supported.
441 config BLK_DEV_OPTI621
442 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
443 depends on EXPERIMENTAL
444 select BLK_DEV_IDEPCI
445 help
446 This is a driver for the OPTi 82C621 EIDE controller.
447 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
449 config BLK_DEV_RZ1000
450 tristate "RZ1000 chipset bugfix/support"
451 depends on X86
452 select BLK_DEV_IDEPCI
453 help
454 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
455 Pentium motherboards, usually along with the "Neptune" chipset.
456 Unfortunately, it has a rather nasty design flaw that can cause
457 severe data corruption under many conditions. Say Y here to include
458 code which automatically detects and corrects the problem under
459 Linux. This may slow disk throughput by a few percent, but at least
460 things will operate 100% reliably.
462 config BLK_DEV_IDEDMA_PCI
463 bool
464 select BLK_DEV_IDEPCI
465 select BLK_DEV_IDEDMA_SFF
467 config BLK_DEV_AEC62XX
468 tristate "AEC62XX chipset support"
469 select BLK_DEV_IDEDMA_PCI
470 help
471 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
472 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
473 speeds and to configure the chip to optimum performance.
475 config BLK_DEV_ALI15X3
476 tristate "ALI M15x3 chipset support"
477 select BLK_DEV_IDEDMA_PCI
478 help
479 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
480 onboard chipsets. It also tests for Simplex mode and enables
481 normal dual channel support.
483 If you say Y here, you also need to say Y to "Use DMA by default
484 when available", above. Please read the comments at the top of
485 <file:drivers/ide/pci/alim15x3.c>.
487 If unsure, say N.
489 config WDC_ALI15X3
490 bool "ALI M15x3 WDC support (DANGEROUS)"
491 depends on BLK_DEV_ALI15X3
492 ---help---
493 This allows for UltraDMA support for WDC drives that ignore CRC
494 checking. You are a fool for enabling this option, but there have
495 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
496 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
497 SERIOUS WARNING.
499 Using this option can allow WDC drives to run at ATA-4/5 transfer
500 rates with only an ATA-2 support structure.
502 SAY N!
504 config BLK_DEV_AMD74XX
505 tristate "AMD and nVidia IDE support"
506 depends on !ARM
507 select BLK_DEV_IDEDMA_PCI
508 help
509 This driver adds explicit support for AMD-7xx and AMD-8111 chips
510 and also for the nVidia nForce chip. This allows the kernel to
511 change PIO, DMA and UDMA speeds and to configure the chip to
512 optimum performance.
514 config BLK_DEV_ATIIXP
515 tristate "ATI IXP chipset IDE support"
516 depends on X86
517 select BLK_DEV_IDEDMA_PCI
518 help
519 This driver adds explicit support for ATI IXP chipset.
520 This allows the kernel to change PIO, DMA and UDMA speeds
521 and to configure the chip to optimum performance.
523 Say Y here if you have an ATI IXP chipset IDE controller.
525 config BLK_DEV_CMD64X
526 tristate "CMD64{3|6|8|9} chipset support"
527 select BLK_DEV_IDEDMA_PCI
528 help
529 Say Y here if you have an IDE controller which uses any of these
530 chipsets: CMD643, CMD646, or CMD648.
532 config BLK_DEV_TRIFLEX
533 tristate "Compaq Triflex IDE support"
534 select BLK_DEV_IDEDMA_PCI
535 help
536 Say Y here if you have a Compaq Triflex IDE controller, such
537 as those commonly found on Compaq Pentium-Pro systems
539 config BLK_DEV_CY82C693
540 tristate "CY82C693 chipset support"
541 select BLK_DEV_IDEDMA_PCI
542 help
543 This driver adds detection and support for the CY82C693 chipset
544 used on Digital's PC-Alpha 164SX boards.
546 If you say Y here, you need to say Y to "Use DMA by default
547 when available" as well.
549 config BLK_DEV_CS5520
550 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
551 depends on EXPERIMENTAL
552 select BLK_DEV_IDEDMA_PCI
553 help
554 Include support for PIO tuning and virtual DMA on the Cyrix MediaGX
555 5510/5520 chipset. This will automatically be detected and
556 configured if found.
558 It is safe to say Y to this question.
560 config BLK_DEV_CS5530
561 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
562 select BLK_DEV_IDEDMA_PCI
563 help
564 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
565 will automatically be detected and configured if found.
567 It is safe to say Y to this question.
569 config BLK_DEV_CS5535
570 tristate "AMD CS5535 chipset support"
571 depends on X86 && !X86_64
572 select BLK_DEV_IDEDMA_PCI
573 help
574 Include support for UDMA on the NSC/AMD CS5535 companion chipset.
575 This will automatically be detected and configured if found.
577 It is safe to say Y to this question.
579 config BLK_DEV_HPT34X
580 tristate "HPT34X chipset support"
581 select BLK_DEV_IDEDMA_PCI
582 help
583 This driver adds up to 4 more EIDE devices sharing a single
584 interrupt. The HPT343 chipset in its current form is a non-bootable
585 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
586 PCI UDMA controllers. This driver requires dynamic tuning of the
587 chipset during the ide-probe at boot time. It is reported to support
588 DVD II drives, by the manufacturer.
590 config HPT34X_AUTODMA
591 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
592 depends on BLK_DEV_HPT34X && EXPERIMENTAL
593 help
594 This is a dangerous thing to attempt currently! Please read the
595 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
596 here, then say Y to "Use DMA by default when available" as well.
598 If unsure, say N.
600 config BLK_DEV_HPT366
601 tristate "HPT36X/37X chipset support"
602 select BLK_DEV_IDEDMA_PCI
603 help
604 HPT366 is an Ultra DMA chipset for ATA-66.
605 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
606 HPT370 is an Ultra DMA chipset for ATA-100.
607 HPT372 is an Ultra DMA chipset for ATA-100.
608 HPT374 is an Ultra DMA chipset for ATA-100.
610 This driver adds up to 4 more EIDE devices sharing a single
611 interrupt.
613 The HPT366 chipset in its current form is bootable. One solution
614 for this problem are special LILO commands for redirecting the
615 reference to device 0x80. The other solution is to say Y to "Boot
616 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
617 your mother board has the chipset natively mounted. Regardless one
618 should use the fore mentioned option and call at LILO or include
619 "ide=reverse" in LILO's append-line.
621 This driver requires dynamic tuning of the chipset during the
622 ide-probe at boot. It is reported to support DVD II drives, by the
623 manufacturer.
625 config BLK_DEV_JMICRON
626 tristate "JMicron JMB36x support"
627 select BLK_DEV_IDEDMA_PCI
628 help
629 Basic support for the JMicron ATA controllers. For full support
630 use the libata drivers.
632 config BLK_DEV_SC1200
633 tristate "National SCx200 chipset support"
634 select BLK_DEV_IDEDMA_PCI
635 help
636 This driver adds support for the on-board IDE controller on the
637 National SCx200 series of embedded x86 "Geode" systems.
639 config BLK_DEV_PIIX
640 tristate "Intel PIIXn chipsets support"
641 select BLK_DEV_IDEDMA_PCI
642 help
643 This driver adds explicit support for Intel PIIX and ICH chips
644 and also for the Efar Victory66 (slc90e66) chip. This allows
645 the kernel to change PIO, DMA and UDMA speeds and to configure
646 the chip to optimum performance.
648 config BLK_DEV_IT8213
649 tristate "IT8213 IDE support"
650 select BLK_DEV_IDEDMA_PCI
651 help
652 This driver adds support for the ITE 8213 IDE controller.
654 config BLK_DEV_IT821X
655 tristate "IT821X IDE support"
656 select BLK_DEV_IDEDMA_PCI
657 help
658 This driver adds support for the ITE 8211 IDE controller and the
659 IT 8212 IDE RAID controller in both RAID and pass-through mode.
661 config BLK_DEV_NS87415
662 tristate "NS87415 chipset support"
663 select BLK_DEV_IDEDMA_PCI
664 help
665 This driver adds detection and support for the NS87415 chip
666 (used mainly on SPARC64 and PA-RISC machines).
668 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
670 config BLK_DEV_PDC202XX_OLD
671 tristate "PROMISE PDC202{46|62|65|67} support"
672 select BLK_DEV_IDEDMA_PCI
673 help
674 Promise Ultra33 or PDC20246
675 Promise Ultra66 or PDC20262
676 Promise Ultra100 or PDC20265/PDC20267/PDC20268
678 This driver adds up to 4 more EIDE devices sharing a single
679 interrupt. This add-on card is a bootable PCI UDMA controller. Since
680 multiple cards can be installed and there are BIOS ROM problems that
681 happen if the BIOS revisions of all installed cards (three-max) do
682 not match, the driver attempts to do dynamic tuning of the chipset
683 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
684 for more than one card. This card may require that you say Y to
685 "Special UDMA Feature".
687 If you say Y here, you need to say Y to "Use DMA by default when
688 available" as well.
690 Please read the comments at the top of
691 <file:drivers/ide/pci/pdc202xx_old.c>.
693 If unsure, say N.
695 config BLK_DEV_PDC202XX_NEW
696 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
697 select BLK_DEV_IDEDMA_PCI
699 config BLK_DEV_SVWKS
700 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
701 select BLK_DEV_IDEDMA_PCI
702 help
703 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
704 chipsets.
706 config BLK_DEV_SGIIOC4
707 tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support"
708 depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4
709 select BLK_DEV_IDEDMA_PCI
710 help
711 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
712 chipset, which has one channel and can support two devices.
713 Please say Y here if you have an Altix System from SGI.
715 config BLK_DEV_SIIMAGE
716 tristate "Silicon Image chipset support"
717 select BLK_DEV_IDEDMA_PCI
718 help
719 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
720 3112 (Serial ATA) chips.
722 config BLK_DEV_SIS5513
723 tristate "SiS5513 chipset support"
724 depends on X86
725 select BLK_DEV_IDEDMA_PCI
726 help
727 This driver ensures (U)DMA support for SIS5513 chipset family based
728 mainboards.
730 The following chipsets are supported:
731 ATA16: SiS5511, SiS5513
732 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
733 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
734 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
735 SiS745, SiS750
737 If you say Y here, you need to say Y to "Use DMA by default when
738 available" as well.
740 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
742 config BLK_DEV_SL82C105
743 tristate "Winbond SL82c105 support"
744 depends on (PPC || ARM)
745 select BLK_DEV_IDEDMA_PCI
746 help
747 If you have a Winbond SL82c105 IDE controller, say Y here to enable
748 special configuration for this chip. This is common on various CHRP
749 motherboards, but could be used elsewhere. If in doubt, say Y.
751 config BLK_DEV_SLC90E66
752 tristate "SLC90E66 chipset support"
753 select BLK_DEV_IDEDMA_PCI
754 help
755 This driver ensures (U)DMA support for Victory66 SouthBridges for
756 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
757 The nice thing about it is that you can mix Ultra/DMA/PIO devices
758 and it will handle timing cycles. Since this is an improved
759 look-a-like to the PIIX4 it should be a nice addition.
761 If you say Y here, you need to say Y to "Use DMA by default when
762 available" as well.
764 Please read the comments at the top of
765 <file:drivers/ide/pci/slc90e66.c>.
767 config BLK_DEV_TRM290
768 tristate "Tekram TRM290 chipset support"
769 select BLK_DEV_IDEDMA_PCI
770 help
771 This driver adds support for bus master DMA transfers
772 using the Tekram TRM290 PCI IDE chip. Volunteers are
773 needed for further tweaking and development.
774 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
776 config BLK_DEV_VIA82CXXX
777 tristate "VIA82CXXX chipset support"
778 select BLK_DEV_IDEDMA_PCI
779 help
780 This driver adds explicit support for VIA BusMastering IDE chips.
781 This allows the kernel to change PIO, DMA and UDMA speeds and to
782 configure the chip to optimum performance.
784 config BLK_DEV_TC86C001
785 tristate "Toshiba TC86C001 support"
786 select BLK_DEV_IDEDMA_PCI
787 help
788 This driver adds support for Toshiba TC86C001 GOKU-S chip.
790 config BLK_DEV_CELLEB
791 tristate "Toshiba's Cell Reference Set IDE support"
792 depends on PPC_CELLEB
793 select BLK_DEV_IDEDMA_PCI
794 help
795 This driver provides support for the on-board IDE controller on
796 Toshiba Cell Reference Board.
797 If unsure, say Y.
799 endif
801 config BLK_DEV_IDE_PMAC
802 tristate "PowerMac on-board IDE support"
803 depends on PPC_PMAC && IDE=y && BLK_DEV_IDE=y
804 help
805 This driver provides support for the on-board IDE controller on
806 most of the recent Apple Power Macintoshes and PowerBooks.
807 If unsure, say Y.
809 config BLK_DEV_IDE_PMAC_ATA100FIRST
810 bool "Probe on-board ATA/100 (Kauai) first"
811 depends on BLK_DEV_IDE_PMAC
812 help
813 This option will cause the ATA/100 controller found in UniNorth2
814 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
815 to be probed before the ATA/66 and ATA/33 controllers. Without
816 these, those machine used to have the hard disk on hdc and the
817 CD-ROM on hda. This option changes this to more natural hda for
818 hard disk and hdc for CD-ROM.
820 config BLK_DEV_IDEDMA_PMAC
821 bool "PowerMac IDE DMA support"
822 depends on BLK_DEV_IDE_PMAC
823 select BLK_DEV_IDEDMA_PCI
824 help
825 This option allows the driver for the on-board IDE controller on
826 Power Macintoshes and PowerBooks to use DMA (direct memory access)
827 to transfer data to and from memory. Saying Y is safe and improves
828 performance.
830 config BLK_DEV_IDE_SWARM
831 tristate "IDE for Sibyte evaluation boards"
832 depends on SIBYTE_SB1xxx_SOC
834 config BLK_DEV_IDE_AU1XXX
835 bool "IDE for AMD Alchemy Au1200"
836 depends on SOC_AU1200
837 choice
838 prompt "IDE Mode for AMD Alchemy Au1200"
839 default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA
840 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
842 config BLK_DEV_IDE_AU1XXX_PIO_DBDMA
843 bool "PIO+DbDMA IDE for AMD Alchemy Au1200"
845 config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
846 bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200"
847 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX
848 endchoice
850 config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ
851 int "Maximum transfer size (KB) per request (up to 128)"
852 default "128"
853 depends on BLK_DEV_IDE_AU1XXX
855 config IDE_ARM
856 tristate "ARM IDE support"
857 depends on ARM && (ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK)
858 default y
860 config BLK_DEV_IDE_ICSIDE
861 tristate "ICS IDE interface support"
862 depends on ARM && ARCH_ACORN
863 help
864 On Acorn systems, say Y here if you wish to use the ICS IDE
865 interface card. This is not required for ICS partition support.
866 If you are unsure, say N to this.
868 config BLK_DEV_IDEDMA_ICS
869 bool "ICS DMA support"
870 depends on BLK_DEV_IDE_ICSIDE
871 help
872 Say Y here if you want to add DMA (Direct Memory Access) support to
873 the ICS IDE driver.
875 config BLK_DEV_IDE_RAPIDE
876 tristate "RapIDE interface support"
877 depends on ARM && ARCH_ACORN
878 help
879 Say Y here if you want to support the Yellowstone RapIDE controller
880 manufactured for use with Acorn computers.
882 config BLK_DEV_IDE_BAST
883 tristate "Simtec BAST / Thorcom VR1000 IDE support"
884 depends on ARM && (ARCH_BAST || MACH_VR1000)
885 help
886 Say Y here if you want to support the onboard IDE channels on the
887 Simtec BAST or the Thorcom VR1000
889 config ETRAX_IDE
890 tristate "ETRAX IDE support"
891 depends on CRIS && BROKEN
892 select BLK_DEV_IDEDMA
893 help
894 Enables the ETRAX IDE driver.
896 You can't use parallel ports or SCSI ports at the same time.
898 config ETRAX_IDE_DELAY
899 int "Delay for drives to regain consciousness"
900 depends on ETRAX_IDE && ETRAX_ARCH_V10
901 default 15
902 help
903 Number of seconds to wait for IDE drives to spin up after an IDE
904 reset.
906 choice
907 prompt "IDE reset pin"
908 depends on ETRAX_IDE && ETRAX_ARCH_V10
909 default ETRAX_IDE_PB7_RESET
911 config ETRAX_IDE_PB7_RESET
912 bool "Port_PB_Bit_7"
913 help
914 IDE reset on pin 7 on port B
916 config ETRAX_IDE_G27_RESET
917 bool "Port_G_Bit_27"
918 help
919 IDE reset on pin 27 on port G
921 endchoice
923 config IDE_H8300
924 tristate "H8300 IDE support"
925 depends on H8300
926 default y
927 help
928 Enables the H8300 IDE driver.
930 config BLK_DEV_GAYLE
931 tristate "Amiga Gayle IDE interface support"
932 depends on AMIGA
933 help
934 This is the IDE driver for the Amiga Gayle IDE interface. It supports
935 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
936 This includes on-board IDE interfaces on some Amiga models (A600,
937 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
938 bus (M-Tech E-Matrix 530 expansion card).
939 Say Y if you have an Amiga with a Gayle IDE interface and want to use
940 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
941 it.
942 Note that you also have to enable Zorro bus support if you want to
943 use Gayle IDE interfaces on the Zorro expansion bus.
945 config BLK_DEV_IDEDOUBLER
946 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
947 depends on BLK_DEV_GAYLE && EXPERIMENTAL
948 ---help---
949 This driver provides support for the so-called `IDE doublers' (made
950 by various manufacturers, e.g. Eyetech) that can be connected to
951 the on-board IDE interface of some Amiga models. Using such an IDE
952 doubler, you can connect up to four instead of two IDE devices to
953 the Amiga's on-board IDE interface.
955 Note that the normal Amiga Gayle IDE driver may not work correctly
956 if you have an IDE doubler and don't enable this driver!
958 Say Y if you have an IDE doubler. The driver is enabled at kernel
959 runtime using the "ide=doubler" kernel boot parameter.
961 config BLK_DEV_BUDDHA
962 tristate "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
963 depends on ZORRO && EXPERIMENTAL
964 help
965 This is the IDE driver for the IDE interfaces on the Buddha, Catweasel
966 and X-Surf expansion boards. It supports up to two interfaces on the
967 Buddha, three on the Catweasel and two on the X-Surf.
969 Say Y if you have a Buddha or Catweasel expansion board and want to
970 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
971 to one of its IDE interfaces.
973 config BLK_DEV_FALCON_IDE
974 tristate "Falcon IDE interface support"
975 depends on ATARI
976 help
977 This is the IDE driver for the on-board IDE interface on the Atari
978 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
979 disks, CD-ROM drives, etc.) that are connected to the on-board IDE
980 interface.
982 config BLK_DEV_MAC_IDE
983 tristate "Macintosh Quadra/Powerbook IDE interface support"
984 depends on MAC
985 help
986 This is the IDE driver for the on-board IDE interface on some m68k
987 Macintosh models. It supports both the `Quadra style' (used in
988 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
989 (used in the Powerbook 150 and 190 models) IDE interface.
991 Say Y if you have such an Macintosh model and want to use IDE
992 devices (hard disks, CD-ROM drives, etc.) that are connected to the
993 on-board IDE interface.
995 config BLK_DEV_Q40IDE
996 tristate "Q40/Q60 IDE interface support"
997 depends on Q40
998 help
999 Enable the on-board IDE controller in the Q40/Q60. This should
1000 normally be on; disable it only if you are running a custom hard
1001 drive subsystem through an expansion card.
1003 config BLK_DEV_PALMCHIP_BK3710
1004 tristate "Palmchip bk3710 IDE controller support"
1005 depends on ARCH_DAVINCI
1006 select BLK_DEV_IDEDMA_SFF
1007 help
1008 Say Y here if you want to support the onchip IDE controller on the
1009 TI DaVinci SoC
1012 config BLK_DEV_MPC8xx_IDE
1013 tristate "MPC8xx IDE support"
1014 depends on 8xx && (LWMON || IVMS8 || IVML24 || TQM8xxL) && IDE=y && BLK_DEV_IDE=y && !PPC_MERGE
1015 help
1016 This option provides support for IDE on Motorola MPC8xx Systems.
1017 Please see 'Type of MPC8xx IDE interface' for details.
1019 If unsure, say N.
1021 choice
1022 prompt "Type of MPC8xx IDE interface"
1023 depends on BLK_DEV_MPC8xx_IDE
1024 default IDE_8xx_PCCARD
1026 config IDE_8xx_PCCARD
1027 bool "8xx_PCCARD"
1028 ---help---
1029 Select how the IDE devices are connected to the MPC8xx system:
1031 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
1032 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
1033 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
1034 systems)
1036 8xx_DIRECT is used for directly connected IDE devices using the 8xx
1037 internal PCMCIA interface (example: IVMS8 systems)
1039 EXT_DIRECT is used for IDE devices directly connected to the 8xx
1040 bus using some glue logic, but _not_ the 8xx internal
1041 PCMCIA interface (example: IDIF860 systems)
1043 config IDE_8xx_DIRECT
1044 bool "8xx_DIRECT"
1046 config IDE_EXT_DIRECT
1047 bool "EXT_DIRECT"
1049 endchoice
1051 # no isa -> no vlb
1052 if ISA
1054 comment "Other IDE chipsets support"
1055 comment "Note: most of these also require special kernel boot parameters"
1057 config BLK_DEV_4DRIVES
1058 bool "Generic 4 drives/port support"
1059 help
1060 Certain older chipsets, including the Tekram 690CD, use a single set
1061 of I/O ports at 0x1f0 to control up to four drives, instead of the
1062 customary two drives per port. Support for this can be enabled at
1063 runtime using the "ide0=four" kernel boot parameter if you say Y
1064 here.
1066 config BLK_DEV_ALI14XX
1067 tristate "ALI M14xx support"
1068 help
1069 This driver is enabled at runtime using the "ali14xx.probe" kernel
1070 boot parameter. It enables support for the secondary IDE interface
1071 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1072 I/O speeds to be set as well. See the files
1073 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c>
1074 for more info.
1076 config BLK_DEV_DTC2278
1077 tristate "DTC-2278 support"
1078 help
1079 This driver is enabled at runtime using the "dtc2278.probe" kernel
1080 boot parameter. It enables support for the secondary IDE interface
1081 of the DTC-2278 card, and permits faster I/O speeds to be set as
1082 well. See the <file:Documentation/ide.txt> and
1083 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1085 config BLK_DEV_HT6560B
1086 tristate "Holtek HT6560B support"
1087 help
1088 This driver is enabled at runtime using the "ht6560b.probe" kernel
1089 boot parameter. It enables support for the secondary IDE interface
1090 of the Holtek card, and permits faster I/O speeds to be set as well.
1091 See the <file:Documentation/ide.txt> and
1092 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1094 config BLK_DEV_QD65XX
1095 tristate "QDI QD65xx support"
1096 help
1097 This driver is enabled at runtime using the "qd65xx.probe" kernel
1098 boot parameter. It permits faster I/O speeds to be set. See the
1099 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c>
1100 for more info.
1102 config BLK_DEV_UMC8672
1103 tristate "UMC-8672 support"
1104 help
1105 This driver is enabled at runtime using the "umc8672.probe" kernel
1106 boot parameter. It enables support for the secondary IDE interface
1107 of the UMC-8672, and permits faster I/O speeds to be set as well.
1108 See the files <file:Documentation/ide.txt> and
1109 <file:drivers/ide/legacy/umc8672.c> for more info.
1111 endif
1113 config BLK_DEV_IDEDMA
1114 def_bool BLK_DEV_IDEDMA_SFF || BLK_DEV_IDEDMA_PMAC || \
1115 BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA
1117 config IDE_ARCH_OBSOLETE_INIT
1118 def_bool ALPHA || (ARM && !ARCH_L7200) || BLACKFIN || X86 || IA64 || M32R || MIPS || PARISC || PPC || (SUPERH64 && BLK_DEV_IDEPCI) || SPARC
1120 endif
1122 config BLK_DEV_HD_ONLY
1123 bool "Old hard disk (MFM/RLL/IDE) driver"
1124 depends on BLK_DEV_IDE=n
1125 help
1126 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1127 the newer enhanced driver, but this old one is still around for two
1128 reasons. Some older systems have strange timing problems and seem to
1129 work only with the old driver (which itself does not work with some
1130 newer systems). The other reason is that the old driver is smaller,
1131 since it lacks the enhanced functionality of the new one. This makes
1132 it a good choice for systems with very tight memory restrictions, or
1133 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1134 driver can save 13 KB or so of kernel memory.
1136 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1137 instead of this one. For more detailed information, read the
1138 Disk-HOWTO, available from
1139 <http://www.tldp.org/docs.html#howto>.
1141 config BLK_DEV_HD
1142 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY
1144 endif # IDE