vsxb(7) DG/UX R4.11MU05 vsxb(7)
NAME
vsxb - VME Streams Cross Bus synchronous controller
SYNOPSIS
vsxb(parent-bus[,controller-num[,line-num]])
DESCRIPTION
The vsxb device driver provides access to an intelligent VMEbus
synchronous communications controller (VSCi). 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 vsxb device. The value 1
refers to port A, 2 refers to port B and 3 refers to port C. The
default value for line-num is the special value 0, which
identifies the vsxb controller itself, distinct from any of the
lines on it.
Each vsxb 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 90 E3400000
1 91 E3410000
2 92 E3420000
3 93 E3430000
4 94 E3440000
5 95 E3450000
6 96 E3460000
7 97 E3470000
8 98 E3480000
9 99 E3490000
A 9A E34A0000
B 9B E34B0000
C 9C E34C0000
D 9D E34D0000
E 9E E34E0000
F 9F E34F0000
A vsxb 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:
vsxb@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 vsxb system file entries, the following
tunable kernel parameters are used by all vsxb devices configured
into the system:
· VSXB_CLONES is the total number of vsxb() clone devices that may
exist per controller. The default value is 4.
· VSXB_B<class-num>_CNT is the number of streams buffers of class
class-num (which is in the range {0..7}) for the onboard VSXBC
environment. The default values varies with each class; see the
DG/UX master file (/usr/etc/master.d/dgux) for details.
· VSXB_B<class-num>_SZ is the size in bytes of the Streams buffers
in class class-num (which is in the range {0..7}) for the onboard
VSXBC environment. The default values varies with each class;
see the DG/UX master file (/usr/etc/master.d/dgux) for details.
· VSXB_QS is the number of streams queue pairs in the onboard VSXBC
environment. The default value is 40.
· VSXB_STRS is the number of streams in the onboard VSXBC
environment. The default value is 16.
· VSXB_MBS is the number of mblocks in the onboard VSXBC
environment. The default value is 1024.
· VSXB_BCS is the number of bufcalls allowed at one time in the
onboard VSXBC environment. The default value is 32.
· VSXB_TOS is the number of timeouts allowed at one time in the
onboard VSXBC environment. The default value is 32.
· VSXB_LOW is the percentage of streams buffers permitted to be
used for low priority allocb() calls. The default value is 70.
· VSXB_MED is the percentage of streams buffers permitted to be
used for medium priority allocb() calls. The default value is
90.
· VSXB_W_STR is the number of write side crossbus structures per
communication stream. The default value is 16.
· VSXB_R_STR is the number of read side crossbus structures per
communication stream. The default value is 16.
The vsxb driver supports internally generated baud rates from 2400 to
64000 bps. The driver will accept any external clock data rate up to
64000 bps.
The maximum frame size can not exceed 4109 bytes.
The vsxb device supports the following external interfaces:
+----------+------------+------------+
|Interface | Electrical | Physical |
+----------+------------+------------+
|RS-232 | RS-232 | DB25 |
|V.35 | V.35 | Winchester |
|RS-530 | RS-442 | DB25 |
|RS-449 | RS-422 | DB37 |
|X.21 | RS-422 | DB15 |
+----------+------------+------------+
FILES
When a standard vsxb controller is configured, it creates a
character-special device node for each serial port, using the
pathname:
/dev/sync/line/vsxb(parent-bus,controller-num,line-num)
A character-special device node for the whole controller is also
created, using the pathname:
/dev/sync/ctrl/vsxb(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/vsxb(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/vsxb@intr-vec-num(parent-bus,a32-addr,line-num)
/dev/sync/ctrl/vsxb@intr-vec-num(parent-bus,a32-addr)
/dev/sync/stat/vsxb@intr-vec-num(parent-bus,a32-addr)
EXAMPLES
The following entries in a DG/UX configuration file configure VSCi
devices that use two of the standard sets of addressing values:
vsxb(vme(1),0)
vsxb(vme(0),4)
The following statement configures a non-standard VSCi device which
uses interrupt vector number 0x4F and VME A32 address 0xE1A00000:
vsxb@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)