syac(7) DG/UX R4.11MU05 syac(7)
NAME
syac, spac - Systech VMEbus/PCI bus asynchronous controllers
SYNOPSIS
syac(parent-bus[,controller-num[,port]])
spac(parent-bus[,pci-device-num[,pci-function-num[,port]]])
DESCRIPTION
The syac device name specifies an intelligent Systech VMEbus
asynchronous terminal I/O controller that connects to a number of
terminal lines. The supported syac controller models are:
VAC/16: A 16-port asynchronous controller. The ports for this
device are wired directly to the controller and appear on
the rear of the computer cabinet.
VDA/128: A terminal server host adapter supporting up to 128
asynchronous lines from one or more remote cluster control
boxes connected via a dedicated ARCNET. Each cluster
control box is either a VDC/8P (with 8 serial ports and a
single parallel port), a VDC/16 (with 16 serial ports), or
a VDC/16P running in emulation mode (as either a VDC/8P or
as a VDC/16).
VDA/255: A terminal server host adapter supporting up to 255
asynchronous lines from one or more remote cluster control
boxes connected via a dedicated ARCNET. The same cluster
boxes supported by the VDA/128 are used by the VDA/255.
VTC/256: A network terminal server host adapter supporting up to 256
network terminal connections on an Ethernet local area
network. The VTC/256 supports a general board Internet
address and optional terminal-specific Internet addresses.
The VTC/256 supports telnet, rlogin, and tcp connections,
as well as call-out connections. By default, ttys
associated with a VTC answer telnet connections made to the
default Internet address for that VTC and telnet binary
mode is negotiated on when a telnet connection is
established. The TCP port, protocol, direction, and telnet
binary modes of a connection can be specified on a per-tty
basis in vtc.addrs(4M). The VTC/256 controller also has an
SNMP agent. The VTC's SNMP communities, hosts, traps, and
site specific objects can be specified by modifying the VTC
SNMP files (see vtc_snmp_files(4M)). The VTC's default
SNMP community is public with read access only.
The spac device name specifies an intelligent Systech PCI bus
asynchronous terminal I/O controller that connects to a number of
terminal lines. The only supported spac controller model is:
PTC/1024: A network terminal server host adapter supporting up to
1024 network terminal connections on an Ethernet local area
network. The PTC/1024's functionality is identical to the
VTC/256, and it also uses the same configuration files (see
vtc.addrs(4M) and vtc_snmp_files(4M)).
The Systech intelligent asynchronous controllers are actually
processors that perform I/O processing according to the tty modes in
effect for each line. It is necessary for the system administrator
to load the controller-resident code image, using tcload(1M), into
the controller's memory before its lines can be used. Please note
that although the maximum number of connections as specified above
for each controller is possible, the I/O performance of each line
decreases as the number of concurrent connections reaches a
controller's maximum capacity.
To configure syac or spac devices, you must add one or more device
name entries to the DG/UX system configuration file, using the form
described in the synopsis above. The parameters in a syac or spac
device name have the following meanings:
· The parent-bus parameter is itself a device name, representing
either the VME or PCI bus device to which the controller is
attached (e.g. vme(0), vme(1), pci(0), or pci(1)). There is no
default value for this parameter; it must always be explicitly
specified.
· The controller-num parameter is a hexadecimal number in the range
0 through F that distinguishes the various standard VME
addressing values to which the syac controller may be jumpered.
Consult the table below for details on these address settings.
The default value for controller-num is zero.
· The pci-device-num parameter is a hexadecimal number in the range
0 through 1F; it represents the PCI device number ("slot number")
used by the spac controller. The default value for pci-device-
num is 0.
· The pci-function-num parameter is a hexadecimal number in the
range 0 through 7 which represents the PCI function number used
by the controller within pci-device-num. The default value for
pci-device-num is 0; non-zero values will be used only if the
controller lies on a multi-function card.
· The port parameter is a hexadecimal number which identifies a
particular asynchronous serial port on a syac or spac device.
The first port on the device uses port number 1, the second uses
2, and so on. The default value for port is the special value 0,
which identifies the syac or spac controller itself, distinct
from any of the lines on it.
These ports present the standard terminal interface described in
termio(7), except for the following unsupported features:
· The stty options for hardware flow control via carrier detect
(cdxon) and isochronous hardware flow control (isxoff)
· The CDXON or ISXOFF flags of the x_hflag field of the termiox
structure
Each syac controller board contains two jumperable VME address
settings: the interrupt vector number used by the board, and the A32
address of the board's 32-bit control register space. The following
hexadecimal address values are used for the 16 standard controller-
num instances supported on each parent VME bus:
Controller Interrupt A32 Address
Number Vector
Number
0 60 E3000000 or 60000000
1 61 E3020000 or 60020000
2 62 E3040000 or 60040000
3 63 E3060000 or 60060000
4 64 E3080000 or 60080000
5 65 E30A0000
6 66 E30C0000
7 67 E30E0000
8 68 E3100000
9 69 E3120000
A 6A E3140000
B 6B E3160000
C 6C E3180000
D 6D E31A0000
E 6E E31C0000
F 6F E31E0000
A syac device can still be used even if it is not jumpered to one of
the standard address settings. However, such a device is referred to
as a non-standard instance, and it requires a different device name
format:
syac@intr-vec-num(parent-bus,a32-addr[,port])
The parameters in a non-standard syac device name have the following
meanings:
· The intr-vec-num value is the hexadecimal VME interrupt vector
number used by the board. There is no default value for this
parameter; it must always be explicitly specified.
· The parent-bus parameter has exactly the same meaning here as it
does in the standard device name format.
· The a32-addr parameter is the hexadecimal value of the VME A32
address of the board's 32-bit control register space. There is
no default value for this parameter; it must always be explicitly
specified.
· The port parameter has exactly the same meaning here as it does
in the standard device name format.
FILES
When a standard syac or spac controller is configured, it creates a
character-special device node for each port, using the associated
pathname:
/dev/async/line/syac(parent-bus,controller-num,port)
/dev/async/line/spac(parent-bus,pci-device-num,pci-function-num,port)
An additional node is created to refer to the entire syac or spac
controller itself, using the associated pathname:
/dev/async/ctrl/syac(parent-bus,controller-num)
/dev/async/line/spac(parent-bus,pci-device-num,pci_function-num)
For non-standard syac controller instances, the respective device
node pathnames are:
/dev/async/line/syac@intr-vec-num(parent-bus,a32-addr,port)
/dev/async/ctrl/syac@intr-vec-num(parent-bus,a32-addr)
The chk.devlink command is responsible for creating and maintaining
links to each port device node, with a pathname of the form
/dev/tty[0-9]* (see chk.devlink(1M) and devlinktab(4M)).
EXAMPLES
The following entries in a DG/UX configuration file configure two
different syac controllers that use standard addressing values:
syac(vme(1),0)
syac(vme(0),4)
The following entry configures a non-standard syac controller that
uses interrupt vector number 0x6F and VME A32 address 0xE1A00000:
syac@6F(vme(0),E1A00000)
The following entry configures a spac controller in the PCI slot that
uses PCI device number 0xB on the primary PC PCI host bridge:
spac(pci(0),B,0)
The following entry configures a spac controller in slot 3 of the
secondary Corollary PCI host bridge:
spac(cpci(1),3)
For more information about DG/UX device configuration, refer to
"Writing a Device Driver" in Programming in the DG/UX Kernel
Environment.
SEE ALSO
tcload(1M), vtc.addrs(4M), vtc_snmp_files(4M), chk.devlink(1M),
devlinktab(4M), system(4), pci_bus(7), termio(7), vme(7).
Licensed material--property of copyright holder(s)