xref: /netbsd-src/share/man/man4/pciide.4 (revision 481fca6e59249d8ffcf24fef7cfbe7b131bfb080)
1.\"	$NetBSD: pciide.4,v 1.22 2000/07/07 09:53:28 bouyer Exp $
2.\"
3.\" Copyright (c) 1998 Manuel Bouyer.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\" 3. All advertising materials mentioning features or use of this software
14.\"    must display the following acknowledgement:
15.\"	This product includes software developed by the University of
16.\"	California, Berkeley and its contributors.
17.\" 4. Neither the name of the University nor the names of its contributors
18.\"    may be used to endorse or promote products derived from this software
19.\"    without specific prior written permission.
20.\"
21.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
22.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
23.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
24.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
25.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
26.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
27.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
28.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
29.\" INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
30.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
31.\"
32.Dd October 15, 1998
33.Dt PCIIDE 4
34.Os
35.Sh NAME
36.Nm PCIIDE
37.Nd PCI IDE disk controllers driver
38.Sh SYNOPSIS
39.Cd "pciide* at pci? dev ? function ? flags 0x0000"
40.Cd "pciide* at pnpbios? index ?"
41.Cd "options PCIIDE_CMD064x_DISABLE"
42.Cd "options PCIIDE_AMD756_ENABLEDMA"
43.Sh DESCRIPTION
44The
45.Nm pciide
46driver supports the PCI IDE controllers as specified in the
47"PCI IDE controller specification, revision 1.0" draft, and provides the core
48functions for the
49.Nm wd
50and
51.Nm atapi
52drivers. This driver include specific, enhanced support for the CMD Tech
53PCI0640 controller, and IDE DMA/Ultra-DMA support for the following
54controllers:
55.Bl -dash -compact -offset indent
56.It
57Acer labs M5229 IDE Controller
58.It
59Advanced Micro Devices AMD-756 IDE Controllers
60.It
61CMD Tech PCI0643, PCI0646, PCI0648 and PCI0649 IDE Controllers
62.It
63Contaq Microsystems/Cypress CY82C693 IDE Controller
64.It
65HighPoint HPT366 Ultra/66 IDE controller
66.It
67Intel PIIX, PIIX3 and PIIX4 IDE Controllers
68.It
69Intel 82801 (ICH/ICH0) IDE Controllers
70.It
71OPTi 82c621 (plus a few of its derivatives) IDE Controllers
72.It
73Promise PDC20246 (Ultra/33), PDC20262 (Ultra/66), and Ultra100 (in Ultra/66
74mode only) PCI IDE controllers
75.It
76Silicon Integrated System 5597/5598 IDE controller
77.It
78VIA Technologies VT82C586 and VT82C586A IDE Controllers
79.El
80Some of these controllers are only available in multifunction PCI chips.
81.Pp
82The 0x0001 flag forces the
83.Nm
84driver to use DMA when there is no explicit DMA mode setting support for
85the controller but DMA is present. If the BIOS didn't set up the controller
86properly, this can cause a machine hang.
87.Sh BUGS
88There's no way to reliably know if a PCI064x controller is enabled or not.
89If the driver finds a PCI064x, it will assume it is enabled unless the
90PCIIDE_CMD064x_DISABLE option is specified in the kernel config file.
91This will be a problem only if the controller has been disabled in the BIOS
92and another controller has been installed and uses the ISA legacy I/O ports
93and interrupts.
94.Pp
95The AMD756 chip revision D2 has a bug affecting DMA (but not Ultra-DMA)
96modes.  The workaround documented by AMD is to not use DMA on any drive which
97does not support Ultra-DMA modes.  This does not appear to be necessary on all
98drives, the PCIIDE_AMD756_ENABLEDMA option can be used to force multiword DMA
99on the buggy revisions.  Multiword DMA eventually be disabled on a per-drive
100basis with config flags, see
101.Xr wd 4 .
102The bug, if triggered, will cause a total system hang.
103.Pp
104The timings used for the PIO and DMA modes for controllers listed above
105are for a PCI bus running at 30 or 33 Mhz (except the OPTi controller,
106which supports both 25 and 33 Mhz PCI bus timings). This driver may not
107work properly on overclocked systems.
108.Sh SEE ALSO
109.Xr intro 4 ,
110.Xr pci 4 ,
111.Xr pnpbios 4 ,
112.Xr scsi 4 ,
113.Xr wd 4 ,
114.Xr wdc 4
115