hken(7) DG/UX 4.30 hken(7)
NAME
hken - Hawk Ethernet interface
SYNOPSIS
hken ([0] | [1]) |
hken ([0] | [1],,alternate_ethernet_address]) |
hken [@dev]
(<short_io>,<base_VME>,[0]|[<alternate_ethernet_address>])
DESCRIPTION
The hken interface provides access to an Ethernet network
through a V/Ethernet 3207 Hawk Local Area Network (LAN)
Controller. The interface is provided for the AViiON
system.
To include support for this board in the DG/UX system
kernel, you must specify the name of the controller (such as
hken()) in the system configuration file. There are defaults
for the first two hken devices in the system. If your
system uses more than two hken's or if you choose to use
different values for the short IO and/or VME base address,
then the full device specification must be given for those
hken's. The third parameter in the device specification may
be used to provide an alternate ethernet address for this
interface. For more information concerning device
configuration, refer to Writing a Device Driver for the
DG/UXTM System.
EXAMPLES
In the following two examples, the default values for the
initial hken are assumed.
hken()
hken(0)
In the next example, the default values for the second hken
is assumed.
hken(1)
The default values for hken devices are as follows:
First board Second board
Device Code 15 16
Short IO Address ffff4000 ffff5000
Base VME Address 55900000 55980000
In the next example, the device code (dev) is 17, the short
IO address (short_io) is ffff6000 and the base VME address
(base_VME) is 55940000.
hken@17(ffff6000,55940000,0)
Licensed material--property of copyright holder(s) Page 1
hken(7) DG/UX 4.30 hken(7)
In the next example, the alternate ethernet address
(alternate_ethernet_address) is 08001b123456 and the default
values of the first interface are used for the short IO
address and base VME address.
hken(0,,08001b123456)
See the V/Ethernet 3207 Hawk User's Guide for details about
setting the short IO and base VME address using switches on
the board.
If the hken device is configured in the kernel, at boot
time, the node /dev/hken0 will be created.
If more than one device of the same type is specified in the
system configuration file, additional nodes will be created
with increasing identifiers. For example, if there are two
entries in the config file for hken devices, then /dev/hken0
and /dev/hken1 will be created at boot time. /dev/hken0 will
refer to the first entry and /dev/hken1 will refer to the
second entry in the configuration file.
The hken device is implementated as a clonable Streams
driver. This means that a single node, for example
/dev/hken0, may be opened to access any unused minor device.
Using this special node guarantees that a separate Stream
(minor number) will be allocated to the driver on every
open(2) system call.
The host's Internet address for this interface is specified
at network configuration time with an SIOCSIFADDR ioctl.
See ifconfig(1M).
DIAGNOSTICS
Use the -i option with netstat(1C).
SEE ALSO
ifconfig(1M), netinit(1M), system(4). arp(6P), intro(7),
inet(7),
Licensed material--property of copyright holder(s) Page 2