1.\" $OpenBSD: pciide.4,v 1.19 2001/12/11 22:07:48 chris Exp $ 2.\" $NetBSD: pciide.4,v 1.8 1999/03/16 01:19:17 garbled Exp $ 3.\" 4.\" Copyright (c) 1998 Manuel Bouyer. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.Dd October 15, 1998 35.Dt PCIIDE 4 36.Os 37.Sh NAME 38.Nm pciide 39.Nd PCI IDE controller driver 40.Sh SYNOPSIS 41.Cd "pciide* at pci ? dev ? function ? flags 0x0000" 42.Cd "options PCIIDE_CMD064x_DISABLE" 43.Sh DESCRIPTION 44The 45.Nm 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.Xr wd 4 50and 51.Xr atapiscsi 4 52drivers. 53This driver includes specific, enhanced support for the CMD Tech 54PCI0640 controller and IDE DMA/UltraDMA support for the following PCI IDE 55controllers: 56.Pp 57.Bl -item -compact -offset indent 58.It 59Acard ATP850, ATP860 60.It 61Acer Labs M5229 62.It 63Advanced Micro Devices AMD-756, AMD-766 64.It 65CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, PCI0649 66.It 67Contaq Microsystems/Cypress CY82C693 68.It 69HighPoint HPT366, HPT370 70.It 71Intel PIIX, PIIX3, and PIIX4 72.It 73Intel 82801 (ICH/ICH0/ICH2) 74.It 75National Semiconductor PC87415 76.It 77OPTi 82c621 78.It 79Promise PDC20246, PDC20262, PDC20265, PDC20267, PDC20268 80.It 81Silicon Integrated System 5513 (5597/5598) 82.It 83VIA Technologies VT82C586/A/B, VT82C596A/B, VT82C686A/B 84.El 85.Pp 86Some of these controllers are only available in multifunction PCI chips. 87.Pp 88The 89.Li 0x0001 90flag forces the 91.Nm 92driver to use DMA when there is no explicit DMA mode setting support for 93the controller but DMA is present. 94If the BIOS didn't configure the controller properly, this can 95cause a machine hang. 96.Sh SEE ALSO 97.Xr atapiscsi 4 , 98.Xr intro 4 , 99.Xr scsi 4 , 100.Xr wd 4 , 101.Xr wdc 4 102.Sh BUGS 103There's no way to know reliably if a PCI064x controller is enabled or not. 104If the driver finds a PCI064x, it will assume it is enabled unless 105.Dv PCIIDE_CMD064x_DISABLE 106is specified in the kernel config file. 107This will be a problem only if the controller has been disabled in the BIOS 108and another controller has been installed which uses the ISA legacy I/O ports 109and interrupts. 110.Pp 111The OPTi controller code is disabled by default because the driver 112does not yet work around all bugs in current chipsets. 113.Pp 114For proper operation of UltraDMA 3 115.Pq 44 MB/sec , 1164 117.Pq 66 MB/sec , 118or 5 119.Pq 100 MB/sec , 120a 40-pin, 80-conductor cable must be used. 121On some controllers, the pciide driver can probe the chip and see if it 122detects that an 80-conductor or 40-conductor cable was used. 123If not, it will down-grade to UltraDMA 2 mode. 124On other controllers, no such capability exists, and the driver assumes 125you are using an 80-conductor cable. 126If you are getting errors about 127corrupted data, check to make sure you are using the correct cable. 128An 80-conductor cable is recommended for any IDE installation, not just 129ones using faster UltraDMA modes, because it will decrease electrical 130noise and increase data reliability. 131.Pp 132The AMD756 chip revision D2 has a bug affecting DMA (but not Ultra-DMA) 133modes. 134The workaround documented by AMD is to not use DMA on any drive which 135does not support Ultra-DMA modes. 136This does not appear to be necessary on all drives, the 137PCIIDE_AMD756_ENABLEDMA option can be used to force multiword DMA 138on the buggy revisions. 139Multiword DMA can eventually be disabled on a per-drive basis with config 140flags, see 141.Xr wd 4 . 142The bug, if triggered, will cause a total system hang. 143.Pp 144The timings used for the PIO and DMA modes for controllers listed above 145are for a PCI bus running at 30 or 33 MHz. 146These timings will work on a slower bus, 147but they may cause errors on an over-clocked bus. 148