ssid(7) DG/UX R4.11MU05 ssid(7)
NAME
ssid - Systech VME Synchronous controller (88K only)
SYNOPSIS
ssid(parent-bus[,controller-num[,line-num]])
DESCRIPTION
The ssid device driver provides access to a Systech VMEbus
synchronous communications controller (VSC). To configure such a
device, you must add to the DG/UX system configuration file one or
more device name entries of the form described in the synopsis above.
The parameters in a device name have the following meanings:
· The parent-bus parameter is itself a device name, representing
the VME bus device to which the controller is attached (vme(0) or
vme(1), for example). There is no default value for this
parameter; it must always be specified explicitly.
· The controller-num parameter is a hexadecimal number in the range
0 through F which distinguishes the various standard addressing
values to which the controller may be jumpered. Consult the
table below for details on these address settings. The default
value for controller-num is 0.
· The line-num parameter is a hexadecimal number which identifies a
particular synchronous port on the ssid device. The value 1
refers to port A, 2 refers to port B, 3 refers to port C and 4
refers to port D. The default value for line-num is the special
value 0, which identifies the ssid controller itself, distinct
from any of the lines on it.
Each ssid controller board contains two jumperable VME board 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 by the device driver on each parent VME bus:
Controller Interrupt A32 Address
Number Vector
Number
0 50 55B00000
1 51 55B10000
2 52 55B20000
3 53 55B30000
4 54 55B40000
5 55 55B50000
6 56 55B60000
7 57 55B70000
8 58 E2080000
9 59 E2090000
A 5A E20A0000
B 5B E20B0000
C 5C E20C0000
D 5D E20D0000
E 5E E20E0000
F 5F E20F0000
A ssid 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:
ssid@intr-vec-num(parent-bus,a32-addr[,line-num])
The parameters in a non-standard 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 specified explicitly.
· 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 specified
explicitly.
· The line-num parameter has exactly the same meaning here as it
does in the standard device name format.
In conjunction with the ssid system file entries, the following
tunable kernel parameters are used by all ssid devices configured
into the system:
· SSID_WRIOCBS specifies the number of write I/O control blocks
allocated for each unit. A write I/O control block is used to
send output messages to the VSC device. The default value is 8.
· SSID_RDIOCBS specifies the number of read I/O control blocks
allocated for each unit. A read I/O control block is used to
receive input messages from the VSC device. The default value is
8.
· SSID_CTLIOCBS specifies the number of control I/O control blocks
allocated for each unit. A control I/O control block is used to
send ioctl or flush messages to the VSC device. The default
value is 3.
· SSID_CLONES specifies the number of allowable clone opens for the
clone device. The default value is 4.
The ssid driver supports the following internally generated baud
rates: 1200, 2400, 4800, 9600, 19200, 38400, 48000, 56000 and 64000
bps. The driver will accept any external clock data rate up to 64000
bps.
The ssid board resident code has fixed I/O buffer area of 16380 bytes
per line. This I/O area may be divided into I/O buffers according to
the following rules:
· The maximum frame size cannot exceed 4096 bytes.
· The sum total number of buffers (both Rx and Tx) multiplied by
the maximum frame size cannot exceed 16380 bytes.
· The sum total number of buffers (both Rx and Tx) cannot exceed
30.
FILES
When a standard ssid controller is configured, it creates a
character-special device node for each serial port, using the
pathname:
/dev/sync/line/ssid(parent-bus,controller-num,line-num)
A character-special device node for the whole controller is also
created, using the pathname:
/dev/sync/ctrl/ssid(parent-bus,controller-num)
This device is used for tasks that require direct access to the
controller, such as downloading its intelligent controller code.
Only one open at a time is permitted on this device.
A second character-special device node for the whole controller is
also created, using the pathname:
/dev/sync/stat/ssid(parent-bus,controller-num)
This device node is a clonable Streams device node, which means that
it can be opened multiple times in order to perform line management
functions such as statistics manipulation and line configuration.
For non-standard controller instances, the respective device node
pathnames are instead:
/dev/sync/line/ssid@intr-vec-num(parent-bus,a32-addr,line-num)
/dev/sync/ctrl/ssid@intr-vec-num(parent-bus,a32-addr)
/dev/sync/stat/ssid@intr-vec-num(parent-bus,a32-addr)
EXAMPLES
The following entries in a DG/UX configuration file configure VSC
devices that use two of the standard sets of addressing values:
ssid(vme(0),0)
ssid(vme(0),4)
The following statement configures a non-standard VSC device which
uses interrupt vector number 0x4F and VME A32 address 0xE1A00000:
ssid@4F(vme(0),E1A00000)
For more information about DG/UX device configuration, refer to
"Writing a Device Driver" in Programming in the DG/UX Kernel
Environment.
SEE ALSO
wanadm(1M), vme(7), synccheck(1M), vscload(1M).
Licensed material--property of copyright holder(s)