| blob | 1e38c471208ab6a24c386a448d3e04638c44e9ce |
1 #
2 # IDE ATA ATAPI Block device driver configuration
3 #
4 # Andre Hedrick <andre@linux-ide.org>
5 #
7 menu "ATA/ATAPI/MFM/RLL support"
9 config IDE
10 tristate "ATA/ATAPI/MFM/RLL support"
11 ---help---
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
17 can say N here.
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 If you want to compile this driver as a module ( = code which can be
47 inserted in and removed from the running kernel whenever you want),
48 say M here and read <file:Documentation/modules.txt>. The module
49 will be called ide.
51 For further information, please read <file:Documentation/ide.txt>.
53 If unsure, say Y.
55 config IDE_MAX_HWIFS
56 int "Max IDE interfaces"
57 depends on ALPHA && IDE
58 default 4
59 help
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.
64 menu "IDE, ATA and ATAPI Block devices"
65 depends on IDE!=n
67 config BLK_DEV_IDE
68 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support"
69 depends on IDE
70 ---help---
71 If you say Y here, you will use the full-featured IDE driver to
72 control up to ten ATA/IDE interfaces, each being able to serve a
73 "master" and a "slave" device, for a total of up to twenty ATA/IDE
74 disk/cdrom/tape/floppy drives.
76 Useful information about large (>540 MB) IDE disks, multiple
77 interfaces, what to do if ATA/IDE devices are not automatically
78 detected, sound card ATA/IDE ports, module support, and other
79 topics, is contained in <file:Documentation/ide.txt>. For detailed
80 information about hard drives, consult the Disk-HOWTO and the
81 Multi-Disk-HOWTO, available from
82 <http://www.tldp.org/docs.html#howto>.
84 To fine-tune ATA/IDE drive/interface parameters for improved
85 performance, look for the hdparm package at
86 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
88 If you want to compile this driver as a module ( = code which can be
89 inserted in and removed from the running kernel whenever you want),
90 say M here and read <file:Documentation/modules.txt> and
91 <file:Documentation/ide.txt>. The module will be called ide-mod.
92 Do not compile this driver as a module if your root file system (the
93 one containing the directory /) is located on an IDE device.
95 If you have one or more IDE drives, say Y or M here. If your system
96 has no IDE drives, or if memory requirements are really tight, you
97 could say N here, and select the "Old hard disk driver" below
98 instead to save about 13 KB of memory in the kernel.
100 comment "Please see Documentation/ide.txt for help/info on IDE drives"
102 config BLK_DEV_HD_IDE
103 bool "Use old disk-only driver on primary interface"
104 depends on BLK_DEV_IDE && X86 && X86_PC9800!=y
105 ---help---
106 There are two drivers for MFM/RLL/IDE disks. Most people use just
107 the new enhanced driver by itself. This option however installs the
108 old hard disk driver to control the primary IDE/disk interface in
109 the system, leaving the new enhanced IDE driver to take care of only
110 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
111 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
112 IDE interface. Choosing this option may be useful for older systems
113 which have MFM/RLL/ESDI controller+drives at the primary port
114 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
115 addresses.
117 Normally, just say N here; you will then use the new driver for all
118 4 interfaces.
120 config BLK_DEV_HD_IDE98
121 bool "Use old disk-only driver on primary interface"
122 depends on BLK_DEV_IDE && X86 && X86_PC9800
123 ---help---
124 There are two drivers for MFM/RLL/IDE disks. Most people use just
125 the new enhanced driver by itself. This option however installs the
126 old hard disk driver to control the primary IDE/disk interface in
127 the system, leaving the new enhanced IDE driver to take care of only
128 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
129 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
130 IDE interface. Choosing this option may be useful for older systems
131 which have MFM/RLL/ESDI controller+drives at the primary port
132 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
133 addresses.
135 Normally, just say N here; you will then use the new driver for all
136 4 interfaces.
138 config BLK_DEV_HD
139 bool
140 default BLK_DEV_HD_ONLY if BLK_DEV_IDE=n
141 default BLK_DEV_HD_IDE if BLK_DEV_IDE
143 config BLK_DEV_IDEDISK
144 tristate "Include IDE/ATA-2 DISK support"
145 depends on BLK_DEV_IDE
146 ---help---
147 This will include enhanced support for MFM/RLL/IDE hard disks. If
148 you have a MFM/RLL/IDE disk, and there is no special reason to use
149 the old hard disk driver instead, say Y. If you have an SCSI-only
150 system, you can say N here.
152 If you want to compile this driver as a module ( = code which can be
153 inserted in and removed from the running kernel whenever you want),
154 say M here and read <file:Documentation/modules.txt>. The module
155 will be called ide-disk. Do not compile this driver as a module
156 if your root file system (the one containing the directory /) is
157 located on the IDE disk. If unsure, say Y.
159 config IDEDISK_MULTI_MODE
160 bool "Use multi-mode by default"
161 depends on BLK_DEV_IDEDISK
162 help
163 If you get this error, try to say Y here:
165 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
166 hda: set_multmode: error=0x04 { DriveStatusError }
168 If in doubt, say N.
170 config IDEDISK_STROKE
171 bool "Auto-Geometry Resizing support"
172 depends on BLK_DEV_IDEDISK
173 help
174 Should you have a system w/ an AWARD Bios and your drives are larger
175 than 32GB and it will not boot, one is required to perform a few OEM
176 operations first. The option is called "STROKE" because it allows
177 one to "soft clip" the drive to work around a barrier limit. For
178 Maxtor drives it is called "jumpon.exe". Please search Maxtor's
179 web-site for "JUMPON.EXE". IBM has a similar tool at:
180 <http://www.storage.ibm.com/hdd/support/download.htm>.
182 If you are unsure, say N here.
184 config BLK_DEV_IDECS
185 tristate "PCMCIA IDE support"
186 depends on BLK_DEV_IDE && PCMCIA
187 help
188 Support for outboard IDE disks, tape drives, and CD-ROM drives
189 connected through a PCMCIA card.
191 config BLK_DEV_IDECD
192 tristate "Include IDE/ATAPI CDROM support"
193 depends on BLK_DEV_IDE
194 ---help---
195 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
196 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
197 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
198 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
199 double(2X) or better speed drives.
201 If you say Y here, the CD-ROM drive will be identified at boot time
202 along with other IDE devices, as "hdb" or "hdc", or something
203 similar (check the boot messages with dmesg). If this is your only
204 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
205 to say Y or M to "ISO 9660 CD-ROM file system support".
207 Note that older versions of LILO (LInux LOader) cannot properly deal
208 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
209 <ftp://brun.dyndns.org/pub/linux/lilo/>.
211 If you want to compile the driver as a module ( = code which can be
212 inserted in and removed from the running kernel whenever you want),
213 say M here and read <file:Documentation/modules.txt>. The module
214 will be called ide-cd.
216 #dep_tristate ' Include IDE/ATAPI TAPE support' CONFIG_BLK_DEV_IDETAPE $CONFIG_BLK_DEV_IDE
217 config BLK_DEV_IDEFLOPPY
218 tristate "Include IDE/ATAPI FLOPPY support"
219 depends on BLK_DEV_IDE
220 ---help---
221 If you have an IDE floppy drive which uses the ATAPI protocol,
222 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
223 drives, similar to the SCSI protocol.
225 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
226 this driver. For information about jumper settings and the question
227 of when a ZIP drive uses a partition table, see
228 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
229 (ATAPI PD-CD/CDR drives are not supported by this driver; support
230 for PD-CD/CDR drives is available if you answer Y to
231 "SCSI emulation support", below).
233 If you say Y here, the FLOPPY drive will be identified along with
234 other IDE devices, as "hdb" or "hdc", or something similar (check
235 the boot messages with dmesg).
237 If you want to compile the driver as a module ( = code which can be
238 inserted in and removed from the running kernel whenever you want),
239 say M here and read <file:Documentation/modules.txt>. The module
240 will be called ide-floppy.
242 config BLK_DEV_IDESCSI
243 tristate "SCSI emulation support"
244 depends on BLK_DEV_IDE && SCSI
245 ---help---
246 This will provide SCSI host adapter emulation for IDE ATAPI devices,
247 and will allow you to use a SCSI device driver instead of a native
248 ATAPI driver.
250 This is useful if you have an ATAPI device for which no native
251 driver has been written (for example, an ATAPI PD-CD or CDR drive);
252 you can then use this emulation together with an appropriate SCSI
253 device driver. In order to do this, say Y here and to "SCSI support"
254 and "SCSI generic support", below. You must then provide the kernel
255 command line "hdx=ide-scsi" (try "man bootparam" or see the
256 documentation of your boot loader (lilo or loadlin) about how to
257 pass options to the kernel at boot time) for devices if you want the
258 native EIDE sub-drivers to skip over the native support, so that
259 this SCSI emulation can be used instead. This is required for use of
260 CD-RW's.
262 Note that this option does NOT allow you to attach SCSI devices to a
263 box that doesn't have a SCSI host adapter installed.
265 If both this SCSI emulation and native ATAPI support are compiled
266 into the kernel, the native support will be used.
268 config IDE_TASK_IOCTL
269 bool "IDE Taskfile Access"
270 depends on BLK_DEV_IDE
271 help
272 This is a direct raw access to the media. It is a complex but
273 elegant solution to test and validate the domain of the hardware and
274 perform below the driver data recover if needed. This is the most
275 basic form of media-forensics.
277 If you are unsure, say N here.
279 config IDE_TASKFILE_IO
280 bool 'IDE Taskfile IO'
281 depends on BLK_DEV_IDE
282 default y
283 ---help---
284 Use new taskfile IO code.
286 It is safe to say Y to this question, in most cases.
288 comment "IDE chipset support/bugfixes"
289 depends on BLK_DEV_IDE
291 config BLK_DEV_CMD640
292 bool "CMD640 chipset bugfix/support"
293 depends on BLK_DEV_IDE && X86
294 ---help---
295 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
296 Pentium motherboards, usually in combination with a "Neptune" or
297 "SiS" chipset. Unfortunately, it has a number of rather nasty
298 design flaws that can cause severe data corruption under many common
299 conditions. Say Y here to include code which tries to automatically
300 detect and correct the problems under Linux. This option also
301 enables access to the secondary IDE ports in some CMD640 based
302 systems.
304 This driver will work automatically in PCI based systems (most new
305 systems have PCI slots). But if your system uses VESA local bus
306 (VLB) instead of PCI, you must also supply a kernel boot parameter
307 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
308 bootparam" or see the documentation of your boot loader about how to
309 pass options to the kernel.)
311 The CMD640 chip is also used on add-in cards by Acculogic, and on
312 the "CSA-6400E PCI to IDE controller" that some people have. For
313 details, read <file:Documentation/ide.txt>.
315 config BLK_DEV_CMD640_ENHANCED
316 bool "CMD640 enhanced support"
317 depends on BLK_DEV_CMD640
318 help
319 This option includes support for setting/autotuning PIO modes and
320 prefetch on CMD640 IDE interfaces. For details, read
321 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
322 and your BIOS does not already do this for you, then say Y here.
323 Otherwise say N.
325 config BLK_DEV_IDEPNP
326 bool "PNP EIDE support"
327 depends on BLK_DEV_IDE && PNP
328 help
329 If you have a PnP (Plug and Play) compatible EIDE card and
330 would like the kernel to automatically detect and activate
331 it, say Y here.
333 config BLK_DEV_IDEPCI
334 bool "PCI IDE chipset support" if PCI
335 depends on BLK_DEV_IDE
336 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC
337 help
338 Say Y here for PCI systems which use IDE drive(s).
339 This option helps the IDE driver to automatically detect and
340 configure all PCI-based IDE interfaces in your system.
342 config BLK_DEV_GENERIC
343 bool "Generic PCI IDE Chipset Support"
344 depends on PCI && BLK_DEV_IDEPCI
346 config IDEPCI_SHARE_IRQ
347 bool "Sharing PCI IDE interrupts support"
348 depends on PCI && BLK_DEV_IDEPCI
349 help
350 Some ATA/IDE chipsets have hardware support which allows for
351 sharing a single IRQ with other cards. To enable support for
352 this in the ATA/IDE driver, say Y here.
354 It is safe to say Y to this question, in most cases.
355 If unsure, say N.
357 config BLK_DEV_IDEDMA_PCI
358 bool "Generic PCI bus-master DMA support"
359 depends on PCI && BLK_DEV_IDEPCI
360 ---help---
361 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
362 is capable of bus-master DMA operation (most Pentium PCI systems),
363 you will want to say Y here to reduce CPU overhead. You can then use
364 the "hdparm" utility to enable DMA for drives for which it was not
365 enabled automatically. By default, DMA is not enabled automatically
366 for these drives, but you can change that by saying Y to the
367 following question "Use DMA by default when available". You can get
368 the latest version of the hdparm utility from
369 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
371 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
372 and the file <file:Documentation/ide.txt> for more information.
374 It is safe to say Y to this question.
376 config BLK_DEV_IDE_TCQ
377 bool "ATA tagged command queueing (EXPERIMENTAL)"
378 depends on BLK_DEV_IDEDMA_PCI && EXPERIMENTAL
379 help
380 Support for tagged command queueing on ATA disk drives. This enables
381 the IDE layer to have multiple in-flight requests on hardware that
382 supports it. For now this includes the IBM Deskstar series drives,
383 such as the 22GXP, 75GXP, 40GV, 60GXP, and 120GXP (ie any Deskstar made
384 in the last couple of years), and at least some of the Western
385 Digital drives in the Expert series (by nature of really being IBM
386 drives).
388 If you have such a drive, say Y here.
390 config BLK_DEV_IDE_TCQ_DEFAULT
391 bool "TCQ on by default"
392 depends on BLK_DEV_IDE_TCQ
393 ---help---
394 Enable tagged command queueing unconditionally on drives that report
395 support for it. Regardless of the chosen value here, tagging can be
396 controlled at run time:
398 echo "using_tcq:32" > /proc/ide/hdX/settings
400 where any value between 1-32 selects chosen queue depth and enables
401 TCQ, and 0 disables it. hdparm version 4.7 an above also support
402 TCQ manipulations.
404 Generally say Y here.
406 config BLK_DEV_IDE_TCQ_DEPTH
407 int "Default queue depth"
408 depends on BLK_DEV_IDE_TCQ
409 default "8"
410 help
411 Maximum size of commands to enable per-drive. Any value between 1
412 and 32 is valid, with 32 being the maxium that the hardware supports.
414 You probably just want the default of 32 here. If you enter an invalid
415 number, the default value will be used.
417 config BLK_DEV_OFFBOARD
418 bool "Boot off-board chipsets first support"
419 depends on PCI && BLK_DEV_IDEPCI
420 ---help---
421 Normally, IDE controllers built into the motherboard (on-board
422 controllers) are assigned to ide0 and ide1 while those on add-in PCI
423 cards (off-board controllers) are relegated to ide2 and ide3.
424 Answering Y here will allow you to reverse the situation, with
425 off-board controllers on ide0/1 and on-board controllers on ide2/3.
426 This can improve the usability of some boot managers such as lilo
427 when booting from a drive on an off-board controller.
429 If you say Y here, and you actually want to reverse the device scan
430 order as explained above, you also need to issue the kernel command
431 line option "ide=reverse". (Try "man bootparam" or see the
432 documentation of your boot loader (lilo or loadlin) about how to
433 pass options to the kernel at boot time.)
435 Note that, if you do this, the order of the hd* devices will be
436 rearranged which may require modification of fstab and other files.
438 If in doubt, say N.
440 config BLK_DEV_IDEDMA_FORCED
441 bool "Force enable legacy 2.0.X HOSTS to use DMA"
442 depends on BLK_DEV_IDEDMA_PCI
443 help
444 This is an old piece of lost code from Linux 2.0 Kernels.
446 Generally say N here.
448 config IDEDMA_PCI_AUTO
449 bool "Use PCI DMA by default when available"
450 depends on BLK_DEV_IDEDMA_PCI
451 ---help---
452 Prior to kernel version 2.1.112, Linux used to automatically use
453 DMA for IDE drives and chipsets which support it. Due to concerns
454 about a couple of cases where buggy hardware may have caused damage,
455 the default is now to NOT use DMA automatically. To revert to the
456 previous behaviour, say Y to this question.
458 If you suspect your hardware is at all flakey, say N here.
459 Do NOT email the IDE kernel people regarding this issue!
461 It is normally safe to answer Y to this question unless your
462 motherboard uses a VIA VP2 chipset, in which case you should say N.
464 config IDEDMA_ONLYDISK
465 bool "Enable DMA only for disks "
466 depends on IDEDMA_PCI_AUTO
467 help
468 This is used if you know your ATAPI Devices are going to fail DMA
469 Transfers.
471 Generally say N here.
473 config BLK_DEV_IDEDMA
474 bool
475 depends on BLK_DEV_IDE
476 default BLK_DEV_IDEDMA_ICS if ARCH_ACORN
477 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDE_PMAC
478 default BLK_DEV_IDEDMA_PCI if PCI && BLK_DEV_IDEPCI
480 config IDEDMA_PCI_WIP
481 bool "ATA Work(s) In Progress (EXPERIMENTAL)"
482 depends on BLK_DEV_IDEDMA_PCI && EXPERIMENTAL
483 help
484 If you enable this you will be able to use and test highly
485 developmental projects. If you say N, the configurator will
486 simply skip those options.
488 It is SAFEST to say N to this question.
490 config IDEDMA_NEW_DRIVE_LISTINGS
491 bool "Good-Bad DMA Model-Firmware (WIP)"
492 depends on IDEDMA_PCI_WIP
493 help
494 If you say Y here, the model and firmware revision of your drive
495 will be compared against a blacklist of buggy drives that claim to
496 be (U)DMA capable but aren't. This is a blanket on/off test with no
497 speed limit options.
499 If in doubt, say N.
501 config BLK_DEV_ADMA
502 bool
503 depends on PCI && BLK_DEV_IDEPCI
504 default BLK_DEV_IDEDMA_PCI
506 config BLK_DEV_AEC62XX
507 tristate "AEC62XX chipset support"
508 depends on BLK_DEV_IDEDMA_PCI
509 help
510 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
511 IDE controllers. This allows the kernel to change PIO, DMA and UDMA
512 speeds and to configure the chip to optimum performance.
514 config BLK_DEV_ALI15X3
515 tristate "ALI M15x3 chipset support"
516 depends on BLK_DEV_IDEDMA_PCI
517 help
518 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
519 onboard chipsets. It also tests for Simplex mode and enables
520 normal dual channel support.
522 If you say Y here, you also need to say Y to "Use DMA by default
523 when available", above. Please read the comments at the top of
524 <file:drivers/ide/alim15x3.c>.
526 If unsure, say N.
528 config WDC_ALI15X3
529 bool "ALI M15x3 WDC support (DANGEROUS)"
530 depends on BLK_DEV_ALI15X3
531 ---help---
532 This allows for UltraDMA support for WDC drives that ignore CRC
533 checking. You are a fool for enabling this option, but there have
534 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
535 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
536 SERIOUS WARNING.
538 Using this option can allow WDC drives to run at ATA-4/5 transfer
539 rates with only an ATA-2 support structure.
541 SAY N!
543 config BLK_DEV_AMD74XX
544 tristate "AMD and nVidia IDE support"
545 depends on BLK_DEV_IDEDMA_PCI
546 help
547 This driver adds explicit support for AMD-7xx and AMD-8111 chips
548 and also for the nVidia nForce chip. This allows the kernel to
549 change PIO, DMA and UDMA speeds and to configure the chip to
550 optimum performance.
552 config BLK_DEV_CMD64X
553 tristate "CMD64{3|6|8|9} chipset support"
554 depends on BLK_DEV_IDEDMA_PCI
555 help
556 Say Y here if you have an IDE controller which uses any of these
557 chipsets: CMD643, CMD646, or CMD648.
559 config BLK_DEV_TRIFLEX
560 tristate "Compaq Triflex IDE support"
561 depends on BLK_DEV_IDEDMA_PCI
562 help
563 Say Y here if you have a Compaq Triflex IDE controller, such
564 as those commonly found on Compaq Pentium-Pro systems
566 config BLK_DEV_CY82C693
567 tristate "CY82C693 chipset support"
568 depends on BLK_DEV_IDEDMA_PCI
569 help
570 This driver adds detection and support for the CY82C693 chipset
571 used on Digital's PC-Alpha 164SX boards.
573 If you say Y here, you need to say Y to "Use DMA by default
574 when available" as well.
576 config BLK_DEV_CS5520
577 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"
578 depends on BLK_DEV_IDEDMA_PCI && EXPERIMENTAL
579 help
580 Include support for PIO tuning an virtual DMA on the Cyrix MediaGX
581 5510/5520 chipset. This will automatically be detected and
582 configured if found.
584 It is safe to say Y to this question.
586 config BLK_DEV_CS5530
587 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"
588 depends on BLK_DEV_IDEDMA_PCIOA
589 help
590 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
591 will automatically be detected and configured if found.
593 It is safe to say Y to this question.
595 config BLK_DEV_HPT34X
596 tristate "HPT34X chipset support"
597 depends on BLK_DEV_IDEDMA_PCI
598 help
599 This driver adds up to 4 more EIDE devices sharing a single
600 interrupt. The HPT343 chipset in its current form is a non-bootable
601 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
602 PCI UDMA controllers. This driver requires dynamic tuning of the
603 chipset during the ide-probe at boot time. It is reported to support
604 DVD II drives, by the manufacturer.
606 config HPT34X_AUTODMA
607 bool "HPT34X AUTODMA support (WIP)"
608 depends on BLK_DEV_HPT34X && IDEDMA_PCI_WIP
609 help
610 This is a dangerous thing to attempt currently! Please read the
611 comments at the top of <file:drivers/ide/hpt34x.c>. If you say Y
612 here, then say Y to "Use DMA by default when available" as well.
614 If unsure, say N.
616 config BLK_DEV_HPT366
617 tristate "HPT36X/37X chipset support"
618 depends on BLK_DEV_IDEDMA_PCI
619 ---help---
620 HPT366 is an Ultra DMA chipset for ATA-66.
621 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
622 HPT370 is an Ultra DMA chipset for ATA-100.
623 HPT372 is an Ultra DMA chipset for ATA-100.
624 HPT374 is an Ultra DMA chipset for ATA-100.
626 This driver adds up to 4 more EIDE devices sharing a single
627 interrupt.
629 The HPT366 chipset in its current form is bootable. One solution
630 for this problem are special LILO commands for redirecting the
631 reference to device 0x80. The other solution is to say Y to "Boot
632 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
633 your mother board has the chipset natively mounted. Regardless one
634 should use the fore mentioned option and call at LILO or include
635 "ide=reverse" in LILO's append-line.
637 This driver requires dynamic tuning of the chipset during the
638 ide-probe at boot. It is reported to support DVD II drives, by the
639 manufacturer.
641 config BLK_DEV_SC1200
642 tristate "National SCx200 chipset support"
643 depends on BLK_DEV_IDEDMA_PCI
644 help
645 This driver adds support for the built in IDE on the National
646 SCx200 series of embedded x86 "Geode" systems
648 config BLK_DEV_PIIX
649 tristate "Intel PIIXn chipsets support"
650 depends on BLK_DEV_IDEDMA_PCI
651 help
652 This driver adds explicit support for Intel PIIX and ICH chips
653 and also for the Efar Victory66 (slc90e66) chip. This allows
654 the kernel to change PIO, DMA and UDMA speeds and to configure
655 the chip to optimum performance.
657 config BLK_DEV_IT8172
658 bool "IT8172 IDE support"
659 depends on (MIPS_ITE8172 || MIPS_IVR) && BLK_DEV_IDEDMA_PCI
660 help
661 Say Y here to support the on-board IDE controller on the Integrated
662 Technology Express, Inc. ITE8172 SBC. Vendor page at
663 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
664 board at <http://www.mvista.com/allies/semiconductor/ite.html>.
666 config BLK_DEV_NS87415
667 tristate "NS87415 chipset support"
668 depends on BLK_DEV_IDEDMA_PCI
669 help
670 This driver adds detection and support for the NS87415 chip
671 (used in SPARC64, among others).
673 Please read the comments at the top of <file:drivers/ide/ns87415.c>.
675 config BLK_DEV_OPTI621
676 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"
677 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL
678 help
679 This is a driver for the OPTi 82C621 EIDE controller.
680 Please read the comments at the top of <file:drivers/ide/opti621.c>.
682 config BLK_DEV_PDC202XX_OLD
683 tristate "PROMISE PDC202{46|62|65|67} support"
684 depends on BLK_DEV_IDEDMA_PCI
686 config PDC202XX_BURST
687 bool "Special UDMA Feature"
688 depends on BLK_DEV_PDC202XX_OLD=y && CONFI_BLK_DEV_IDEDMA_PCI
689 ---help---
690 This option causes the pdc202xx driver to enable UDMA modes on the
691 PDC202xx even when the PDC202xx BIOS has not done so.
693 It was originally designed for the PDC20246/Ultra33, whose BIOS will
694 only setup UDMA on the first two PDC20246 cards. It has also been
695 used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
696 when the PDC20265 BIOS has been disabled (for faster boot up).
698 Please read the comments at the top of
699 <file:drivers/ide/pdc202xx.c>.
701 If unsure, say N.
703 config BLK_DEV_PDC202XX_NEW
704 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
705 depends on BLK_DEV_IDEDMA_PCI
707 # FIXME - probably wants to be one for old and for new
708 config PDC202XX_FORCE
709 bool "Special FastTrak Feature"
710 depends on BLK_DEV_PDC202XX_NEW=y
711 help
712 For FastTrak enable overriding BIOS.
714 config BLK_DEV_RZ1000
715 tristate "RZ1000 chipset bugfix/support"
716 depends on PCI && BLK_DEV_IDEPCI && X86
717 help
718 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
719 Pentium motherboards, usually along with the "Neptune" chipset.
720 Unfortunately, it has a rather nasty design flaw that can cause
721 severe data corruption under many conditions. Say Y here to include
722 code which automatically detects and corrects the problem under
723 Linux. This may slow disk throughput by a few percent, but at least
724 things will operate 100% reliably.
726 config BLK_DEV_SVWKS
727 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support"
728 depends on BLK_DEV_IDEDMA_PCI
729 help
730 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
731 chipsets.
733 config BLK_DEV_SIIMAGE
734 tristate "Silicon Image chipset support"
735 depends on BLK_DEV_IDEDMA_PCI
736 help
737 This driver adds PIO/(U)DMA support for the SI CMD680 and SII
738 3112 (Serial ATA) chips.
740 config BLK_DEV_SIS5513
741 tristate "SiS5513 chipset support"
742 depends on BLK_DEV_IDEDMA_PCI && X86
743 ---help---
744 This driver ensures (U)DMA support for SIS5513 chipset family based
745 mainboards.
747 The following chipsets are supported:
748 ATA16: SiS5511, SiS5513
749 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
750 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
751 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
752 SiS745, SiS750
754 If you say Y here, you need to say Y to "Use DMA by default when
755 available" as well.
757 Please read the comments at the top of <file:drivers/ide/sis5513.c>.
759 config BLK_DEV_SLC90E66
760 tristate "SLC90E66 chipset support"
761 depends on BLK_DEV_IDEDMA_PCI
762 help
763 This driver ensures (U)DMA support for Victroy66 SouthBridges for
764 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
765 The nice thing about it is that you can mix Ultra/DMA/PIO devices
766 and it will handle timing cycles. Since this is an improved
767 look-a-like to the PIIX4 it should be a nice addition.
769 If you say Y here, you need to say Y to "Use DMA by default when
770 available" as well.
772 Please read the comments at the top of
773 drivers/ide/slc90e66.c.
775 config BLK_DEV_TRM290
776 tristate "Tekram TRM290 chipset support"
777 depends on BLK_DEV_IDEDMA_PCI
778 help
779 This driver adds support for bus master DMA transfers
780 using the Tekram TRM290 PCI IDE chip. Volunteers are
781 needed for further tweaking and development.
782 Please read the comments at the top of <file:drivers/ide/trm290.c>.
784 config BLK_DEV_VIA82CXXX
785 tristate "VIA82CXXX chipset support"
786 depends on BLK_DEV_IDEDMA_PCI
787 help
788 This driver adds explicit support for VIA BusMastering IDE chips.
789 This allows the kernel to change PIO, DMA and UDMA speeds and to
790 configure the chip to optimum performance.
792 config BLK_DEV_SL82C105
793 tristate "Winbond SL82c105 support"
794 depends on PCI && (PPC || ARM) && BLK_DEV_IDEPCI
795 help
796 If you have a Winbond SL82c105 IDE controller, say Y here to enable
797 special configuration for this chip. This is common on various CHRP
798 motherboards, but could be used elsewhere. If in doubt, say Y.
800 config BLK_DEV_IDE_PMAC
801 bool "Builtin PowerMac IDE support"
802 depends on BLK_DEV_IDE && PPC_PMAC
803 help
804 This driver provides support for the built-in IDE controller on
805 most of the recent Apple Power Macintoshes and PowerBooks.
806 If unsure, say Y.
808 config BLK_DEV_IDEDMA_PMAC
809 bool "PowerMac IDE DMA support"
810 depends on BLK_DEV_IDE_PMAC
811 help
812 This option allows the driver for the built-in IDE controller on
813 Power Macintoshes and PowerBooks to use DMA (direct memory access)
814 to transfer data to and from memory. Saying Y is safe and improves
815 performance.
817 config BLK_DEV_IDEDMA_PMAC_AUTO
818 bool "Use DMA by default"
819 depends on BLK_DEV_IDEDMA_PMAC
820 help
821 This option allows the driver for the built-in IDE controller on
822 Power Macintoshes and PowerBooks to use DMA automatically, without
823 it having to be explicitly enabled. This option is provided because
824 of concerns about a couple of cases where using DMA on buggy PC
825 hardware may have caused damage. Saying Y should be safe on all
826 Apple machines.
828 config BLK_DEV_IDE_SWARM
829 bool "SWARM onboard IDE support"
830 depends on BLK_DEV_IDE && SIBYTE_SWARM
832 config BLK_DEV_IDE_ICSIDE
833 tristate "ICS IDE interface support"
834 depends on BLK_DEV_IDE!=n && ARM && ARCH_ACORN
835 help
836 On Acorn systems, say Y here if you wish to use the ICS IDE
837 interface card. This is not required for ICS partition support.
838 If you are unsure, say N to this.
840 config BLK_DEV_IDEDMA_ICS
841 bool "ICS DMA support"
842 depends on BLK_DEV_IDE_ICSIDE
843 help
844 Say Y here if you want to add DMA (Direct Memory Access) support to
845 the ICS IDE driver.
847 config IDEDMA_ICS_AUTO
848 bool "Use ICS DMA by default"
849 depends on BLK_DEV_IDEDMA_ICS
850 help
851 Prior to kernel version 2.1.112, Linux used to automatically use
852 DMA for IDE drives and chipsets which support it. Due to concerns
853 about a couple of cases where buggy hardware may have caused damage,
854 the default is now to NOT use DMA automatically. To revert to the
855 previous behaviour, say Y to this question.
857 If you suspect your hardware is at all flakey, say N here.
858 Do NOT email the IDE kernel people regarding this issue!
860 config BLK_DEV_IDE_RAPIDE
861 tristate "RapIDE interface support"
862 depends on BLK_DEV_IDE!=n && ARM && ARCH_ACORN
863 help
864 Say Y here if you want to support the Yellowstone RapIDE controller
865 manufactured for use with Acorn computers.
867 config BLK_DEV_GAYLE
868 bool "Amiga Gayle IDE interface support"
869 depends on BLK_DEV_IDE && AMIGA
870 help
871 This is the IDE driver for the builtin IDE interface on some Amiga
872 models. It supports both the `A1200 style' (used in A600 and A1200)
873 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
874 interface. Say Y if you have such an Amiga model and want to use IDE
875 devices (hard disks, CD-ROM drives, etc.) that are connected to the
876 builtin IDE interface.
878 config BLK_DEV_IDEDOUBLER
879 bool "Amiga IDE Doubler support (EXPERIMENTAL)"
880 depends on BLK_DEV_GAYLE && EXPERIMENTAL
881 ---help---
882 This driver provides support for the so-called `IDE doublers' (made
883 by various manufacturers, e.g. Eyetech) that can be connected to the
884 builtin IDE interface of some Amiga models. Using such an IDE
885 doubler, you can connect up to four instead of two IDE devices on
886 the Amiga's builtin IDE interface.
888 Note that the normal Amiga Gayle IDE driver may not work correctly
889 if you have an IDE doubler and don't enable this driver!
891 Say Y if you have an IDE doubler. The driver is enabled at kernel
892 runtime using the "ide=doubler" kernel boot parameter.
894 config BLK_DEV_BUDDHA
895 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)"
896 depends on BLK_DEV_IDE && ZORRO && EXPERIMENTAL
897 help
898 This is the IDE driver for the IDE interfaces on the Buddha,
899 Catweasel and X-Surf expansion boards. It supports up to two interfaces
900 on the Buddha, three on the Catweasel and two on the X-Surf.
902 Say Y if you have a Buddha or Catweasel expansion board and want to
903 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
904 to one of its IDE interfaces.
906 config BLK_DEV_FALCON_IDE
907 bool "Falcon IDE interface support"
908 depends on BLK_DEV_IDE && ATARI
909 help
910 This is the IDE driver for the builtin IDE interface on the Atari
911 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
912 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
913 interface.
915 config BLK_DEV_MAC_IDE
916 bool "Macintosh Quadra/Powerbook IDE interface support"
917 depends on BLK_DEV_IDE && MAC
918 help
919 This is the IDE driver for the builtin IDE interface on some m68k
920 Macintosh models. It supports both the `Quadra style' (used in
921 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
922 (used in the Powerbook 150 and 190 models) IDE interface.
924 Say Y if you have such an Macintosh model and want to use IDE
925 devices (hard disks, CD-ROM drives, etc.) that are connected to the
926 builtin IDE interface.
928 config BLK_DEV_Q40IDE
929 bool "Q40/Q60 IDE interface support"
930 depends on BLK_DEV_IDE && Q40
931 help
932 Enable the on-board IDE controller in the Q40/Q60. This should
933 normally be on; disable it only if you are running a custom hard
934 drive subsystem through an expansion card.
936 config BLK_DEV_MPC8xx_IDE
937 bool "MPC8xx IDE support"
938 depends on BLK_DEV_IDE && 8xx
939 help
940 This option provides support for IDE on Motorola MPC8xx Systems.
941 Please see 'Type of MPC8xx IDE interface' for details.
943 If unsure, say N.
945 choice
946 prompt "Type of MPC8xx IDE interface"
947 depends on BLK_DEV_MPC8xx_IDE
948 default IDE_8xx_PCCARD
950 config IDE_8xx_PCCARD
951 bool "8xx_PCCARD"
952 ---help---
953 Select how the IDE devices are connected to the MPC8xx system:
955 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
956 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
957 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
958 systems)
960 8xx_DIRECT is used for directly connected IDE devices using the 8xx
961 internal PCMCIA interface (example: IVMS8 systems)
963 EXT_DIRECT is used for IDE devices directly connected to the 8xx
964 bus using some glue logic, but _not_ the 8xx internal
965 PCMCIA interface (example: IDIF860 systems)
967 config IDE_8xx_DIRECT
968 bool "8xx_DIRECT"
970 config IDE_EXT_DIRECT
971 bool "EXT_DIRECT"
973 endchoice
975 # no isa -> no vlb
976 config IDE_CHIPSETS
977 bool "Other IDE chipset support"
978 depends on BLK_DEV_IDE && ISA
979 ---help---
980 Say Y here if you want to include enhanced support for various IDE
981 interface chipsets used on motherboards and add-on cards. You can
982 then pick your particular IDE chip from among the following options.
983 This enhanced support may be necessary for Linux to be able to
984 access the 3rd/4th drives in some systems. It may also enable
985 setting of higher speed I/O rates to improve system performance with
986 these chipsets. Most of these also require special kernel boot
987 parameters to actually turn on the support at runtime; you can find
988 a list of these in the file <file:Documentation/ide.txt>.
990 People with SCSI-only systems can say N here.
992 comment "Note: most of these also require special kernel boot parameters"
993 depends on BLK_DEV_IDE && IDE_CHIPSETS
995 config BLK_DEV_4DRIVES
996 bool "Generic 4 drives/port support"
997 depends on IDE_CHIPSETS
998 help
999 Certain older chipsets, including the Tekram 690CD, use a single set
1000 of I/O ports at 0x1f0 to control up to four drives, instead of the
1001 customary two drives per port. Support for this can be enabled at
1002 runtime using the "ide0=four" kernel boot parameter if you say Y
1003 here.
1005 config BLK_DEV_ALI14XX
1006 tristate "ALI M14xx support"
1007 depends on IDE_CHIPSETS && BLK_DEV_IDE
1008 help
1009 This driver is enabled at runtime using the "ide0=ali14xx" kernel
1010 boot parameter. It enables support for the secondary IDE interface
1011 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1012 I/O speeds to be set as well. See the files
1013 <file:Documentation/ide.txt> and <file:drivers/ide/ali14xx.c> for
1014 more info.
1016 config BLK_DEV_DTC2278
1017 tristate "DTC-2278 support"
1018 depends on IDE_CHIPSETS && BLK_DEV_IDE
1019 help
1020 This driver is enabled at runtime using the "ide0=dtc2278" kernel
1021 boot parameter. It enables support for the secondary IDE interface
1022 of the DTC-2278 card, and permits faster I/O speeds to be set as
1023 well. See the <file:Documentation/ide.txt> and
1024 <file:drivers/ide/dtc2278.c> files for more info.
1026 config BLK_DEV_HT6560B
1027 tristate "Holtek HT6560B support"
1028 depends on IDE_CHIPSETS && BLK_DEV_IDE
1029 help
1030 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1031 boot parameter. It enables support for the secondary IDE interface
1032 of the Holtek card, and permits faster I/O speeds to be set as well.
1033 See the <file:Documentation/ide.txt> and
1034 <file:drivers/ide/ht6560b.c> files for more info.
1036 config BLK_DEV_PDC4030
1037 tristate "PROMISE DC4030 support (EXPERIMENTAL)"
1038 depends on IDE_CHIPSETS && BLK_DEV_IDEDISK && EXPERIMENTAL
1039 help
1040 This driver provides support for the secondary IDE interface and
1041 cache of the original Promise IDE chipsets, e.g. DC4030 and DC5030.
1042 It is nothing to do with the later range of Promise UDMA chipsets -
1043 see the PDC_202XX support for these. CD-ROM and TAPE devices are not
1044 supported (and probably never will be since I don't think the cards
1045 support them). This driver is enabled at runtime using the "ide0=dc4030"
1046 or "ide1=dc4030" kernel boot parameter. See the
1047 <file:drivers/ide/pdc4030.c> file for more info.
1049 config BLK_DEV_QD65XX
1050 tristate "QDI QD65xx support"
1051 depends on IDE_CHIPSETS && BLK_DEV_IDE
1052 help
1053 This driver is enabled at runtime using the "ide0=qd65xx" kernel
1054 boot parameter. It permits faster I/O speeds to be set. See the
1055 <file:Documentation/ide.txt> and <file:drivers/ide/qd65xx.c> for
1056 more info.
1058 config BLK_DEV_UMC8672
1059 tristate "UMC-8672 support"
1060 depends on IDE_CHIPSETS && BLK_DEV_IDE
1061 help
1062 This driver is enabled at runtime using the "ide0=umc8672" kernel
1063 boot parameter. It enables support for the secondary IDE interface
1064 of the UMC-8672, and permits faster I/O speeds to be set as well.
1065 See the files <file:Documentation/ide.txt> and
1066 <file:drivers/ide/umc8672.c> for more info.
1068 config BLK_DEV_HD_ONLY
1069 bool "Old hard disk (MFM/RLL/IDE) driver"
1070 depends on BLK_DEV_IDE=n
1071 ---help---
1072 There are two drivers for MFM/RLL/IDE hard disks. Most people use
1073 the newer enhanced driver, but this old one is still around for two
1074 reasons. Some older systems have strange timing problems and seem to
1075 work only with the old driver (which itself does not work with some
1076 newer systems). The other reason is that the old driver is smaller,
1077 since it lacks the enhanced functionality of the new one. This makes
1078 it a good choice for systems with very tight memory restrictions, or
1079 for systems with only older MFM/RLL/ESDI drives. Choosing the old
1080 driver can save 13 KB or so of kernel memory.
1082 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
1083 instead of this one. For more detailed information, read the
1084 Disk-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>.
1087 config IDEDMA_AUTO
1088 bool
1089 depends on IDEDMA_PCI_AUTO || BLK_DEV_IDEDMA_PMAC_AUTO || IDEDMA_ICS_AUTO
1090 default y
1092 config IDEDMA_IVB
1093 bool "IGNORE word93 Validation BITS"
1094 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS
1095 ---help---
1096 There are unclear terms in ATA-4 and ATA-5 standards how certain
1097 hardware (an 80c ribbon) should be detected. Different interpretations
1098 of the standards have been released in hardware. This causes problems:
1099 for example, a host with Ultra Mode 4 (or higher) will not run
1100 in that mode with an 80c ribbon.
1102 If you are experiencing compatibility or performance problems, you
1103 MAY try to answering Y here. However, it does not necessarily solve
1104 any of your problems, it could even cause more of them.
1106 It is normally safe to answer Y; however, the default is N.
1108 config DMA_NONPCI
1109 bool
1110 depends on BLK_DEV_TIVO
1111 default y
1113 config BLK_DEV_PDC202XX
1114 bool
1115 depends on BLK_DEV_IDEDMA_PCI && (BLK_DEV_PDC202XX_OLD || BLK_DEV_PDC202XX_NEW)
1116 default y
1117 ---help---
1118 Promise Ultra33 or PDC20246
1119 Promise Ultra66 or PDC20262
1120 Promise Ultra100 or PDC20265/PDC20267/PDC20268
1122 This driver adds up to 4 more EIDE devices sharing a single
1123 interrupt. This add-on card is a bootable PCI UDMA controller. Since
1124 multiple cards can be installed and there are BIOS ROM problems that
1125 happen if the BIOS revisions of all installed cards (three-max) do
1126 not match, the driver attempts to do dynamic tuning of the chipset
1127 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
1128 for more than one card. This card may require that you say Y to
1129 "Special UDMA Feature".
1131 If you say Y here, you need to say Y to "Use DMA by default when
1132 available" as well.
1134 Please read the comments at the top of
1135 <file:drivers/ide/pdc202xx.c>.
1137 If unsure, say N.
1139 config BLK_DEV_IDE_MODES
1140 bool
1141 depends on BLK_DEV_4DRIVES || BLK_DEV_ALI14XX || BLK_DEV_DTC2278 || BLK_DEV_HT6560B || BLK_DEV_PDC4030 || BLK_DEV_QD65XX || BLK_DEV_UMC8672 || BLK_DEV_AEC62XX=y || BLK_DEV_ALI15X3=y || BLK_DEV_AMD74XX=y || BLK_DEV_CMD640 || BLK_DEV_CMD64X=y || BLK_DEV_CS5530=y || BLK_DEV_CY82C693=y || BLK_DEV_HPT34X=y || BLK_DEV_HPT366=y || BLK_DEV_IDE_PMAC || BLK_DEV_IT8172 || BLK_DEV_MPC8xx_IDE || BLK_DEV_NFORCE=y || BLK_DEV_OPTI621=y || BLK_DEV_PDC202XX || BLK_DEV_PIIX=y || BLK_DEV_SVWKS=y || BLK_DEV_SIIMAGE=y || BLK_DEV_SIS5513=y || BLK_DEV_SL82C105=y || BLK_DEV_SLC90E66=y || BLK_DEV_VIA82CXXX=y
1142 default y
1144 endmenu
1146 endmenu