Lines Matching +full:background +full:- +full:layer

33 .Nd 802.11 network layer
66 software layer.
72 layer for protocol services but devices that off-load functionality
73 may bypass the layer to connect directly to the device.
90 layer virtualizes most 802.11 state
96 layer with drivers responsible purely for moving data between the host
108 layer means that drivers must be structured to follow specific rules.
120 to the 802.11 network stack layer.
181 functions are device-independent handlers for
206 sub-type, for the device
215 sub-type.
218 The virtual radio architecture splits state between a single per-device
225 as read-only.
230 layer as adjunct data to a device's
240 and should be extended with any driver-private state.
244 data structures and should be exploited to maintain driver-private state
255 Long-lasting references to a node are counted to guard against
265 fill-in and/or override to take control of certain operations.
268 layer and are described below.
272 layer with the
275 The driver is expected to allocate and setup any device-private
279 structure must be pre-initialized with state required to setup the
281 layer:
282 .Bl -tag -width ic_channels
304 .Bl -tag -width ic_channels
308 Drivers that support multi-bssid operation may honor the requested BSSID
385 The default method ages frames on the power-save queue (in AP mode)
386 and pending frames in the receive reorder queues (for stations using A-MPDU).
433 Drivers that off-load scan work to firmware typically use this method
434 to trigger per-channel scan activity.
456 Check if transmit A-MPDU should be enabled for the specified station and AC.
457 The default method checks a per-AC traffic rate against a per-vap
458 threshold to decide if A-MPDU should be enabled.
459 This method also rate-limits ADDBA requests so that requests are not
462 Request A-MPDU transmit aggregation.
466 for handling transmit A-MPDU.
469 needed for doing transmit A-MPDU.
471 Shutdown an A-MPDU transmit stream for the specified station and AC.
476 Prepare to receive A-MPDU data from the specified station for the TID.
478 Terminate receipt of A-MPDU data from the specified station for the TID.
483 layer is attached to a driver there are two more steps typically done
485 .Bl -enum
504 worry about being re-entered.
523 layer propagates a subset of these capabilities to each vap through
530 .Bl -tag -width IEEE80211_C_8023ENCAP
534 Device requires 802.3-encapsulated frames be passed for transmit.
539 Device supports Atheros Fast-Frames.
545 Device supports dynamic power-management (aka power save) in station mode.
581 Device supports transmit/receive of 4-address frames.
583 Device supports background scanning.
593 will fall-back to software support when a device is not capable
595 This can be done on a per-key basis.
602 .Bl -tag -width IEEE80211_C_8023ENCAP
608 Device supports hardware AES-OCB cipher.
610 Device supports hardware AES-CCM cipher.
622 layer.
623 .Bl -tag -width IEEE80211_C_8023ENCAP
641 Device supports 1-2 spatial streams for STBC receive.
643 Device supports 1-3 spatial streams for STBC receive.
645 Device supports A-MSDU frames up to 7935 octets.
647 Device supports A-MSDU frames up to 3839 octets.
655 Device supports L-SIG TXOP protection.
657 Device supports A-MPDU aggregation.
658 Note that any 802.11n compliant device must support A-MPDU receive
661 of A-MPDU frames.
663 Device supports A-MSDU aggregation.
664 Note that any 802.11n compliant device must support A-MSDU receive
667 of A-MSDU frames.
707 .An -nosplit