2 # IDE ATA ATAPI Block device driver configuration
4 # Andre Hedrick <andre@linux-ide.org>
7 menu "ATA/ATAPI/MFM/RLL support"
10 tristate "ATA/ATAPI/MFM/RLL support"
12 If you say Y here, your kernel will be able to manage low cost mass
13 storage units such as ATA/(E)IDE and ATAPI units. The most common
14 cases are IDE hard drives and ATAPI CD-ROM drives.
16 If your system is pure SCSI and doesn't use these interfaces, you
19 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
20 for mass storage units such as hard disks. It was designed by
21 Western Digital and Compaq Computer in 1984. It was then named
22 ST506. Quite a number of disks use the IDE interface.
24 AT Attachment (ATA) is the superset of the IDE specifications.
25 ST506 was also called ATA-1.
27 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
28 ATA-3. It provides support for larger disks (up to 8.4GB by means of
29 the LBA standard), more disks (4 instead of 2) and for other mass
30 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
31 ATA-4 and provides faster (and more CPU friendly) transfer modes
32 than previous PIO (Programmed processor Input/Output) from previous
33 ATA/IDE standards by means of fast DMA controllers.
35 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
36 CD-ROM drives, similar in many respects to the SCSI protocol.
38 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
39 designed in order to prevent data corruption and disk crash by
40 detecting pre hardware failure conditions (heat, access time, and
41 the like...). Disks built since June 1995 may follow this standard.
42 The kernel itself doesn't manage this; however there are quite a
43 number of user programs such as smart that can query the status of
44 SMART parameters from disk drives.
46 To compile this driver as a module, choose M here: the
47 module will be called ide.
49 For further information, please read <file:Documentation/ide.txt>.
56 int "Max IDE interfaces"
60 This is the maximum number of IDE hardware interfaces that will
61 be supported by the driver. Make sure it is at least as high as
62 the number of IDE interfaces in your system.
65 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
67 If you say Y here, you will use the full-featured IDE driver to
68 control up to ten ATA/IDE interfaces, each being able to serve a
69 "master" and a "slave" device, for a total of up to twenty ATA/IDE
70 disk/cdrom/tape/floppy drives.
72 Useful information about large (>540 MB) IDE disks, multiple
73 interfaces, what to do if ATA/IDE devices are not automatically
74 detected, sound card ATA/IDE ports, module support, and other
75 topics, is contained in <file:Documentation/ide.txt>. For detailed
76 information about hard drives, consult the Disk-HOWTO and the
77 Multi-Disk-HOWTO, available from
78 <http://www.tldp.org/docs.html#howto>.
80 To fine-tune ATA/IDE drive/interface parameters for improved
81 performance, look for the hdparm package at
82 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
84 To compile this driver as a module, choose M here and read
85 <file:Documentation/ide.txt>. The module will be called ide-mod.
86 Do not compile this driver as a module if your root file system (the
87 one containing the directory /) is located on an IDE device.
89 If you have one or more IDE drives, say Y or M here. If your system
90 has no IDE drives, or if memory requirements are really tight, you
91 could say N here, and select the "Old hard disk driver" below
92 instead to save about 13 KB of memory in the kernel.
96 comment "Please see Documentation/ide.txt for help/info on IDE drives"
99 bool "Use old disk-only driver on primary interface"
100 depends on ((X86 && X86_PC9800!=y) || SH_MPC1211)
102 There are two drivers for MFM/RLL/IDE disks. Most people use just
103 the new enhanced driver by itself. This option however installs the
104 old hard disk driver to control the primary IDE/disk interface in
105 the system, leaving the new enhanced IDE driver to take care of only
106 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
107 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
108 IDE interface. Choosing this option may be useful for older systems
109 which have MFM/RLL/ESDI controller+drives at the primary port
110 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
113 Normally, just say N here; you will then use the new driver for all
116 config BLK_DEV_HD_IDE98
117 bool "Use old disk-only driver on primary interface"
118 depends on X86 && X86_PC9800
120 There are two drivers for MFM/RLL/IDE disks. Most people use just
121 the new enhanced driver by itself. This option however installs the
122 old hard disk driver to control the primary IDE/disk interface in
123 the system, leaving the new enhanced IDE driver to take care of only
124 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
125 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
126 IDE interface. Choosing this option may be useful for older systems
127 which have MFM/RLL/ESDI controller+drives at the primary port
128 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
131 Normally, just say N here; you will then use the new driver for all
134 config BLK_DEV_IDEDISK
135 tristate "Include IDE/ATA-2 DISK support"
137 This will include enhanced support for MFM/RLL/IDE hard disks. If
138 you have a MFM/RLL/IDE disk, and there is no special reason to use
139 the old hard disk driver instead, say Y. If you have an SCSI-only
140 system, you can say N here.
142 To compile this driver as a module, choose M here: the
143 module will be called ide-disk.
144 Do not compile this driver as a module if your root file system
145 (the one containing the directory /) is located on the IDE disk.
149 config IDEDISK_MULTI_MODE
150 bool "Use multi-mode by default"
151 depends on BLK_DEV_IDEDISK
153 If you get this error, try to say Y here:
155 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
156 hda: set_multmode: error=0x04 { DriveStatusError }
160 config IDEDISK_STROKE
161 bool "Auto-Geometry Resizing support"
162 depends on BLK_DEV_IDEDISK
164 Should you have a system w/ an AWARD Bios and your drives are larger
165 than 32GB and it will not boot, one is required to perform a few OEM
166 operations first. The option is called "STROKE" because it allows
167 one to "soft clip" the drive to work around a barrier limit. For
168 Maxtor drives it is called "jumpon.exe". Please search Maxtor's
169 web-site for "JUMPON.EXE". IBM has a similar tool at:
170 <http://www.storage.ibm.com/hdd/support/download.htm>.
172 If you are unsure, say N here.
175 tristate "PCMCIA IDE support"
178 Support for outboard IDE disks, tape drives, and CD-ROM drives
179 connected through a PCMCIA card.
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 Note that older versions of LILO (LInux LOader) cannot properly deal
197 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
198 <http://lilo.go.dyndns.org/>.
200 To compile this driver as a module, choose M here: the
201 module will be called ide-cd.
203 config BLK_DEV_IDETAPE
204 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
205 depends on EXPERIMENTAL
207 If you have an IDE tape drive using the ATAPI protocol, say Y.
208 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
209 similar to the SCSI protocol. If you have an SCSI tape drive
210 however, you can say N here.
212 You should also say Y if you have an OnStream DI-30 tape drive; this
213 will not work with the SCSI protocol, until there is support for the
214 SC-30 and SC-50 versions.
216 If you say Y here, the tape drive will be identified at boot time
217 along with other IDE devices, as "hdb" or "hdc", or something
218 similar, and will be mapped to a character device such as "ht0"
219 (check the boot messages with dmesg). Be sure to consult the
220 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
221 for usage information.
223 To compile this driver as a module, choose M here: the
224 module will be called ide-tape.
226 config BLK_DEV_IDEFLOPPY
227 tristate "Include IDE/ATAPI FLOPPY support"
229 If you have an IDE floppy drive which uses the ATAPI protocol,
230 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
231 drives, similar to the SCSI protocol.
233 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
234 this driver. For information about jumper settings and the question
235 of when a ZIP drive uses a partition table, see
236 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
237 (ATAPI PD-CD/CDR drives are not supported by this driver; support
238 for PD-CD/CDR drives is available if you answer Y to
239 "SCSI emulation support", below).
241 If you say Y here, the FLOPPY drive will be identified along with
242 other IDE devices, as "hdb" or "hdc", or something similar (check
243 the boot messages with dmesg).
245 To compile this driver as a module, choose M here: the
246 module will be called ide-floppy.
248 config BLK_DEV_IDESCSI
249 tristate "SCSI emulation support"
252 WARNING: ide-scsi is no longer needed for cd writing applications!
253 The 2.6 kernel supports direct writing to ide-cd, which eliminates
254 the need for ide-scsi + the entire scsi stack just for writing a
255 cd. The new method is more efficient in every way.
257 This will provide SCSI host adapter emulation for IDE ATAPI devices,
258 and will allow you to use a SCSI device driver instead of a native
261 This is useful if you have an ATAPI device for which no native
262 driver has been written (for example, an ATAPI PD-CD drive);
263 you can then use this emulation together with an appropriate SCSI
264 device driver. In order to do this, say Y here and to "SCSI support"
265 and "SCSI generic support", below. You must then provide the kernel
266 command line "hdx=ide-scsi" (try "man bootparam" or see the
267 documentation of your boot loader (lilo or loadlin) about how to
268 pass options to the kernel at boot time) for devices if you want the
269 native EIDE sub-drivers to skip over the native support, so that
270 this SCSI emulation can be used instead.
272 Note that this option does NOT allow you to attach SCSI devices to a
273 box that doesn't have a SCSI host adapter installed.
275 If both this SCSI emulation and native ATAPI support are compiled
276 into the kernel, the native support will be used.
278 config IDE_TASK_IOCTL
279 bool "IDE Taskfile Access"
281 This is a direct raw access to the media. It is a complex but
282 elegant solution to test and validate the domain of the hardware and
283 perform below the driver data recover if needed. This is the most
284 basic form of media-forensics.
286 If you are unsure, say N here.
288 config IDE_TASKFILE_IO
289 bool 'IDE Taskfile IO (EXPERIMENTAL)'
290 depends on EXPERIMENTAL
293 Use new taskfile IO code.
295 It is safe to say Y to this question, in most cases.
297 comment "IDE chipset support/bugfixes"
300 tristate "generic/default IDE chipset support"
305 config BLK_DEV_CMD640
306 bool "CMD640 chipset bugfix/support"
309 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
310 Pentium motherboards, usually in combination with a "Neptune" or
311 "SiS" chipset. Unfortunately, it has a number of rather nasty
312 design flaws that can cause severe data corruption under many common
313 conditions. Say Y here to include code which tries to automatically
314 detect and correct the problems under Linux. This option also
315 enables access to the secondary IDE ports in some CMD640 based
318 This driver will work automatically in PCI based systems (most new
319 systems have PCI slots). But if your system uses VESA local bus
320 (VLB) instead of PCI, you must also supply a kernel boot parameter
321 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
322 bootparam" or see the documentation of your boot loader about how to
323 pass options to the kernel.)
325 The CMD640 chip is also used on add-in cards by Acculogic, and on
326 the "CSA-6400E PCI to IDE controller" that some people have. For
327 details, read <file:Documentation/ide.txt>.
329 config BLK_DEV_CMD640_ENHANCED
330 bool "CMD640 enhanced support"
331 depends on BLK_DEV_CMD640
333 This option includes support for setting/autotuning PIO modes and
334 prefetch on CMD640 IDE interfaces. For details, read
335 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
336 and your BIOS does not already do this for you, then say Y here.
339 config BLK_DEV_IDEPNP
340 bool "PNP EIDE support"
343 If you have a PnP (Plug and Play) compatible EIDE card and
344 would like the kernel to automatically detect and activate
347 config BLK_DEV_IDEPCI
348 bool "PCI IDE chipset support" if PCI
349 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
351 Say Y here for PCI systems which use IDE drive(s).
352 This option helps the IDE driver to automatically detect and
353 configure all PCI-based IDE interfaces in your system.
355 config IDEPCI_SHARE_IRQ
356 bool "Sharing PCI IDE interrupts support"
357 depends on PCI && BLK_DEV_IDEPCI
359 Some ATA/IDE chipsets have hardware support which allows for
360 sharing a single IRQ with other cards. To enable support for
361 this in the ATA/IDE driver, say Y here.
363 It is safe to say Y to this question, in most cases.
366 config BLK_DEV_OFFBOARD
367 bool "Boot off-board chipsets first support"
368 depends on PCI && BLK_DEV_IDEPCI
370 Normally, IDE controllers built into the motherboard (on-board
371 controllers) are assigned to ide0 and ide1 while those on add-in PCI
372 cards (off-board controllers) are relegated to ide2 and ide3.
373 Answering Y here will allow you to reverse the situation, with
374 off-board controllers on ide0/1 and on-board controllers on ide2/3.
375 This can improve the usability of some boot managers such as lilo
376 when booting from a drive on an off-board controller.
378 If you say Y here, and you actually want to reverse the device scan
379 order as explained above, you also need to issue the kernel command
380 line option "ide=reverse". (Try "man bootparam" or see the
381 documentation of your boot loader (lilo or loadlin) about how to
382 pass options to the kernel at boot time.)
384 Note that, if you do this, the order of the hd* devices will be
385 rearranged which may require modification of fstab and other files.
389 config BLK_DEV_GENERIC
390 bool "Generic PCI IDE Chipset Support"
391 depends on PCI && BLK_DEV_IDEPCI
393 config BLK_DEV_OPTI621
394 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
395 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
397 This is a driver for the OPTi 82C621 EIDE controller.
398 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
400 config BLK_DEV_RZ1000
401 tristate "RZ1000 chipset bugfix/support"
402 depends on PCI && BLK_DEV_IDEPCI && X86
404 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
405 Pentium motherboards, usually along with the "Neptune" chipset.
406 Unfortunately, it has a rather nasty design flaw that can cause
407 severe data corruption under many conditions. Say Y here to include
408 code which automatically detects and corrects the problem under
409 Linux. This may slow disk throughput by a few percent, but at least
410 things will operate 100% reliably.
412 config BLK_DEV_SL82C105
413 tristate "Winbond SL82c105 support"
414 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
416 If you have a Winbond SL82c105 IDE controller, say Y here to enable
417 special configuration for this chip. This is common on various CHRP
418 motherboards, but could be used elsewhere. If in doubt, say Y.
420 config BLK_DEV_IDEDMA_PCI
421 bool "Generic PCI bus-master DMA support"
422 depends on PCI && BLK_DEV_IDEPCI
424 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
425 is capable of bus-master DMA operation (most Pentium PCI systems),
426 you will want to say Y here to reduce CPU overhead. You can then use
427 the "hdparm" utility to enable DMA for drives for which it was not
428 enabled automatically. By default, DMA is not enabled automatically
429 for these drives, but you can change that by saying Y to the
430 following question "Use DMA by default when available". You can get
431 the latest version of the hdparm utility from
432 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
434 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
435 and the file <file:Documentation/ide.txt> for more information.
437 It is safe to say Y to this question.
439 if BLK_DEV_IDEDMA_PCI
441 # TCQ is disabled for now
442 config BLK_DEV_IDE_TCQ
443 bool "ATA tagged command queueing (EXPERIMENTAL)"
444 depends on EXPERIMENTAL && n
446 Support for tagged command queueing on ATA disk drives. This enables
447 the IDE layer to have multiple in-flight requests on hardware that
448 supports it. For now this includes the IBM Deskstar series drives,
449 such as the 22GXP, 75GXP, 40GV, 60GXP, and 120GXP (ie any Deskstar made
450 in the last couple of years), and at least some of the Western
451 Digital drives in the Expert series (by nature of really being IBM
454 If you have such a drive, say Y here.
456 config BLK_DEV_IDE_TCQ_DEFAULT
457 bool "TCQ on by default"
458 depends on BLK_DEV_IDE_TCQ
460 Enable tagged command queueing unconditionally on drives that report
461 support for it. Regardless of the chosen value here, tagging can be
462 controlled at run time:
464 echo "using_tcq:32" > /proc/ide/hdX/settings
466 where any value between 1-32 selects chosen queue depth and enables
467 TCQ, and 0 disables it. hdparm version 4.7 an above also support
470 Generally say Y here.
472 config BLK_DEV_IDE_TCQ_DEPTH
473 int "Default queue depth"
474 depends on BLK_DEV_IDE_TCQ
477 Maximum size of commands to enable per-drive. Any value between 1
478 and 32 is valid, with 32 being the maxium that the hardware supports.
480 You probably just want the default of 32 here. If you enter an invalid
481 number, the default value will be used.
483 config BLK_DEV_IDEDMA_FORCED
484 bool "Force enable legacy 2.0.X HOSTS to use DMA"
486 This is an old piece of lost code from Linux 2.0 Kernels.
488 Generally say N here.
490 config IDEDMA_PCI_AUTO
491 bool "Use PCI DMA by default when available"
493 Prior to kernel version 2.1.112, Linux used to automatically use
494 DMA for IDE drives and chipsets which support it. Due to concerns
495 about a couple of cases where buggy hardware may have caused damage,
496 the default is now to NOT use DMA automatically. To revert to the
497 previous behaviour, say Y to this question.
499 If you suspect your hardware is at all flakey, say N here.
500 Do NOT email the IDE kernel people regarding this issue!
502 It is normally safe to answer Y to this question unless your
503 motherboard uses a VIA VP2 chipset, in which case you should say N.
505 config IDEDMA_ONLYDISK
506 bool "Enable DMA only for disks "
507 depends on IDEDMA_PCI_AUTO
509 This is used if you know your ATAPI Devices are going to fail DMA
512 Generally say N here.
516 depends on PCI && BLK_DEV_IDEPCI
517 default BLK_DEV_IDEDMA_PCI
519 config BLK_DEV_AEC62XX
520 tristate "AEC62XX chipset support"
522 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
523 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
524 speeds and to configure the chip to optimum performance.
526 config BLK_DEV_ALI15X3
527 tristate "ALI M15x3 chipset support"
529 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
530 onboard chipsets. It also tests for Simplex mode and enables
531 normal dual channel support.
533 If you say Y here, you also need to say Y to "Use DMA by default
534 when available", above. Please read the comments at the top of
535 <file:drivers/ide/pci/alim15x3.c>.
540 bool "ALI M15x3 WDC support (DANGEROUS)"
541 depends on BLK_DEV_ALI15X3
543 This allows for UltraDMA support for WDC drives that ignore CRC
544 checking. You are a fool for enabling this option, but there have
545 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
546 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
549 Using this option can allow WDC drives to run at ATA-4/5 transfer
550 rates with only an ATA-2 support structure.
554 config BLK_DEV_AMD74XX
555 tristate "AMD and nVidia IDE support"
557 This driver adds explicit support for AMD-7xx and AMD-8111 chips
558 and also for the nVidia nForce chip. This allows the kernel to
559 change PIO, DMA and UDMA speeds and to configure the chip to
562 config BLK_DEV_ATIIXP
563 tristate "ATI IXP chipset IDE support"
566 This driver adds explicit support for ATI IXP chipset.
567 This allows the kernel to change PIO, DMA and UDMA speeds
568 and to configure the chip to optimum performance.
570 Say Y here if you have an ATI IXP chipset IDE controller.
572 config BLK_DEV_CMD64X
573 tristate "CMD64{3|6|8|9} chipset support"
575 Say Y here if you have an IDE controller which uses any of these
576 chipsets: CMD643, CMD646, or CMD648.
578 config BLK_DEV_TRIFLEX
579 tristate "Compaq Triflex IDE support"
581 Say Y here if you have a Compaq Triflex IDE controller, such
582 as those commonly found on Compaq Pentium-Pro systems
584 config BLK_DEV_CY82C693
585 tristate "CY82C693 chipset support"
587 This driver adds detection and support for the CY82C693 chipset
588 used on Digital's PC-Alpha 164SX boards.
590 If you say Y here, you need to say Y to "Use DMA by default
591 when available" as well.
593 config BLK_DEV_CS5520
594 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
595 depends on EXPERIMENTAL
597 Include support for PIO tuning an virtual DMA on the Cyrix MediaGX
598 5510/5520 chipset. This will automatically be detected and
601 It is safe to say Y to this question.
603 config BLK_DEV_CS5530
604 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
606 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
607 will automatically be detected and configured if found.
609 It is safe to say Y to this question.
611 config BLK_DEV_HPT34X
612 tristate "HPT34X chipset support"
614 This driver adds up to 4 more EIDE devices sharing a single
615 interrupt. The HPT343 chipset in its current form is a non-bootable
616 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
617 PCI UDMA controllers. This driver requires dynamic tuning of the
618 chipset during the ide-probe at boot time. It is reported to support
619 DVD II drives, by the manufacturer.
621 config HPT34X_AUTODMA
622 bool "HPT34X AUTODMA support (EXPERIMENTAL)"
623 depends on BLK_DEV_HPT34X && EXPERIMENTAL
625 This is a dangerous thing to attempt currently! Please read the
626 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
627 here, then say Y to "Use DMA by default when available" as well.
631 config BLK_DEV_HPT366
632 tristate "HPT36X/37X chipset support"
634 HPT366 is an Ultra DMA chipset for ATA-66.
635 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
636 HPT370 is an Ultra DMA chipset for ATA-100.
637 HPT372 is an Ultra DMA chipset for ATA-100.
638 HPT374 is an Ultra DMA chipset for ATA-100.
640 This driver adds up to 4 more EIDE devices sharing a single
643 The HPT366 chipset in its current form is bootable. One solution
644 for this problem are special LILO commands for redirecting the
645 reference to device 0x80. The other solution is to say Y to "Boot
646 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
647 your mother board has the chipset natively mounted. Regardless one
648 should use the fore mentioned option and call at LILO or include
649 "ide=reverse" in LILO's append-line.
651 This driver requires dynamic tuning of the chipset during the
652 ide-probe at boot. It is reported to support DVD II drives, by the
655 config BLK_DEV_SC1200
656 tristate "National SCx200 chipset support"
658 This driver adds support for the built in IDE on the National
659 SCx200 series of embedded x86 "Geode" systems
662 tristate "Intel PIIXn chipsets support"
664 This driver adds explicit support for Intel PIIX and ICH chips
665 and also for the Efar Victory66 (slc90e66) chip. This allows
666 the kernel to change PIO, DMA and UDMA speeds and to configure
667 the chip to optimum performance.
669 config BLK_DEV_IT8172
670 bool "IT8172 IDE support"
671 depends on (MIPS_ITE8172 || MIPS_IVR)
673 Say Y here to support the on-board IDE controller on the Integrated
674 Technology Express, Inc. ITE8172 SBC. Vendor page at
675 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
676 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
678 config BLK_DEV_NS87415
679 tristate "NS87415 chipset support"
681 This driver adds detection and support for the NS87415 chip
682 (used in SPARC64, among others).
684 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
686 config BLK_DEV_PDC202XX_OLD
687 tristate "PROMISE PDC202{46|62|65|67} support"
689 Promise Ultra33 or PDC20246
690 Promise Ultra66 or PDC20262
691 Promise Ultra100 or PDC20265/PDC20267/PDC20268
693 This driver adds up to 4 more EIDE devices sharing a single
694 interrupt. This add-on card is a bootable PCI UDMA controller. Since
695 multiple cards can be installed and there are BIOS ROM problems that
696 happen if the BIOS revisions of all installed cards (three-max) do
697 not match, the driver attempts to do dynamic tuning of the chipset
698 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
699 for more than one card. This card may require that you say Y to
700 "Special UDMA Feature".
702 If you say Y here, you need to say Y to "Use DMA by default when
705 Please read the comments at the top of
706 <file:drivers/ide/pci/pdc202xx_old.c>.
710 config PDC202XX_BURST
711 bool "Special UDMA Feature"
712 depends on BLK_DEV_PDC202XX_OLD
714 This option causes the pdc202xx driver to enable UDMA modes on the
715 PDC202xx even when the PDC202xx BIOS has not done so.
717 It was originally designed for the PDC20246/Ultra33, whose BIOS will
718 only setup UDMA on the first two PDC20246 cards. It has also been
719 used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
720 when the PDC20265 BIOS has been disabled (for faster boot up).
722 Please read the comments at the top of
723 <file:drivers/ide/pci/pdc202xx_old.c>.
727 config BLK_DEV_PDC202XX_NEW
728 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
730 # FIXME - probably wants to be one for old and for new
731 config PDC202XX_FORCE
732 bool "Enable controller even if disabled by BIOS"
733 depends on BLK_DEV_PDC202XX_NEW
735 Enable the PDC202xx controller even if it has been disabled in the BIOS setup.
738 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
740 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
743 config BLK_DEV_SGIIOC4
744 tristate "Silicon Graphics IOC4 chipset support"
745 depends on IA64_SGI_SN2 || IA64_GENERIC
747 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
748 chipset, which has one channel and can support two devices.
749 Please say Y here if you have an Altix System from SGI.
751 config BLK_DEV_SIIMAGE
752 tristate "Silicon Image chipset support"
754 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
755 3112 (Serial ATA) chips.
757 config BLK_DEV_SIS5513
758 tristate "SiS5513 chipset support"
761 This driver ensures (U)DMA support for SIS5513 chipset family based
764 The following chipsets are supported:
765 ATA16: SiS5511, SiS5513
766 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
767 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
768 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
771 If you say Y here, you need to say Y to "Use DMA by default when
774 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
776 config BLK_DEV_SLC90E66
777 tristate "SLC90E66 chipset support"
779 This driver ensures (U)DMA support for Victroy66 SouthBridges for
780 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
781 The nice thing about it is that you can mix Ultra/DMA/PIO devices
782 and it will handle timing cycles. Since this is an improved
783 look-a-like to the PIIX4 it should be a nice addition.
785 If you say Y here, you need to say Y to "Use DMA by default when
788 Please read the comments at the top of
789 <file:drivers/ide/pci/slc90e66.c>.
791 config BLK_DEV_TRM290
792 tristate "Tekram TRM290 chipset support"
794 This driver adds support for bus master DMA transfers
795 using the Tekram TRM290 PCI IDE chip. Volunteers are
796 needed for further tweaking and development.
797 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
799 config BLK_DEV_VIA82CXXX
800 tristate "VIA82CXXX chipset support"
802 This driver adds explicit support for VIA BusMastering IDE chips.
803 This allows the kernel to change PIO, DMA and UDMA speeds and to
804 configure the chip to optimum performance.
808 config BLK_DEV_IDE_PMAC
809 bool "Builtin PowerMac IDE support"
812 This driver provides support for the built-in IDE controller on
813 most of the recent Apple Power Macintoshes and PowerBooks.
816 config BLK_DEV_IDE_PMAC_ATA100FIRST
817 bool "Probe internal ATA/100 (Kauai) first"
818 depends on BLK_DEV_IDE_PMAC
820 This option will cause the ATA/100 controller found in UniNorth2
821 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...)
822 to be probed before the ATA/66 and ATA/33 controllers. Without
823 these, those machine used to have the hard disk on hdc and the
824 CD-ROM on hda. This option changes this to more natural hda for
825 hard disk and hdc for CD-ROM.
827 config BLK_DEV_IDEDMA_PMAC
828 bool "PowerMac IDE DMA support"
829 depends on BLK_DEV_IDE_PMAC
831 This option allows the driver for the built-in IDE controller on
832 Power Macintoshes and PowerBooks to use DMA (direct memory access)
833 to transfer data to and from memory. Saying Y is safe and improves
836 config BLK_DEV_IDE_PMAC_BLINK
837 bool "Blink laptop LED on drive activity"
838 depends on BLK_DEV_IDE_PMAC && ADB_PMU
840 This option enables the use of the sleep LED as a hard drive
843 config BLK_DEV_IDEDMA_PMAC_AUTO
844 bool "Use DMA by default"
845 depends on BLK_DEV_IDEDMA_PMAC
847 This option allows the driver for the built-in IDE controller on
848 Power Macintoshes and PowerBooks to use DMA automatically, without
849 it having to be explicitly enabled. This option is provided because
850 of concerns about a couple of cases where using DMA on buggy PC
851 hardware may have caused damage. Saying Y should be safe on all
854 config BLK_DEV_IDE_SWARM
855 bool "SWARM onboard IDE support"
856 depends on SIBYTE_SWARM
858 config BLK_DEV_IDE_ICSIDE
859 tristate "ICS IDE interface support"
860 depends on ARM && ARCH_ACORN
862 On Acorn systems, say Y here if you wish to use the ICS IDE
863 interface card. This is not required for ICS partition support.
864 If you are unsure, say N to this.
866 config BLK_DEV_IDEDMA_ICS
867 bool "ICS DMA support"
868 depends on BLK_DEV_IDE_ICSIDE
870 Say Y here if you want to add DMA (Direct Memory Access) support to
873 config IDEDMA_ICS_AUTO
874 bool "Use ICS DMA by default"
875 depends on BLK_DEV_IDEDMA_ICS
877 Prior to kernel version 2.1.112, Linux used to automatically use
878 DMA for IDE drives and chipsets which support it. Due to concerns
879 about a couple of cases where buggy hardware may have caused damage,
880 the default is now to NOT use DMA automatically. To revert to the
881 previous behaviour, say Y to this question.
883 If you suspect your hardware is at all flakey, say N here.
884 Do NOT email the IDE kernel people regarding this issue!
886 config BLK_DEV_IDE_RAPIDE
887 tristate "RapIDE interface support"
888 depends on ARM && ARCH_ACORN
890 Say Y here if you want to support the Yellowstone RapIDE controller
891 manufactured for use with Acorn computers.
894 bool "Amiga Gayle IDE interface support"
897 This is the IDE driver for the Amiga Gayle IDE interface. It supports
898 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
899 This includes builtin IDE interfaces on some Amiga models (A600,
900 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
901 bus (M-Tech E-Matrix 530 expansion card).
902 Say Y if you have an Amiga with a Gayle IDE interface and want to use
903 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to
905 Note that you also have to enable Zorro bus support if you want to
906 use Gayle IDE interfaces on the Zorro expansion bus.
908 config BLK_DEV_IDEDOUBLER
909 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
910 depends on BLK_DEV_GAYLE && EXPERIMENTAL
912 This driver provides support for the so-called `IDE doublers' (made
913 by various manufacturers, e.g. Eyetech) that can be connected to the
914 builtin IDE interface of some Amiga models. Using such an IDE
915 doubler, you can connect up to four instead of two IDE devices on
916 the Amiga's builtin IDE interface.
918 Note that the normal Amiga Gayle IDE driver may not work correctly
919 if you have an IDE doubler and don't enable this driver!
921 Say Y if you have an IDE doubler. The driver is enabled at kernel
922 runtime using the "ide=doubler" kernel boot parameter.
924 config BLK_DEV_BUDDHA
925 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
926 depends on ZORRO && EXPERIMENTAL
928 This is the IDE driver for the IDE interfaces on the Buddha,
929 Catweasel and X-Surf expansion boards. It supports up to two interfaces
930 on the Buddha, three on the Catweasel and two on the X-Surf.
932 Say Y if you have a Buddha or Catweasel expansion board and want to
933 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
934 to one of its IDE interfaces.
936 config BLK_DEV_FALCON_IDE
937 bool "Falcon IDE interface support"
940 This is the IDE driver for the builtin IDE interface on the Atari
941 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
942 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
945 config BLK_DEV_MAC_IDE
946 bool "Macintosh Quadra/Powerbook IDE interface support"
949 This is the IDE driver for the builtin IDE interface on some m68k
950 Macintosh models. It supports both the `Quadra style' (used in
951 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
952 (used in the Powerbook 150 and 190 models) IDE interface.
954 Say Y if you have such an Macintosh model and want to use IDE
955 devices (hard disks, CD-ROM drives, etc.) that are connected to the
956 builtin IDE interface.
958 config BLK_DEV_Q40IDE
959 bool "Q40/Q60 IDE interface support"
962 Enable the on-board IDE controller in the Q40/Q60. This should
963 normally be on; disable it only if you are running a custom hard
964 drive subsystem through an expansion card.
966 config BLK_DEV_MPC8xx_IDE
967 bool "MPC8xx IDE support"
970 This option provides support for IDE on Motorola MPC8xx Systems.
971 Please see 'Type of MPC8xx IDE interface' for details.
976 prompt "Type of MPC8xx IDE interface"
977 depends on BLK_DEV_MPC8xx_IDE
978 default IDE_8xx_PCCARD
980 config IDE_8xx_PCCARD
983 Select how the IDE devices are connected to the MPC8xx system:
985 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
986 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
987 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
990 8xx_DIRECT is used for directly connected IDE devices using the 8xx
991 internal PCMCIA interface (example: IVMS8 systems)
993 EXT_DIRECT is used for IDE devices directly connected to the 8xx
994 bus using some glue logic, but _not_ the 8xx internal
995 PCMCIA interface (example: IDIF860 systems)
997 config IDE_8xx_DIRECT
1000 config IDE_EXT_DIRECT
1007 bool "Other IDE chipset support"
1010 Say Y here if you want to include enhanced support for various IDE
1011 interface chipsets used on motherboards and add-on cards. You can
1012 then pick your particular IDE chip from among the following options.
1013 This enhanced support may be necessary for Linux to be able to
1014 access the 3rd/4th drives in some systems. It may also enable
1015 setting of higher speed I/O rates to improve system performance with
1016 these chipsets. Most of these also require special kernel boot
1017 parameters to actually turn on the support at runtime; you can find
1018 a list of these in the file <file:Documentation/ide.txt>.
1020 People with SCSI-only systems can say N here.
1024 comment "Note: most of these also require special kernel boot parameters"
1026 config BLK_DEV_4DRIVES
1027 bool "Generic 4 drives/port support"
1029 Certain older chipsets, including the Tekram 690CD, use a single set
1030 of I/O ports at 0x1f0 to control up to four drives, instead of the
1031 customary two drives per port. Support for this can be enabled at
1032 runtime using the "ide0=four" kernel boot parameter if you say Y
1035 config BLK_DEV_ALI14XX
1036 tristate "ALI M14xx support"
1038 This driver is enabled at runtime using the "ide0=ali14xx" kernel
1039 boot parameter. It enables support for the secondary IDE interface
1040 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1041 I/O speeds to be set as well. See the files
1042 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
1045 config BLK_DEV_DTC2278
1046 tristate "DTC-2278 support"
1048 This driver is enabled at runtime using the "ide0=dtc2278" kernel
1049 boot parameter. It enables support for the secondary IDE interface
1050 of the DTC-2278 card, and permits faster I/O speeds to be set as
1051 well. See the <file:Documentation/ide.txt> and
1052 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1054 config BLK_DEV_HT6560B
1055 tristate "Holtek HT6560B support"
1057 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1058 boot parameter. It enables support for the secondary IDE interface
1059 of the Holtek card, and permits faster I/O speeds to be set as well.
1060 See the <file:Documentation/ide.txt> and
1061 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1063 config BLK_DEV_PDC4030
1064 tristate "PROMISE DC4030 support (EXPERIMENTAL)"
1065 depends on BLK_DEV_IDEDISK && EXPERIMENTAL
1067 This driver provides support for the secondary IDE interface and
1068 cache of the original Promise IDE chipsets, e.g. DC4030 and DC5030.
1069 It is nothing to do with the later range of Promise UDMA chipsets -
1070 see the PDC_202XX support for these. CD-ROM and TAPE devices are not
1071 supported (and probably never will be since I don't think the cards
1072 support them). This driver is enabled at runtime using the "ide0=dc4030"
1073 or "ide1=dc4030" kernel boot parameter. See the
1074 <file:drivers/ide/legacy/pdc4030.c> file for more info.
1076 config BLK_DEV_QD65XX
1077 tristate "QDI QD65xx support"
1079 This driver is enabled at runtime using the "ide0=qd65xx" kernel
1080 boot parameter. It permits faster I/O speeds to be set. See the
1081 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
1084 config BLK_DEV_UMC8672
1085 tristate "UMC-8672 support"
1087 This driver is enabled at runtime using the "ide0=umc8672" kernel
1088 boot parameter. It enables support for the secondary IDE interface
1089 of the UMC-8672, and permits faster I/O speeds to be set as well.
1090 See the files <file:Documentation/ide.txt> and
1091 <file:drivers/ide/legacy/umc8672.c> for more info.
1095 config BLK_DEV_IDEDMA
1096 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1099 bool "IGNORE word93 Validation BITS"
1100 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1102 There are unclear terms in ATA-4 and ATA-5 standards how certain
1103 hardware (an 80c ribbon) should be detected. Different interpretations
1104 of the standards have been released in hardware. This causes problems:
1105 for example, a host with Ultra Mode 4 (or higher) will not run
1106 in that mode with an 80c ribbon.
1108 If you are experiencing compatibility or performance problems, you
1109 MAY try to answering Y here. However, it does not necessarily solve
1110 any of your problems, it could even cause more of them.
1112 It is normally safe to answer Y; however, the default is N.
1115 def_bool IDEDMA_PCI_AUTO || BLK_DEV_IDEDMA_PMAC_AUTO || IDEDMA_ICS_AUTO
1119 config BLK_DEV_HD_ONLY
1120 bool "Old hard disk (MFM/RLL/IDE) driver"
1121 depends on BLK_DEV_IDE=n
1123 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1124 the newer enhanced driver, but this old one is still around for two
1125 reasons. Some older systems have strange timing problems and seem to
1126 work only with the old driver (which itself does not work with some
1127 newer systems). The other reason is that the old driver is smaller,
1128 since it lacks the enhanced functionality of the new one. This makes
1129 it a good choice for systems with very tight memory restrictions, or
1130 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1131 driver can save 13 KB or so of kernel memory.
1133 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1134 instead of this one. For more detailed information, read the
1135 Disk-HOWTO, available from
1136 <http://www.tldp.org/docs.html#howto>.
1139 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY