Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This section covers WDI data transfer. The following terminology is used in this section.
| Term | Description |
|---|---|
Target WLAN device (target) |
A physical NIC. |
Virtual WLAN device (port) |
A virtual NIC (for example, P2P role ports). |
WDI |
A Microsoft WLAN component. It is a target-agnostic component. |
A target-specific software layer that interfaces with the target through the bus-specific APIs. It creates and manages DMA channels and provides bus abstraction. |
|
RX Manager / RxMgr |
RxMgr performs receive processing steps that are not offloaded to the target. |
RxEngine |
RxEngine sends and receives data-synchronous messages to and from the target, interprets RX descriptor formats, and manages buffers for direct hardware to software RX DMA. |
TX Manager / TxMgr |
The WDI-compliant driver component that gets TX frames from the operating system, delivers them to the TxEngine at the appropriate time, and returns the completed TX frames back to the operating system. |
TxEngine |
The target-specific software component that handles the TX data transfer from host to target, and handles TX completion messages from the target. |
Target Abstraction Layer (TAL) |
The "lower-edge" that has a standardized API to the WDI compliant driver, but has a target-specific internal implementation. The TAL is a container layer for individual target-specific host software components such as TxEngine and RxEngine. |