Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ dpen(7) — DG/UX R4.11

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ifconfig(1M)

netinit(1M)

netstat(1C)

admdevice(1M)

system(4)

chk.devlink(1M)

devlinktab(4M)

arp(6P)

inet(6F)

intro(7)



dpen(7)                          DG/UX R4.11                         dpen(7)


NAME
       dpen - DecChip 21040/21140 Ethernet Network Interface for PCI

SYNOPSIS
       dpen(parentbus,slotnumber,functionnumber[,hardwareaddress,media])

DESCRIPTION
       The dpen device driver allows a DG/UX system that includes Ethernet
       adapters with a DecChip 21040/21140 local area network (LAN)
       controller to access an Ethernet network. 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
                           dpen adapter is attached.  Currently, dpen can
                           only be attached to a PCI bus.

       slotnumber         The parentbus slot in which the DecChip
                           21040/21140-based Ethernet adapter resides.

       functionnumber     The network interface instance number for those
                           PCI cards with more than one Ethernet controller.
                           Note: The instance number for adapters with an
                           internal PCI bridge is zero, since each adapter
                           instance occupies a separate pci slot. This
                           parameter normally has a value of zero.


       hardwareaddress
                      An overriding alternate IEEE 802.3/Ethernet address
                      for this adapter on the network.

       media          An overriding media type for this adapter.  Where the
                      following media types/options are supported:

                      10B - for cable running 10BaseT
                      FD - for cable running 10BaseT or 100BaseTx full duplex
                      10FD - for 10BaseT cable running full duplex
                      100 - for cable running 100BaseTX
                      100FD - for 100BaseTX cable running Full Duplex
                      AUI - for cable running 10Base5
                      BNC - for cable running 10Base2

                      Some adapters with both TP and AUI/BNC connectors can
                      detect and autoconfigure the correct TP or AUI/BNC
                      interface; other adapters require specification of the
                      appropriate media parameter.  Some dual-speed adapters
                      can be configured with either a 10BaseT or 100BaseTX
                      interface; 100BaseTX is the default.  Check the
                      hardware manual for the adapter to determine if a
                      media parameter and/or jumper changes on the adapter
                      are required.  If it is not clear whether or not the
                      adapter will autosense/autoconfigure to the correct
                      mode, the dpen driver's media parameters can be used
                      to set the adapter into the correct mode.

                      Autoconfiguration of full-duplex support is not
                      supported. Full-duplex support must be defined as a
                      media parameter and is only supported on 10BaseT and
                      100BaseTX Full-Duplex Ethernet networks which are
                      generally connected to an Ethernet Switch that
                      supports Full-Duplex connectivity.

       Each dpen device creates a single character-special device node when
       it is configured:

       /dev/net/dpen(parentbus, slotnumber, functionnumber)

       Later, during system initialization, symbolic links are created in
       /dev, in the form /dev/dpenadapternumber, 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 dpen device node, with a
       pathname of the form /dev/net/dpen[0-n].  See the chk.devlink(1M) and
       devlinktab(4M) man pages.

       The dpen device is implemented as a clonable Streams driver. This
       means that you can open a single node, such as /dev/dpen0, 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
       DecChip 21040/21140-based adapters at nodes /dev/net/dpen(pci(0),4,0)
       and /dev/net/dpen(pci(0),E,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 E (14 decimal).

       dpen(pci(0),4,0)
       dpen(pci(0),e,0)

       The following statement configures a DecChip 21040/21140-based
       Ethernet adapter with an alternate Ethernet address:

       dpen(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)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026