dmfe(7d) - osol9

1dmfe(7D)                            Devices                           dmfe(7D)
2
3
4

NAME

6       dmfe - Davicom Fast Ethernet driver for Davicom DM9102A
7

SYNOPSIS

9       /kernel/drv/sparcv9/dmfe
10
11

DESCRIPTION

13       The  dmfe  Ethernet  device  provides  100Base-TX networking interfaces
14       using the Davicom DM9102A chip, which  incorporates  its  own  internal
15       transceiver.
16
17
18       The  dmfe  driver  functions  include  controller initialization, frame
19       transmit and receive, promiscuous  and  multicast  support,  and  error
20       recovery  and reporting. Multiple controllers installed within the sys‐
21       tem are supported by the driver.
22
23
24       The 100Base-TX standard specifies an auto-negotiation protocol to auto‐
25       matically  select  the mode and speed of operation. The internal trans‐
26       ceiver is capable of performing auto-negotiation with the remote-end of
27       the  link  (link  partner)  and receives the capabilities of the remote
28       end. It selects the highest common denominator mode of operation  based
29       on the priorities. The internal transceiver also supports a forced-mode
30       of operation under which the driver selects the operational mode.
31

APPLICATION PROGRAMMING INTERFACE

33       The /dev/dmfe cloning character-special device is used  to  access  all
34       Davicom DM9102A devices installed in the system.
35
36
37       You must send an explicit DL_ATTACH_REQ message to associate the opened
38       stream with a particular device (ppa). The ppa ID is interpreted as  an
39       unsigned  integer  data  type  and  indicates  the corresponding device
40       instance (unit) number. If the ppa field value does not correspond to a
41       valid  device  instance number for this system, an error (DL_ERROR_ACK)
42       is returned. The device is initialized on first attach and  de-initial‐
43       ized (stopped) at last detach.
44
45
46       The  values  returned  by  the  driver  in the DL_INFO_ACK primitive in
47       response to a DL_INFO_REQ are as follows:
48
49           o      Maximum  SDU  is  1500  (ETHERMTU - defined   in  sys/ether‐
50                  net.h).
51
52           o      Minimum SDU is 0.
53
54           o      DLSAP address length is 8.
55
56           o      MAC type is DL_ETHER.
57
58           o      The  sap length value  is  -2,  meaning the physical address
59                  component is followed immediately by a 2-byte sap  component
60                  within the DLSAP address.
61
62           o      The  broadcast address value is  the Ethernet/IEEE broadcast
63                  address (FF:FF:FF:FF:FF:FF).
64
65
66       Once  in  the  DL_ATTACHED  state, you must send  a DL_BIND_REQ to  as‐
67       sociate a particular Service Access Point (SAP) with the stream.
68

CONFIGURATION

70       By  default,  the  dmfe  driver performs auto-negotiation to select the
71       speed and mode of the link. Link speed and mode can be 100  Mbps  (full
72       or  half-duplex)  or  10 Mbps (full or half-duplex) as described in the
73       100Base-TX standard.
74
75
76       The auto-negotiation protocol automatically selects speed mode  (either
77       100  Mbps  or  10 Mbps) and operation mode (either full-duplex or half-
78       duplex) as the highest common denominator supported by both link  part‐
79       ners.  Because  the  dmfe  device  supports all modes, this effectively
80       selects the highest-throughput mode supported by the other device.
81
82
83       Alternatively, you can explicitly specify the link parameters by adding
84       entries  to the dmfe driver configuration file (/kernel/drv/dmfe.conf).
85       You can set the speed parameter to 10 or 100 to force dmfe  devices  to
86       operate  at  the  specified  speed. Additionally, you can set the full-
87       duplex parameter to 0 or 1 to disable or force  full-duplex  operation,
88       respectively.
89
90
91       Note  that  specifying  either "speed" or "full-duplex" explicitly dis‐
92       ables auto-negotiation. To enable the driver to determine the appropri‐
93       ate  setting for each parameter, you should always set both parameters.
94       If it is necessary to force either speed or duplex setting  (for  exam‐
95       ple,  because the  dmfe device is connected to an ancient device or hub
96       that does not support  auto-negotiation),  both  parameters  should  be
97       explicitly specified to match the requirements of the external device.
98

FILES

100       /dev/dmfe                   Character special device
101
102
103       /kernel/drv/dmfe            32-bit kernel module (x86)
104
105
106       /kernel/drv/sparcv9/dmfe    64-bit kernel module (SPARC)
107
108
109       /kernel/drv/amd64/dmfe      64-bit kernel module (x86)
110
111
112       /kernel/drv/dmfe.conf       dmfe configuration file
113
114

ATTRIBUTES

116       See attributes(5) for descriptions of the following attributes:
117
118
119
120
121       ┌─────────────────────────────┬─────────────────────────────┐
122       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
123       ├─────────────────────────────┼─────────────────────────────┤
124       │Architecture                 │SPARC, x86                   │
125       └─────────────────────────────┴─────────────────────────────┘
126