mpcc.4

早期freebsd实现

.\" Copyright (c) 1987, 1991 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" This code is derived from software contributed to Berkeley by
.\" Computer Consoles Inc.
.\"
.\" 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 the University of
.\"	California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``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 REGENTS OR CONTRIBUTORS 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.
.\"
.\"     @(#)mpcc.4	6.6 (Berkeley) 5/10/91
.\"
.Dd May 10, 1991
.Dt MPCC 4
.Os
.Sh NAME
.Nm mpcc
.Nd multi protocol communications controller
.Sh SYNOPSIS
.Cd "device mp0 at vba? csr 0xffff5000 mpintr mpdlintr"
.br
	thru
.Cd "device mp15 at vba? csr 0xffff5f00 mpintr mpdlintr"
.Sh DESCRIPTION
The
.Tn MPCC
has two different connecter panel styles.
The 16 port
.Tn MPCC
will support any combination of
.Tn SYNC
or
.Tn ASYNC
ports.
The 32 port
.Tn MPCC
will only support
.Tn ASYNC
ports.
Each async line attached to the
.Tn MPCC
communications controller
behaves as described in
.Xr tty 7
and may be set to run at any of 16 speeds; see
.Xr tty
for the encoding.
.Pp
Each
.Tn MPCC
controller uses two consecutive entries in the
.Tn SCB
for
download/handshake, and command/response interrupts.  These entries
start at 0xa0 for the 1st controllers download/handshake interrupts
and 0xa1 for the 1st controllers command/response.
.Pp
The
.Tn MPCC
controller requires a firmware download to be completed
before it can function.  See
.Xr dlmpcc 8
and
.Xr mpcctab 4
for specific information on how to configure and download the
firmware into the
.Tn MPCC
controller.
.Pp
A maximum of 16
.Tn MPCC
communication controllers can be supported.
.Sh FILES
.Bl -tag -width /dev/tty[A-P][0-f,g-v] -compact
.It Pa /dev/tty[A-P][0-f]
for 16 port
.Tn MPCC
.It Pa /dev/tty[A-P][0-f,g-v]
for 32 port
.Tn MPCC
.El
.Sh SEE ALSO
.Xr tty 7
.Sh HISTORY
The
.Nm mpcc
driver appeared in
.Bx 4.3 tahoe .
.Sh BUGS
As of the
.Bx 4.3 tahoe
release, only 16 port
.Nm mpcc Ns 's
work, and then
only in async mode.  Attempting to reload firmware on an
.Nm mpcc
with
active ports may crash the system.  This should be fixed within
a short period of time; contact the
.Tn CSRG
at University of California,
Berkeley, for upgrade information.