1.\" $OpenBSD: puc.4,v 1.8 2001/03/28 21:07:56 deraadt Exp $ 2.\" $NetBSD: puc.4,v 1.7 1999/07/03 05:55:23 cgd Exp $ 3.\" 4.\" Copyright (c) 1998 Christopher G. Demetriou. All rights reserved. 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 Christopher G. Demetriou 17.\" for the NetBSD Project. 18.\" 4. The name of the author may not be used to endorse or promote products 19.\" derived from this software 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 July 11, 1998 33.Dt PUC 4 34.Os 35.Sh NAME 36.Nm puc 37.Nd PCI 38.Dq universal 39communications card driver 40.Sh SYNOPSIS 41.Cd "puc* at pci? 42.Cd "pccom* at puc? port ?" 43.Cd "lpt* at puc? port ?" 44.Sh DESCRIPTION 45The 46.Nm 47driver provides support for PCI communications cards containing 48simple communications ports, such as NS16550-family 49.Pf ( Nm com ) 50serial ports and standard PC-like 51.Pf ( Nm lpt ) 52parallel ports. 53The driver is called 54.Dq universal 55because the interfaces to these devices aren't nearly as well 56defined and standard as they should be. 57.Pp 58The driver currently supports the following cards: 59.Pp 60.Bl -tag -width -offset indent -compact 61.It Tn "Dolphin Peripherals 4014 (dual parallel)" 62.It Tn "Dolphin Peripherals 4035 (dual serial)" 63.It Tn "SIIG Cyber 2P1S PCI (dual parallel and single serial)" 64.It Tn "SIIG Cyber 2S1P PCI (dual serial and single parallel)" 65.It Tn "SIIG Cyber 4S PCI (quad serial)" 66.It Tn "SIIG Cyber I/O PCI (single serial and single parallel)" 67.It Tn "SIIG Cyber Parallel Dual PCI (dual parallel)" 68.It Tn "SIIG Cyber Parallel PCI (single parallel)" 69.It Tn "SIIG Cyber Serial Dual PCI (dual serial)" 70.It Tn "SIIG Cyber Serial PCI (single serial)" 71.It Tn "SIIG Cyber 8S PCI 16C850" 72.It Tn "VScom PCI-800 (8 port serial, probably OEM)" 73.It Tn "AT&T/Lucent Venus Modem (found on IBM 33L4618 card, Actiontec 56K, and others)" 74.It Tn "US Robotics 3CP5609 PCI (modem)" 75.It Tn "Lava Computers 2SP-PCI (parallel port)" 76.It Tn "Lava Computers 2SP-PCI and Quattro-PCI (dual serial)" 77.It Tn "Lava Computers Octopus-550" 78.It Tn "Lava LavaPort-650" 79.It Tn "NEC PK-UG-X008 (serial)" 80.It Tn "NEC PK-UG-X001 K56flex PCI (modem)" 81.It Tn "Koutech IOFLEX-2S (dual serial)" 82.El 83.Pp 84The driver does not support these cards: 85.Pp 86.Bl -tag -width -offset indent -compact 87.It Tn "Dolphin Peripherals 4006 (single parallel)" 88.It Tn "Dolphin Peripherals 4025 (single serial)" 89.It Tn "Dolphin Peripherals 4078 (dual serial and single parallel)" 90.El 91.Pp 92but support for them (and for similar cards) should be trivial to add. 93.Pp 94The 95.Ar port 96locator is used to identify the port (starting from 0) on the 97communications card that a subdevice is supposed to attach to. 98Typically, the numbering of ports is explained in a card's 99hardware documentation, and the port numbers used by the driver 100are the same as (or one off from, e.g., the manual uses ports 101numbered starting from 1) those described in the documentation. 102.Sh SEE ALSO 103.Xr com 4 , 104.Xr lpt 4 , 105.Xr pci 4 106.Sh HISTORY 107The 108.Nm 109driver first appeared in 110.Nx 1.4 . 111.Ox 112support was added in 113.Ox 2.7 . 114.Sh AUTHORS 115The 116.Nm 117driver was written by Chris Demetriou. 118.Sh BUGS 119The current design of this driver keeps any 120.Nm com 121ports on these cards from easily being used as console. 122Of course, because boards with those are PCI boards, they also suffer 123from dynamic address assignment, which also means that they 124can't easily be used as console. 125.Pp 126Some of cards supported by this driver have jumper-selectable 127.Nm com 128port clock multipliers, which are unsupported by this driver. 129Those can be easily accommodated with driver flags, or by 130using a properly scaled baud rate when talking to the card. 131.Pp 132Some of the cards supported by this driver, e.g., the VScom PCI-800, 133have software-selectable 134.Nm com 135port clock multipliers, which are unsupported by this driver. 136Those can be accommodated using internal driver flags, or by using 137a properly scaled baud rate when talking to the card. 138.Pp 139Some ports use an 140.Nm lpt 141driver other than the machine-independent driver. 142Those ports will not be able to use 143.Nm lpt 144ports attached to 145.Nm 146devices. 147