Initialize drive object drivers#
Initialize drive object driver#
Initialize drive object free#

Initialize drive object driver#

The following example shows how a client driver might start a NETADAPTER object. The driver must then call NetAdapterStart to start their adapter. The driver calls NetAdapterSetLinkLayerMtuSize to set the MTU size. Link layer maximum transfer unit (MTU) size. The driver calls NetAdapterSetLinkLayerCapabilities to set these capabilities. For more information, see Network data buffer management. The driver calls NetAdapterSetDataPathCapabilities to set these capabilities. NetAdapterCx requires the client driver to set the following capabilities:Дata path capabilities. Within EVT_WDF_DEVICE_PREPARE_HARDWARE, in addition to other hardware preparation tasks the client driver sets the adapter's required and optional capabilities. To register an EVT_WDF_DEVICE_PREPARE_HARDWARE callback function, a NetAdapterCx client driver must call WdfDeviceInitSetPnpPowerEventCallbacks.

Initialize drive object drivers#

Many NetAdapterCx client drivers start their adapters from within their EVT_WDF_DEVICE_PREPARE_HARDWARE callback function, with the notable exception of Mobile Broadband class extension client drivers. You can optionally provide 2 callbacks to the NET_ADAPTER_DATAPATH_CALLBACKS_INIT method:ДЇor details on what to provide in your implementations of these callbacks, see the individual reference pages. To simplify the porting process, just convert that entire structure to the WDFDEVICE context, and make the NETADAPTER's context a small structure that points to the WDFDEVICE's context. If you are porting an existing NDIS 6.x driver, you'll likely have a single MiniportAdapterContext that combines networking-related and device-related data into a single data structure. We recommend that you put device-related data in the context for your WDFDEVICE, and networking-related data such as link layer addresses into your NETADAPTER context. For more info, see Framework Object Context Space. In the example in step 3, the client adds MY_ADAPTER_CONTEXT to the NETADAPTER object. Since you can set a context on any WDF object, you could add separate context space for the WDFDEVICE and the NETADAPTER objects. Optionally, you can add context space to the NETADAPTER object. PMY_ADAPTER_CONTEXT adapterContext = GetMyAdapterContext(&netAdapter)

// Optional: initialize the adapter's context //

Initialize drive object free#

// Required: free the adapter initialization object even // if adapter creation succeeds // NetAdapterInitFree(adapterInit)

Status = NetAdapterCreate(adapterInit, &attribs, netAdapter) NetAdapterInitSetDatapathCallbacks(adapterInit, NET_ADAPTER_DATAPATH_CALLBACKS_INIT(&datapathCallbacks, NET_ADAPTER_DATAPATH_CALLBACKS datapathCallbacks // Optional: set additional attributes // // Datapath callbacks for creating packet queues PNETADAPTER_INIT adapterInit = NetAdapterInitAllocate(device)

// Allocate the initialization structure // WDF_OBJECT_ATTRIBUTES_INIT_CONTEXT_TYPE(&attribs, MY_ADAPTER_CONTEXT)