pciide man page on OpenBSD

Man page or keyword search:  
man Server   11362 pages
apropos Keyword Search (all sections)
Output format
OpenBSD logo
[printable version]

PCIIDE(4)		  OpenBSD Programmer's Manual		     PCIIDE(4)

NAME
     pciide - PCI IDE controller driver

SYNOPSIS
     pciide* at pci? flags 0x0000
     pciide* at jmb? flags 0x0000

     option PCIIDE_AMD756_ENABLEDMA
     option PCIIDE_CMD064x_DISABLE
     option PCIIDE_CMD0646U_ENABLEUDMA

     atapiscsi* at pciide? flags 0x0000
     wd* at pciide? flags 0x0000

DESCRIPTION
     The pciide driver supports the PCI IDE controllers as specified in the
     "PCI IDE controller specification, revision 1.0" draft, as well as the
     Serial ATA controllers working either in parallel ATA compatibility mode
     or in native serial mode.	It provides the core functions for the wd(4)
     and atapiscsi(4) drivers.	This driver includes specific, enhanced
     support for the CMD Tech PCI0640 controller and IDE DMA/UltraDMA support
     for the following PCI IDE controllers:

	   o   Acard ATP850U, ATP860, ATP860-A, ATP865-A, ATP865-R
	   o   Acer Labs M5229
	   o   Adaptec AAR-1210SA
	   o   AMD 756, 766, 768, 8111, Hudson 2
	   o   ATI SB200, SB300, SB400, SB600, SB700 (IDE only)
	   o   CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, PCI0649, PCI0680
	   o   Contaq Microsystems/Cypress CY82C693
	   o   HighPoint HPT366, HPT370, HPT372, HPT302, HPT371, HPT374
	   o   Intel 6300ESB/6321ESB
	   o   Intel 82801 (ICH/ICH0/ICH2/ICH3/ICH4/ICH4-M/ICH5/ICH5R/
	       ICH6/ICH6M/ICH6R/ICH7/ICH7M/ICH7R/ICH7M DH/ICH8/ICH8M/
	       ICH9/ICH9M)
	   o   Intel PIIX, PIIX3, and PIIX4
	   o   ITE IT8211F, IT8212F
	   o   JMicron JMB361/3/5/6/8
	   o   National Semiconductor PC87415
	   o   National Semiconductor SCx200 (found on SC1100 SoC)
	   o   NVIDIA nForce/nForce2/nForce2-400/nForce3/nForce3-250/nForce4,
	       MCP04/MCP51/MCP55/MCP61/MCP65/MCP67/MCP73/MCP77
	   o   Phison PS5000
	   o   Promise PDC20246, PDC20262, PDC20265, PDC20267, PDC20268,
	       PDC20268R, PDC20269, PDC20271, PDC20275, PDC20276, PDC20277,
	       PDC20318, PDC20319, PDC20371, PDC20375, PDC20376, PDC20377,
	       PDC20378, PDC20379, PDC20571, PDC20575, PDC20579, PDC20771,
	       PDC20775, PDC40518, PDC40519, PDC40718, PDC40719, PDC40779
	   o   ServerWorks SATA, OSB4, CSB5, CSB6 (including support for the
	       third channel)
	   o   Silicon Image SiI3112, SiI3512, SiI3114
	   o   Silicon Integrated System 180, 181, 5513 (5597/5598), 540, 550,
	       620, 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652,
	       655, 658, 661, 730, 733, 735, 740, 745, 746, 748, 750, 751,
	       752, 755, 760, 962, 963
	   o   VIA Technologies CX700, VT82C586/A/B, VT82C596A/B, VT82C686A/B,
	       VT8231, VT8366, VT8233, VT8235, VT8237, VT8237A/S, VT8251,
	       VT6410, VX700, VX855

     Some of these controllers are only available in multifunction PCI chips.

     The 0x0001 flag forces the pciide driver to use DMA when there is no
     explicit DMA mode setting support for the controller but DMA is present.
     If the BIOS didn't configure the controller properly, this can cause a
     machine hang.

SEE ALSO
     atapiscsi(4), intro(4), jmb(4), pci(4), scsi(4), wd(4), wdc(4)

BUGS
     There's no way to know reliably if a CMD064x controller is enabled or
     not.  If the driver finds a PCI064x, it will assume it is enabled unless
     PCIIDE_CMD064x_DISABLE is specified in the kernel config file.  This will
     be a problem only if the controller has been disabled in the BIOS and
     another controller has been installed which uses the ISA legacy I/O ports
     and interrupts.

     The CMD0646U is reportedly unable to operate properly in UltraDMA mode.
     UltraDMA will not be enabled on this controller unless
     PCIIDE_CMD0646U_ENABLEUDMA is specified in the kernel config file.

     For proper operation of UltraDMA 3 and higher modes a 40-pin, 80-
     conductor cable must be used.  On some controllers, the pciide driver can
     probe the chip and see if it detects that an 80-conductor or 40-conductor
     cable was used.  If not, it will down-grade to UltraDMA 2 mode.  On other
     controllers, no such capability exists, and the driver assumes you are
     using an 80-conductor cable.  If you are getting errors about corrupted
     data, check to make sure you are using the correct cable.	An 80-
     conductor cable is recommended for any IDE installation, not just ones
     using faster UltraDMA modes, because it will decrease electrical noise
     and increase data reliability.

     The AMD756 chip revision D2 has a bug affecting DMA (but not Ultra-DMA)
     modes.  The workaround documented by AMD is to not use DMA on any drive
     which does not support Ultra-DMA modes.  This does not appear to be
     necessary on all drives, the PCIIDE_AMD756_ENABLEDMA option can be used
     to force multiword DMA on the buggy revisions.  Multiword DMA can
     eventually be disabled on a per-drive basis with config flags, see wd(4).
     The bug, if triggered, will cause a total system hang.

     The timings used for the PIO and DMA modes for controllers listed above
     are for a PCI bus running at 30 or 33 MHz.	 These timings will work on a
     slower bus, but they may cause errors on an over-clocked bus.

OpenBSD 4.9			March 25, 2010			   OpenBSD 4.9
[top]

List of man pages available for OpenBSD

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net