|
|
1.1 root 1: .\" Copyright (c) 1987 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)mpcc.4 6.3 (Berkeley) 7/20/88
6: .\"
7: .TH MPCC 4 "July 20, 1988"
8: .UC 7
9: .SH NAME
10: mpcc \- Multi protocol communications controller
11: .SH SYNOPSIS
12: device mp0 at vba? csr 0xffff5000 mpintr mpdlintr
13: .br
14: thru
15: .br
16: device mp15 at vba? csr 0xffff5f00 mpintr mpdlintr
17: .SH DESCRIPTION
18: The MPCC has two different connecter panel styles.
19: The 16 port MPCC will support any combination of SYNC or ASYNC ports.
20: The 32 port MPCC will only support ASYNC ports.
21: Each async line attached to the MPCC communications controller
22: behaves as described in
23: .IR tty (7)
24: and may be set to run at any of 16 speeds; see
25: .IR tty (7)
26: for the encoding.
27: .PP
28: Each MPCC controller uses 2 consecutive entries in the SCB for
29: download/handshake, and command/response interrupts. These entries
30: start at 0xa0 for the 1st controllers download/handshake interrupts
31: and 0xa1 for the 1st controllers command/response.
32: .PP
33: The MPCC controller requires a firmware download to be completed
34: before it can function. See \fIdlmpcc\fP(8) and \fImpcctab\fP(4)
35: for specific information on how to configure and download the
36: firmware into the MPCC controller.
37: .PP
38: A maximum of 16 MPCC communication controllers can be supported.
39: .SH FILES
40: /dev/tty[A-P][0-f] for 16 port MPCC
41: .br
42: /dev/tty[A-P][0-f,g-v] for 32 port MPCC
43: .SH "SEE ALSO"
44: tty(7)
45: .SH BUGS
46: As of the 4.3BSD-tahoe release, only 16 port mpcc's work, and then
47: only in async mode. Attempting to reload firmware on an mpcc with
48: active ports may crash the system. This should be fixed within
49: a short period of time; contact the CSRG at University of California,
50: Berkeley, for upgrade information.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.