1.\" $NetBSD: puc.4,v 1.9 2000/06/14 17:25:32 cgd Exp $ 2.\" 3.\" Copyright (c) 1998 Christopher G. Demetriou 4.\" 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 for the 17.\" NetBSD Project. See http://www.netbsd.org/ for 18.\" information about NetBSD. 19.\" 4. The name of the author may not be used to endorse or promote products 20.\" derived from this software without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 23.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 24.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 25.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 26.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 27.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 28.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 29.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 30.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 31.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 32.\" 33.\" <<Id: LICENSE,v 1.2 2000/06/14 15:57:33 cgd Exp>> 34.\" 35.Dd July 11, 1998 36.Dt PUC 4 37.Os 38.Sh NAME 39.Nm puc 40.Nd PCI 41.Dq universal 42communications card driver 43.Sh SYNOPSIS 44.Cd "puc* at pci? dev ? function ?" 45.Cd "com* at puc? port ?" 46.Cd "lpt* at puc? port ?" 47.Sh DESCRIPTION 48The 49.Nm 50driver provides support for PCI communications cards containing 51simple communications ports, such as NS16550-family 52.Pf ( Nm com ) 53serial ports and standard PC-like 54.Pf ( Nm lpt ) 55parallel ports. 56The driver is called 57.Dq universal 58because the interfaces to these devices aren't nearly as well 59defined and standard as they should be. 60.Pp 61The driver currently supports the following cards: 62.Pp 63.Bl -tag -width -offset indent -compact 64.It Tn "Dolphin Peripherals 4014 (dual parallel)" 65.It Tn "Dolphin Peripherals 4035 (dual serial)" 66.It Tn "SIIG Cyber 2P1S PCI (dual parallel and single serial)" 67.It Tn "SIIG Cyber 2S1P PCI (dual serial and single parallel)" 68.It Tn "SIIG Cyber 4S PCI (quad serial)" 69.It Tn "SIIG Cyber I/O PCI (single serial and single parallel)" 70.It Tn "SIIG Cyber Parallel Dual PCI (dual parallel)" 71.It Tn "SIIG Cyber Parallel PCI (single parallel)" 72.It Tn "SIIG Cyber Serial Dual PCI (dual serial)" 73.It Tn "SIIG Cyber Serial PCI (single serial)" 74.It Tn "VScom PCI-800 (8 port serial, probably OEM)" 75.El 76.Pp 77The driver does not support the cards: 78.Pp 79.Bl -tag -width -offset indent -compact 80.It Tn "Dolphin Peripherals 4006 (single parallel)" 81.It Tn "Dolphin Peripherals 4025 (single serial)" 82.It Tn "Dolphin Peripherals 4078 (dual serial and single parallel)" 83.El 84.Pp 85but support for them (and for similar cards) should be trivial to add. 86.Pp 87The 88.Ar port 89locator is used to identify the port (starting from 0) on the 90communications card that a subdevice is supposed to attach to. 91Typically, the numbering of ports is explained in a card's 92hardware documentation, and the port numbers used by the driver 93are the same as (or one off from, e.g. the manual uses ports 94numbered starting from 1) those described in the documentation. 95.Sh SEE ALSO 96.Xr com 4 , 97.Xr lpt 4 , 98.Xr pci 4 99.Sh HISTORY 100The 101.Nm 102driver appeared in 103.Nx 1.4 . 104.Sh AUTHOR 105The 106.Nm 107driver was written by Chris Demetriou. 108.Sh BUGS 109The current design of this driver keeps any 110.Nm com 111ports on these cards from easily being used as console. Of 112course, because boards with those are PCI boards, they also suffer 113from dynamic address assignment, which also means that they 114can't easily be used as console. 115.Pp 116Some of cards supported by this driver have jumper-selectable 117.Nm com 118port clock multipliers, which are unsupported by this 119driver. Those can be easily accommodated with driver flags, or by 120using a properly scaled baud rate when talking to the card. 121.Pp 122Some of the cards supported by this driver, e.g. the VScom PCI-800, 123have software-selectable 124.Nm com 125port clock multipliers, which are unsupported by this driver. 126Those can be accomodated using internal driver flags, or by using 127a properly scaled baud rate when talking to the card. 128.Pp 129Some ports use an 130.Nm lpt 131driver other than the machine-independent driver. Those ports 132will not be able to use 133.Nm lpt 134ports attached to 135.Nm 136devices. 137