Device Control Operations
The ndd_ctl entry point is used to provide device control functions.
- NDD_GET_STATS
- The user should pass in the tok_ndd_stats_t structure as
defined in the sys/cdli_tokuser.h file. The driver fails a
call with a buffer smaller than the structure.
The structure must be in kernel heap so that the device driver can copy the statistics into it. Also, it must be pinned.
- NDD_PROMISCUOUS_ON
- Setting promiscuous mode will not cause non-LLC frames
to be received by the driver unless the user also enables those filters
(Attention MAC frames, Beacon MAC frames).
The driver maintains a counter of requests.
- NDD_PROMISCUOUS_OFF
- This command releases a request from a user to PROMISCUOUS_ON; it will not exit the mode on the adapter if more requests are outstanding.
- NDD_MIB_QUERY
- The arg parameter specifies the address of the token_ring_all_mib_t structure.
This structure is defined in the /usr/include/sys/tokenring_mibs.h file.
The device driver does not support any variables for read_write or write only. If the syntax of a member of the structure is an integer type, the level of support flag is stored in the whole field, regardless of the size of the field. For those fields that are defined as character arrays, the value is returned only in the first byte in the field.
- NDD_MIB_GET
- The arg parameter specifies the address of the token_ring_all_mib_t structure. This structure is defined in the /usr/include/sys/tokenring_mibs.h file.
- NDD_ENABLE_ADDRESS
- This command enables the receipt of packets with a functional
or a group address. The functional address indicator (bit 0 "the MSB"
of byte 2) indicates whether the address is a functional address (bit
0) or a group address (bit 1). The length field is not used
because the address must be 6 bytes in length.
- functional address
- The specified address is ORed with the currently specified functional
addresses, and the resultant address is set as the functional address
for the device. Functional addresses are encoded in a bit-significant
format, thereby allowing multiple individual groups to be designated
by a single address.
The Token-Ring network architecture provides bit-specific functional addresses for widely used functions, such as configuration report server. Ring stations use functional address "masks" to identify these functions. For example, if function G is assigned a functional address of 0xC000 0008 0000, and function M is assigned a function address of 0xC000 0000 0040, then ring station Y, whose node contains function G and M, would have a mask of 0xC000 0008 0040. Ring station Y would receive packets addressed to either function G or M or to an address, such as 0xC000 0008 0048, because that address contains bits specified in the "mask."
The NDD_ALTADDRS and TOK_RECEIVE_FUNC flags in the ndd_flags field are set.
Because functional addresses are encoded in a bit-significant format, reference counts are kept on each of the 31 least significant bits of the address.
- group address
- The device supports 256 general group addresses. The promiscuous
mode is turned on when the group addresses to be set is more than
256. The device driver maintains a reference count on this operation.
The device supports 256 general group addresses. The promiscuous mode is turned on when the group address needed to be set are more than 256. The device driver will maintain a reference count on this operation.
The NDD_ALTADDRS and TOK_RECEIVE_GROUP flags in the ndd_flags field are set.
- NDD_DISABLE_ADDRESS
- This command disables the receipt of packets with a functional
or a group address. The functional address indicator (bit 0 "the MSB"
of byte 2) indicates whether the address is a functional address (bit
0) or a group address (bit 1). The length field is not used
because the address must be 6 bytes in length.
- functional address
- The reference counts are decremented for those bits in the functional
address that are 1 (on). If the reference count for a bit goes to
0, the bit is "turned off" in the functional address for the device.
If no functional addresses are active after receipt of this command, the TOK_RECEIVE_FUNC flag in the ndd_flags field is reset. If no functional or group addresses are active after receipt of this command, the NDD_ALTADDRS flag in the ndd_flags field is reset.
- group address
- If group address enable is less than 256, the driver sends a command
to the device to disable the receipt of the packets with the specified
group address. Otherwise, the group address is deleted from the group
address table.
If there are less than 256 group addresses enabled after the receipt of this command, the promiscuous mode is turned off.
If no group address is active after receipt of this command, the TOK_RECEIVE_GROUP flag in the ndd_flags field is reset. If no functional or group addresses are active after receipt of this command, the NDD_ALTADDRS flag in the ndd_flags field is reset.
- NDD_PRIORITY_ADDRESS
- The driver returns the address of the device driver's priority transmit routine.
- NDD_MIB_ADDR
- The driver returns at least three addresses that are device physical addresses (or alternate addresses specified by the user), two broadcast addresses (0xFFFFFFFFFFFF and 0xC000 FFFF FFFF), and any additional addresses specified by the user, such as functional addresses and group addresses.
- NDD_CLEAR_STATS
- The counters kept by the device are zeroed.
- NDD_GET_ALL_STATS
- Used to gather all statistics for the specified device. The arg parameter
specifies the address of the statistics structure for this particular
device type. The folowing structures are available:
- The sky_all_stats_t structure is available for the PCI Token-Ring High Performance Device Driver (14101800), and is defined in the device-specific /usr/include/sys/cdli_tokuser.h include file.
- The cs_all_stats_t structure is available for the PCI Token-Ring Device Driver (14103e00), and is defined in the device-specific /usr/include/sys/cdli_tokuser.cstok.h include file.
The statistics that are returned contain information obtained from the device. If the device is inoperable, the statistics returned are not the current device statistics. The copy of the ndd_flags field can be checked to determine the state of the device.