Man page for puc(4) from NetBSD

1 files changed, 133 insertions, 0 deletions

diff --git a/share/man/man4/puc.4 b/share/man/man4/puc.4
new file mode 100644
index 00000000000..b2ea94fa2af
--- /dev/null
+++ b/share/man/man4/puc.4
@@ -0,0 +1,133 @@
+.\"	$OpenBSD: puc.4,v 1.1 2000/05/18 17:06:47 millert Exp $
+.\"	$NetBSD: puc.4,v 1.7 1999/07/03 05:55:23 cgd Exp $
+.\"
+.\" Copyright (c) 1998 Christopher G. Demetriou.  All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou
+.\"      for the NetBSD Project.
+.\" 4. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd July 11, 1998
+.Dt PUC 4
+.Os
+.Sh NAME
+.Nm puc
+.Nd PCI
+.Dq universal
+communications card driver
+.Sh SYNOPSIS
+.Cd "puc* at pci?
+.Cd "pccom* at puc? port ?"
+.Cd "lpt* at puc? port ?"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides support for PCI communications cards containing
+simple communications ports, such as NS16550-family
+.Pf ( Nm com )
+serial ports and standard PC-like
+.Pf ( Nm lpt )
+parallel ports.
+The driver is called
+.Dq universal
+because the interfaces to these devices aren't nearly as well
+defined and standard as they should be.
+.Pp
+The driver currently supports the following cards:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It Tn "Dolphin Peripherals 4014 (dual parallel)"
+.It Tn "Dolphin Peripherals 4035 (dual serial)"
+.It Tn "SIIG Cyber 2P1S PCI (dual parallel and single serial)"
+.It Tn "SIIG Cyber 2S1P PCI (dual serial and single parallel)"
+.It Tn "SIIG Cyber 4S PCI (quad serial)"
+.It Tn "SIIG Cyber I/O PCI (single serial and single parallel)"
+.It Tn "SIIG Cyber Parallel Dual PCI (dual parallel)"
+.It Tn "SIIG Cyber Parallel PCI (single parallel)"
+.It Tn "SIIG Cyber Serial Dual PCI (dual serial)"
+.It Tn "SIIG Cyber Serial PCI (single serial)"
+.It Tn "VScom PCI-800 (8 port serial, probably OEM)"
+.El
+.Pp
+The driver does not support the cards:
+.Pp
+.Bl -tag -width -offset indent -compact
+.It Tn "Dolphin Peripherals 4006 (single parallel)"
+.It Tn "Dolphin Peripherals 4025 (single serial)"
+.It Tn "Dolphin Peripherals 4078 (dual serial and single parallel)"
+.El
+.Pp
+but support for them (and for similar cards) should be trivial to add.
+.Pp
+The
+.Ar port
+locator is used to identify the port (starting from 0) on the
+communications card that a subdevice is supposed to attach to.
+Typically, the numbering of ports is explained in a card's
+hardware documentation, and the port numbers used by the driver
+are the same as (or one off from, e.g. the manual uses ports
+numbered starting from 1) those described in the documentation.
+.Sh SEE ALSO
+.Xr com 4 ,
+.Xr lpt 4 ,
+.Xr pci 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Nx 1.4 .
+.Sh AUTHOR
+The
+.Nm
+driver was written by Chris Demetriou.
+.Sh BUGS
+The current design of this driver keeps any
+.Nm com
+ports on these cards from easily being used as console.  Of
+course, because boards with those are PCI boards, they also suffer
+from dynamic address assignment, which also means that they
+can't easily be used as console.
+.Pp
+Some of cards supported by this driver have jumper-selectable
+.Nm com
+port clock multipliers, which are unsupported by this
+driver.  Those can be easily accommodated with driver flags, or by
+using a properly scaled baud rate when talking to the card.
+.Pp
+Some of the cards supported by this driver, e.g. the VScom PCI-800,
+have software-selectable
+.Nm com
+port clock multipliers, which are unsupported by this driver.
+Those can be accomodated using internal driver flags, or by using
+a properly scaled baud rate when talking to the card.
+.Pp
+Some ports use an
+.Nm lpt
+driver other than the machine-independent driver.  Those ports
+will not be able to use
+.Nm lpt
+ports attached to
+.Nm
+devices.