xref: /netbsd/share/man/man4/puc.4 (revision bf9ec67e)
1.\" $NetBSD: puc.4,v 1.13 2002/02/07 03:15:08 ross 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 Dv -offset indent -compact
64.It Tn "Dolphin Peripherals 4014 (dual parallel)"
65.It Tn "Dolphin Peripherals 4035 (dual serial)"
66.It Tn "NetMos NM9835 (dual parallel and single serial)"
67.It Tn "SIIG Cyber 2P1S PCI (dual parallel and single serial)"
68.It Tn "SIIG Cyber 2S1P PCI (dual serial and single parallel)"
69.It Tn "SIIG Cyber 4S PCI (quad serial)"
70.It Tn "SIIG Cyber I/O PCI (single serial and single parallel)"
71.It Tn "SIIG Cyber Parallel Dual PCI (dual parallel)"
72.It Tn "SIIG Cyber Parallel PCI (single parallel)"
73.It Tn "SIIG Cyber Serial Dual PCI (dual serial)"
74.It Tn "SIIG Cyber Serial PCI (single serial)"
75.It Tn "VScom PCI-800 (8 port serial, probably OEM)"
76.El
77.Pp
78The driver does not support the cards:
79.Pp
80.Bl -tag -width Fl -offset indent -compact
81.It Tn "Dolphin Peripherals 4006 (single parallel)"
82.It Tn "Dolphin Peripherals 4025 (single serial)"
83.It Tn "Dolphin Peripherals 4078 (dual serial and single parallel)"
84.El
85.Pp
86but support for them (and for similar cards) should be trivial to add.
87.Pp
88The
89.Ar port
90locator is used to identify the port (starting from 0) on the
91communications card that a subdevice is supposed to attach to.
92Typically, the numbering of ports is explained in a card's
93hardware documentation, and the port numbers used by the driver
94are the same as (or one off from, e.g. the manual uses ports
95numbered starting from 1) those described in the documentation.
96.Sh SEE ALSO
97.Xr com 4 ,
98.Xr lpt 4 ,
99.Xr pci 4
100.Sh HISTORY
101The
102.Nm
103driver appeared in
104.Nx 1.4 .
105.Sh AUTHORS
106The
107.Nm
108driver was written by Chris Demetriou.
109.Sh BUGS
110The current design of this driver keeps any
111.Nm com
112ports on these cards from easily being used as console.  Of
113course, because boards with those are PCI boards, they also suffer
114from dynamic address assignment, which also means that they
115can't easily be used as console.
116.Pp
117Some of cards supported by this driver have jumper-selectable
118.Nm com
119port clock multipliers, which are unsupported by this
120driver.  Those can be easily accommodated with driver flags, or by
121using a properly scaled baud rate when talking to the card.
122.Pp
123Some of the cards supported by this driver, e.g. the VScom PCI-800,
124have software-selectable
125.Nm com
126port clock multipliers, which are unsupported by this driver.
127Those can be accommodated using internal driver flags, or by using
128a properly scaled baud rate when talking to the card.
129.Pp
130Some ports use an
131.Nm lpt
132driver other than the machine-independent driver.  Those ports
133will not be able to use
134.Nm lpt
135ports attached to
136.Nm
137devices.
138