Return to mpcc.4 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / tahoe

BSD 4.3tahoe

.\" Copyright (c) 1987 Regents of the University of California.
.\" All rights reserved.  The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\"
.\"	@(#)mpcc.4	6.3 (Berkeley) 7/20/88
.\"
.TH MPCC 4 "July 20, 1988"
.UC 7
.SH NAME
mpcc \- Multi protocol communications controller
.SH SYNOPSIS
device mp0 at vba? csr 0xffff5000 mpintr mpdlintr
.br
thru
.br
device mp15 at vba? csr 0xffff5f00 mpintr mpdlintr
.SH DESCRIPTION
The MPCC has two different connecter panel styles.
The 16 port MPCC will support any combination of SYNC or ASYNC ports.
The 32 port MPCC will only support ASYNC ports.
Each async line attached to the MPCC communications controller
behaves as described in
.IR tty (7)
and may be set to run at any of 16 speeds; see
.IR tty (7)
for the encoding.
.PP
Each MPCC controller uses 2 consecutive entries in the 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 MPCC controller requires a firmware download to be completed
before it can function.  See \fIdlmpcc\fP(8) and \fImpcctab\fP(4)
for specific information on how to configure and download the
firmware into the MPCC controller.
.PP
A maximum of 16 MPCC communication controllers can be supported.
.SH FILES
/dev/tty[A-P][0-f] for 16 port MPCC
.br
/dev/tty[A-P][0-f,g-v] for 32 port MPCC
.SH "SEE ALSO"
tty(7)
.SH BUGS
As of the 4.3BSD-tahoe release, only 16 port mpcc's work, and then
only in async mode.  Attempting to reload firmware on an mpcc with
active ports may crash the system.  This should be fixed within
a short period of time; contact the CSRG at University of California,
Berkeley, for upgrade information.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.