dpfn(7) DG/UX R4.11 dpfn(7)
NAME
dpfn - Model 7453, 7454, and 7455 PCI FDDI Controllers Network
Interface
SYNOPSIS
dpfn(parentbus,slotnumber[,functionnumber[,hardwareaddress]])
DESCRIPTION
The dpfn device driver allows a DG/UX system that includes one or
more Model 7453, 7454, or 7455 PCI FDDI local area network (LAN)
adapters to access a Fiber Distributed Data Interface (FDDI) network.
These controllers are 100Mbit FDDI adapters for Dual Attach Fiber
(7453), Single Attach Fiber (7454), and Single Attach Copper (7455)
Lan Media. To configure such devices, you must add one or more
device name entries (as described in the Synopsis) to the DG/UX
system configuration file. The parameters in the device name entry
are defined as follows:
parentbus The device name of the parent bus to which the
dpfn adapter is attached. The PCI FDDI adapters
can be attached only to a PCI bus.
slotnumber The parentbus slot in which the Model 7453,
7454, or 7455 PCI FDDI adapter resides.
functionnumber The network interface instance number for those
PCI cards with more than one FDDI interface.
This parameter must have a value of zero, since
no multi-function adapters are currently
supported.
hardwareaddress
An overriding alternate FDDI station address for this
adapter on the network with a user-specified value,
which must be represented as a string of exactly 12
hexadecimal digits. If no hardwareaddress parameter
is specified, the controller-resident default FDDI
station address is used.
In conjunction with the dpfn system file entries, the following
tunable kernel parameters are used by all dpfn devices configured
into the system:
ยท DPFNBUFFERCOUNT (alias for cf_dpfn_buffer_count) is the count
of receive buffers for DPFN. This may be adjusted to prevent DPFN
from hogging the bus for an extended time if necessary. The
range of valid values is {0 .. 64}; a value of this parameter of
0 will result in an effective value of 32, which is the default.
A value greater than 64 will result in an effective value of 64.
Each dpfn device creates a single character-special device node when
it is configured:
/dev/net/dpfn(parentbus, slotnumber, functionnumber)
Later, during system initialization, symbolic links are created in
/dev, in the form /dev/dpfn[adapternumber], as defined by the
corresponding entries in /etc/devlinktab. These symbolic links
provide for more convenient user access.
The chk.devlink command also is responsible for creating and
maintaining an additional link to each dpfn device node, with a
pathname of the form /dev/net/dpfn[0-n]. See the chk.devlink(1M) and
devlinktab(4M) man pages.
The dpfn device is implemented as a clonable Streams driver. This
means that you can open a single node, such as /dev/dpfn0, to access
any unused minor device. Each subsequent access of the node via the
open(2) system call allocates a separate Stream (minor number) to the
device driver.
EXAMPLES
The following entries in a DG/UX configuration file configure two
Model 7453, 7454, or 7455 PCI FDDI adapters at nodes
/dev/net/dpfn(pci(0),4,0) and /dev/net/dpfn(pci(0),6,0). The first
example is attached to the pci(0) bus in slot 4, and the second
example is attached to the pci(0) bus in slot 6.
dpfn(pci(0),4,0)
dpfn(pci(0),6,0)
The following statement configures a Model 7453, 7454, or 7455 PCI
FDDI adapter with an alternate FDDI station address:
dpfn(pci(0),6,0,08001b123456)
For more information about DG/UX device configuration, refer to
"Writing a Device Driver" in Programming in the DG/UX Kernel
Environment.
FILES
/etc/devlinktab This file contains entries used to make short-named
links to device nodes.
DIAGNOSTICS
Use the -i option with netstat(1C).
Use the -o specify, -o configure, or -o deconfigure option with
admdevice(1M).
SEE ALSO
ifconfig(1M), netinit(1M), netstat(1C), admdevice(1M), system(4),
chk.devlink(1M), devlinktab(4M), arp(6P), inet(6F), pcibus(7),
intro(7).
Licensed material--property of copyright holder(s)