HP 800 HP DLPI Programmer's Guide - Page 171

Supported ioctls, DL_IOC_DRIVER_OPTIONS

Page 171 highlights

NOTE DLPI Input/Output Controls Supported ioctls Supported ioctls DLPI supports the following ioctls: • DL_IOC_DRIVER_OPTIONS • DL_IOC_HDR_INFO • DL_HP_SET_DRV_PARAM_IOCTL • DL_HP_GET_DRV_PARAM_IOCTL • DLPI_SET_NOLOOPBACK For all ioctls, either an M_IOCACK or M_IOCNACK message is sent to the DLS user, and if an error occurs, the ioc_error field is set. DL_IOC_DRIVER_OPTIONS DL_IOC_DRIVER_OPTIONS negotiates the options between DLPI and a DLS user. In other words, this ioctl negotiates the features with an instance of the driver. This ioctl is valid for in-kernel STREAMS DLPI users only. DLS user sets the feature bits about which it wants to enquire. DLPI compares the DLS user's feature with the driver's feature and its own internal capability. After the comparison, DLPI clears the bits in driver_ops_type (defined later in this section) that are not supported or not understood by DLPI or driver. The DLS user that negotiates the driver features and header template must also request for link event notifications using the DL_HP_NOTIFY_EVENT_REQ primitive (see "DL_HP_NOTIFY_EVENT_REQ" on page 67). Chapter 3 171

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

DLPI Input/Output Controls
Supported ioctls
Chapter 3
171
Supported ioctls
DLPI supports the following ioctls:
DL_IOC_DRIVER_OPTIONS
DL_IOC_HDR_INFO
DL_HP_SET_DRV_PARAM_IOCTL
DL_HP_GET_DRV_PARAM_IOCTL
DLPI_SET_NOLOOPBACK
For all ioctls, either an M_IOCACK or M_IOCNACK message is sent to
the DLS user, and if an error occurs, the ioc_error field is set.
DL_IOC_DRIVER_OPTIONS
DL_IOC_DRIVER_OPTIONS negotiates the options between DLPI and
a DLS user. In other words, this ioctl negotiates the features with an
instance of the driver.
NOTE
This ioctl is valid for in-kernel STREAMS DLPI users only.
DLS user sets the feature bits about which it wants to enquire. DLPI
compares the DLS user
s feature with the driver
s feature and its own
internal capability. After the comparison, DLPI clears the bits in
driver_ops_type (defined later in this section) that are not supported or
not understood by DLPI or driver.
The DLS user that negotiates the driver features and header template
must also request for link event notifications using the
DL_HP_NOTIFY_EVENT_REQ primitive (see
DL_HP_NOTIFY_EVENT_REQ
on page 67).