dpfn(7) DG/UX R4.11MU05 dpfn(7)
NAME
dpfn - DEC PCI FDDI Network Interface
SYNOPSIS
dpfn(parent-bus[,pci-device-num[,pci-function-num[,alt-fddi-addr]]])
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 100 Mb/s 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 to the DG/UX
system configuration file a device name entry 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 PCI bus device to which the controller is attached (pci(0),
for example). There is no default value for this parameter; it
must always be specified explicitly.
· 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 device. The default value for pci-device-num is 0.
· The pci-function-num parameter is a hexadecimal number in the
range 0 through 7; it 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 alt-fddi-addr parameter can be used to override the
controller's default FDDI station address with a user-specified
value, which must be represented as a string of exactly 12
hexadecimal digits. If no alt-fddi-addr 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:
· 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 0 for this parameter 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(parent-bus,pci-device-num,pci-function-num)
The chk.devlink command is responsible for creating and maintaining
an additional link to each dpfn device node, with a pathname of the
form /dev/net/dpfn[0-9]*. See the chk.devlink(1M) and devlinktab(4M)
man pages for details.
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
dpfn adapters at nodes /dev/net/dpfn(cpci(0),4,0) and
/dev/net/dpfn(cpci(1),2,0). The first card is connected to slot 4 of
the primary Corollary PCI host bridge, and the second card is
connected to slot 2 of the secondary Corollary PCI host bridge.
dpfn(cpci(0),4,0)
dpfn(cpci(1),2,0)
The following statement configures a dpfn 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), pci_bus(7),
intro(7).
Licensed material--property of copyright holder(s)